excuse me for the delayed response. I forgot the buspirate @ work, so i couldn't make any test through weekend.
After several firmware testing (5.5, 4.5, 4.2) i discovered that VR2 (MIC5205-3.3) was giving 4.068V instead of 3.3V. I really don't know how i semi burnt it. But hardware sometimes get screwed up. Iron time!!
I checked the IC labeling, so it's not a problem of a wrong chip but of a bad use!!.
Anyway, thank you for the tips.
Slimfish
edit: i replaced the mic5205-3.3 by a tps76033 (i didn't have any other right here) and everything works fine (checked with all firmwares). Bus pirate hardware is very resilient!!!
i've recently upgraded my buspirate v2go to fw V5.4. When i tried to use the PSU it reported an error (VREG too low, is there a short?), so i disconect everything and performed a self test (with Vpu to +5V and ADC to +3.3V connections).
The test failed due low voltages but i measured them (before terminating the test) and they are 5V and 3.3V as expected. The case is that self-test measured values are off by the same constant (5/3.8 = 3.3/2.5)
Bus Pirate v3a Firmware v5.4 (r454) Bootloader v4.4 DEVID:0x0447 REVID:0x3043 (B5) http://dangerousprototypes.com HiZ> HiZ> ~ Disconnect any devices Connect (Vpu to +5V) and (ADC to +3.3V) Space to continue Ctrl AUX OK MODE LED OK PULLUP H OK PULLUP H OK VREG OK ADC and supply 5V(3.80) FAIL VPU(3.80) FAIL 3.3V(2.50) FAIL ADC(2.50) FAIL Bus high MOSI OK CLK OK MISO OK CS OK Bus Hi-Z 0 MOSI OK CLK OK MISO OK CS OK Bus Hi-Z 1 MOSI OK CLK OK MISO OK CS OK MODE and VREG LEDs should be on! Any key to exit Found 4 errors.
I've compared schematic of Olimex dev. board with the board i have (DSO Nano) and JTAG resistors are not exactly the same (18K instead of 10K) and not all resistors are pull-up. So i will try to match the resistors in your board and see what happens... but unfortunately that will be on monday.
The cables are quite short, about 10cm or less and all run in parallel. If you had the same problem with the wiggler and long cables maybe firmware is toggling JTAG lines too fast.
Tomorrow i'll try to make the cable shorter (3cm) and test again.
finaly, i'd managed to update my buspirate firmware and build the openOCD (0.5.0-dev-00066-g17d437a-dirty). I've sucessfully connected to a STM32F106 CPU. But when i tried to make a flash dump to test the transfer speed ( dump_image /home/slimfish/backup.bin 134217728 131072) i've got the following error:
Open On-Chip Debugger 0.5.0-dev-00066-g17d437a-dirty (2010-03-10-09:39) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html srst_only separate srst_gates_jtag srst_open_drain 1000 kHz jtag_nsrst_delay: 100 jtag_ntrst_delay: 100
Info : Buspirate Interface ready! Error: Translation from jtag_speed to khz not implemented Info : interface specific clock speed value 1000 Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) Info : JTAG tap: stm32.bs tap/device found: 0x16410041 (mfg: 0x020, part: 0x6410, ver: 0x1) Info : stm32.cpu: hardware has 6 breakpoints, 4 watchpoints Info : accepting 'telnet' connection from 0 Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) Info : JTAG tap: stm32.bs tap/device found: 0x16410041 (mfg: 0x020, part: 0x6410, ver: 0x1) target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x08000120 msp: 0x20000a7c Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x80000004 Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x80000004 Warn : Block read error address 0x80000000, count 0x8c Command handler execution failed
Do you know what does the error mean? (i'm pretty new to OpenOCD). By the way, i'm not using TRST pin... could be that the source of the error?
Congratulations robots (as i'm afraid that the error is not in the code but in my openocd 'skills'). Again, kudos to you.
i followed the steps you post in the howto. But some problems have arose: -When i updated buspirate firmware with the one you provided, does it replace bootloader (v4.2) somehow? the GUI only allowed me to burn the new firmware if the bootloader can be overwritten. -Related to previous one... is there any way to check if the buspirate has the openocd firmware up and running via terminal?
