background preloader

Open On-Chip Debugger

Open On-Chip Debugger
Related:  Electronics

StepStick Please note: StepStick has 0.2 ohm sense resistors instead of Pololu stepper driver boards 0.05 ohm. This limits the current to 1A. See Notes on building for more info. StepStick Release status: experimental With the recent outage of Pololu stepper driver boards, I've been wanting to build my own, and break my dependency (no offense, I <3 you Pololu!). This is an Allegro A4983 / A4988 x4 breakout board for Sanguinololu. Now this is not for the iron wielding solderer. That being said, I believe this is an easy to solder board using a toaster oven or hotplate reflow method. But if you're not up to the task, stay tuned and keep an eye on this place for a published list of places where you can get this pre-assembled. The Pololu A4988 Stepper Motor Driver Carrier is produced on a 2oz copper PCB board. Another consideration is the problem of using x16 microstepping in a low-current application. Adjusting and testing the current Stepsticka4984 Design

CrossWorks for ARM - C/C++ Compiler for ARM and Cortex Microcontrollers CrossWorks for ARM is a complete C/C++ and assembly language development system for Cortex-M, Cortex-A, Cortex-R, ARM7, ARM9, ARM11, and XScale microcontrollers. And when we say complete we mean complete — CrossWorks for ARM is packed full of features such as: CrossStudio Integrated Development Environment which takes care of edit, build, flash download, and debugging over JTAG. C, C++, and assembler toolchain from the GNU Compiler Collection. Supported cores, devices, boards, and technologies CrossWorks supports a wide range of ARM cores: For a complete list of the CPUs, devices, and technologies we support, you can browse… CPU Support packages for all popular, and not-so-popular microcontrollers. Wide industry support Because CrossWorks for ARM uses the industry-standard GNU Compiler Collection, many companies realize that it makes perfect business sense to support GCC. SEGGER has support for CrossWorks on Cortex-M, ARM7, ARM9, and Cortex-A/R, and MSP430. Target Connections Computer Support

ARM - by Andreas Schwarz ARM is a company that develops processor cores. ARM does not produce any silicon itself, but licenses the IP (intellectual property) to semiconductor manufacturers who integrate the core with peripherals and RAM. Architectures The ARM7(TDMI) was the first ARM architecture that gained widespread use in small to medium-size microcontrollers. The extension TDMI indicates support for an additional, 16 bit instruction set, called Thumb. The first company to offer small ARM7-based microcontrollers was Philips (today NXP) with the LPC2000 series, which is still popular especially among hobbyists because of the wide availability and the easy to use serial-port bootloader. The ARM7TDMI has a few disadvantages, though. ARM7-based controllers are available from many manufacturers, for example NXP (LPC2000), Atmel (AT91SAM7*), ADI (ADUC7000), ST (STR7). ARM Cortex-M4 The Cortex-M4 is a Cortex-M3 with DSP Instructions, and optional floating-point unit (FPU). ARM Cortex-M3 ARM Cortex-M0+

OpenOCD - Open On-Chip Debugger (JTAG) | Get OpenOCD - Open On-Chip Debugger (JTAG) at Simple Pyro RF Transmitter (27 MHz) While it may seem like a trivial idea to create a wireless on/off switch, the design, implementation and understanding that goes into such a thing is actually much more invovled than you would first think. For many years I have wanted to build an RF transmitter and RF receiver pair from scratch but it always proved too difficult. This time things will be different! In this article we'll explore what it takes to build a simple rf transmitter at 27 mhz, the different stages that go into the transmitter, how those stages interact and we'll test it out with some measurement equipment. The ultimate goal will be to pair this transmitter with a receiver, so that when we transmit, the receiver turns on an LED. Simple Pyro RF Receiver + Transmitter (27 MHz) - Demonstration Simple Pyro RF Transmitter (27 MHz) - Project Setup Purpose & Overview Of This Project The purpose of this project is to create an RF transmitter that can send on/off pulses out of its antenna to some receiver.

News - BeagleBoardOpenOCD This page is about how to use open source OpenOCD JTAG software with BeagleBoard and Linux. With this, it will be possible to have OMAP3 JTAG debug using cheap JTAG hardware, e.g. Flyswatter. As of September 2009, OpenOCD has basic support for OMAP3 and ARM Cortex A8 on Beagle Board. Status: You need at least OpenOCD revision 2770 (using git). To be able to use OpenOCD with OMAP3 based BeagleBoard, make sure that your JTAG Dongle supports: 1.8V devices. Flyswatter dongle supports both requirements. OpenOCD build instructions describe how to build OpenOCD. Get OpenOCD code via git: > git clone openocd For Flyswatter you additionally need libftd2xx or libFTDI. If you downloaded OpenOCD git and have libftd2xx or libFTDI, build OpenOCD (assuming you extracted/built FTDI library already): > cd openocd > . When compiling the doc directory You get an error: openocd.texi:12: @include `version.texi': No such file or directory. make pdf or > . > bp

OpenOCD OpenOCD provides Free and Open On-Chip Debugging, In-System Programming and Boundary-Scan Testing Look for the package named openocd in the Synaptic Package Manager and install it. OpenOCD Setup After installing OpenOCD package, you need to set permissions right. Create a file ""/etc/udev/rules.d/45-ft2232.rules"" with following contents: BUS! Then connect ARM-USB-OCD to the USB port. Connect ARM-USB-OCD dongle to LPC-H2103 prototype board via JTAG cable. Power on LPC-H2103 board by giving 5 volts between Vin and gnd pins. Next you need to create a configuration file. The file can be named for example openocd.cfg, and the contents of that file: source [find interface/olimex-arm-usb-ocd.cfg] source [find target/sam7x256.cfg] This configuration should automatically find the correct default configurations for the board and for the dongle. Start OpenOCD daemon with the following command: openocd -f openocd.cfg TODO: Add output here Test the setup by connecting to openocd daemon with telnet: