[quote author="ian"]I'm sorry we couldn't help you out.
Quote
This happens regardless if the usb cable/buspirate is plugged in or not.
Quote
Then I would guess the port name was wrong. Did you ever try screen /dev/ttyUSB0 (or similar) to open a terminal to the Bus Pirate to be sure it is present on your system?
The screen part works fine and responds as it should.
Quote
So I only have the GND = Black, TX= Pink and RX= Brown connected.
Quote
I also just noticed this. The pinout you link is a whole JTAG header (TDI/TDO, etc), but this describes a serial UART, probably for a serial console terminal. I don't think it is the cause of your issue, but I have never heard of a JTAG device being JTAGed though a serial header. Did you also connect the new programmer that way?
[/quote]
This is even before you hook anything up, at this point all I have is the OpenOCD and buspirate connected, nothing else.
# Disabled for the dockstar #arm7_9 dcc_downloads enable
# this assumes the hardware default peripherals location before u-Boot moves it set _FLASHNAME $_CHIPNAME.flash nand device $_FLASHNAME orion 0 0xd8000000
proc dockstar_init { } {
# We need to assert DBGRQ while holding nSRST down. # However DBGACK will be set only when nSRST is released. # Furthermore, the JTAG interface doesn't respond at all when # the CPU is in the WFI (wait for interrupts) state, so it is # possible that initial tap examination failed. So let's # re-examine the target again here when nSRST is asserted which # should then succeed. jtag_reset 0 1 feroceon.cpu arp_examine halt 0 jtag_reset 0 0 wait_halt
openocd -f ./dockstar.cfg Open On-Chip Debugger 0.5.0-dev-00959-gd6c42bf (2011-07-23-18:11) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html Warn : Adapter driver 'buspirate' did not declare which transports it allows; assuming legacy JTAG-only Info : only one transport option; autoselect 'jtag' srst_only separate srst_gates_jtag srst_open_drain trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain adapter_nsrst_delay: 200 jtag_ntrst_delay: 200 500 kHz adapter_nsrst_delay: 500 Warn : use 'feroceon.cpu' as target identifier, not '0' dockstar_reset_cpu Error: You need to specify port ! in procedure 'init'
Everything sounds correct. Did you try loading the latest v5.10 firmware HEX with either the ds30 Loader or the pirate-loader console utility? That should complete the update. Just program, then remove jumper, then re-plug the Bus Pirate USB cable to reset into normal mode. Either of these methods should work: http://dangerousprototypes.com/docs/Bus ... tloader_v4
Which update docs are you have a problem with? I'll do my best to add new notes. Is this it: http://dangerousprototypes.com/docs/V2_to_v4_upgrades In step 2 ONLY the p24qp bootloader utility should be used, never the ds30 loader.
What Bus Pirate version do you have? No currently-shipping Bus Pirate should need a bootloader update, they already have bootloader v4 from the factory.
Ahh well I didnt check it before I started, I assumed it was coming with it shipped with the older versions.
Yes I loaded it with 5.10 and still nothing comes out of the terminal.
v2 to v4, p24qp doesnt work with the newer bus pirates if they come pre-loaded and I ave no way of telling what bootloader/firmware, do you think its fubared? Should i get an rma?
Bootloader 4.4, well that explains why I couldnt reload it.
I am new to using the buspirate, I followed the instructions outlined in the How-to: Bus Pirate bootloader v4 upgrade, I can tell you that for the first time user this is a very frustrating doc as I attempted to load the "boot loader" in section 2, I got the pic loader to finally run only to find that it produced an error.
I looked on the forums and saw someone else having the same issue and someone mentioned that it wasn't compatible and to use the ds30 loader. Shouldn't this have been reflected in that doc?
I went to step 4 and followed those instructions, I load3-4.3 bootloader and the 5.10 firmware. When I load tera term I get 0 response from the terminal. I look on the forums again and follow the *After I upgrade to v4+ firmware my Bus Pirate doesn't work, I don't see anything in the terminal, etc.* directions.
The problem I am getting is I got it to respond one time via terminal and that it asked me if I wanted to upgrade the bootloader, I saw that it was on 4.4 and it loaded 4.3 again.
Now ds30 doesn't give me the option to write and tera term doesn't give me any output.
I have deleted the dir but when I select the 4.4 bootloader the write option grays out and I am not able to write to the buspirate. I have removed the xml copied the directory where the 4.4 loader is but i get a unhandled expection and I have to quit the app. I have reloaded the app but the write is grayed out. I open the terminal that's built into the ds30 and I get BL4+ as the response back.
In fact when I load tera term and type anything in there i get BL4+ as a repeating response.
I do have the jumper between the PGC and the PGD, I do see the mode light come on.
I loaded the bootloader v3 upgrade to v4to4.3 and I was able to write to that, I loaded tera term and i got the found bootloader 4.3, will install bootloader 4.3 hit yes to program, i hit yes and it said success , upload the new firmware with the ds30 loader and when i hit enter I get BL4+ and the mode light is on.
I load ds30 loader and select 4.4 bootloader and the write is grayed out. I load tera term and set for 115200 and i get no responce, I do see the rx light light up but nothing else. If I reload the 3v to 4.3 hex I do get a responce but it keeps asking me to to type yes to program the bootloader.
