thanks! I telnet-ed in and was able to write my .bin file, although it's a pain to do so through command line, surely there must be a way to make this simpler... I am unable to run the same commands from the .cfg file, putting
Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 2000 kHz srst_only srst_pulls_trst srst_gates_jtag srst_open_drain Warn : sam7x512.cpu: nonstandard IR mask Info : max TCK change to: 30000 kHz Info : clock speed 2000 kHz Info : JTAG tap: sam7x512.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3) Info : Embedded ICE version 1 Info : sam7x512.cpu: hardware has 2 breakpoint/watchpoint units
after a long time of waiting for something to happen
Thanks for the pointer to that file, it was not included in the package I downloaded, I tried the at91sam7sx.cfg before and got a bunch of errors regarding the IDs not matching (not surprised)
Do I have to recompile anything so that the at91sam7x256.cfg works? is there anywhere in the source code where I can check that the ID I want is defined?
I'm stumped on how to use OpenOCD and Bus Blaster to write to my AT91SAM7XC512
The document "using open source tools for at91sam7s cross development" appears to be very outdated as many of the commands have different parameters now. Many of the command names appears to have changed as well. Many guides I found are completely useless, since many of the commands they have used no longer exist, such as "jtag_device".
Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 30000 kHz Info : max TCK change to: 30000 kHz Info : clock speed 30000 kHz Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!! Warn : AUTO auto0.tap - use "jtag newtap auto0 tap -expected-id 0x7f1f1f1f ..." Warn : AUTO auto0.tap - use "... -irlen 2" Error: auto0.tap: IR capture error; saw 0x0003 not 0x0001 Info : JTAG tap: auto0.tap tap/device found: 0x7f1f1f1f (mfg: 0x78f, part: 0xf1f1, ver: 0x7) Error: auto0.tap: IR capture error; saw 0x0003 not 0x0001 Command handler execution failed Warn : jtag initialization failed; try 'jtag init' again. Warn : gdb services need one or more targets defined
Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 30000 kHz Info : max TCK change to: 30000 kHz Info : clock speed 30000 kHz Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!! Warn : AUTO auto0.tap - use "jtag newtap auto0 tap -expected-id 0x0b63207f ..." Warn : AUTO auto0.tap - use "... -irlen 2" Error: auto0.tap: IR capture error; saw 0x0003 not 0x0001 Info : JTAG tap: auto0.tap tap/device found: 0x0b63207f (mfg: 0x03f, part: 0xb632, ver: 0x0) Error: auto0.tap: IR capture error; saw 0x0003 not 0x0001 Command handler execution failed Warn : jtag initialization failed; try 'jtag init' again. Warn : gdb services need one or more targets defined
Note, my target is powered and appears to be responding, as I am able to see its identifiers Also notice the line "Error: auto0.tap: IR capture error; saw 0x0003 not 0x0001"
From the OpenOCD manual says "The bit pattern loaded by the TAP into the JTAG shift register on entry to the ir capture state, such as 0x01. JTAG requires the two LSBs of this value to be 01."
Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 30000 kHz Warn : at91samx512.cpu: nonstandard IR mask Info : max TCK change to: 30000 kHz Info : clock speed 30000 kHz Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. Command handler execution failed Warn : jtag initialization failed; try 'jtag init' again. Warn : gdb services need one or more targets defined
I double checked the power, and also even tried 2000 kHz instead of 30000 kHz
Also note that I am specifying at91sam7x512 instead of at91sam7xc512 because OpenOCD told me I should (I forgot when I got an warning, but it did tell me to use x instead of xc)
it got the ID just fine at 30000 kHz, I think the speed and connections and power are all fine. I can still use SAM-BA with the TST and ERASE pins.
Can anybody help me simply write a .bin file into my AT91SAM7XC512?
I would add to what sqkybeaver said - it depends on the application.
I've been doing CPLD and FPGA programming with a 30cm long tangle of 1-to-1 jumper wires, but it is quite slow.
For high-speed arm debugging or something like that short as possible is probably best, I'd try 10cm and less if possible.[/quote]
It arrived fast since I paid for UPS shipping instead of regular, it actually got here in 4 days, the shipment confirmation was sent from Seeed on their Monday morning (my Sunday night), and arrived on my Monday afternoon, but the tracking said it was shipped on Friday.
Are you suggesting that the wire length actually affects the speed of the JTAG interface? Did you have to adjust the speed of the JTAG interface due to the long wires?
I made my cable about 6" long and it's then connected to an adapter I made that's designed for my target board. All the ground wires are connected.
I have a question regarding the ground wires on a 20 pin JTAG flat cable: what is the significance of having alternating signal-ground pairs of wires? Is it to provide a return path for all the signals in close proximity in order to reduce EMF?
Hey I got my V1, awesome. I got some flat cable and connectors and I'm wondering how long I can make the flat cable before running into problems?
How do I calculate this? In our power system class, we covered inductance and admittance of 3 phase transmission lines, I'm not sure if that kind of stuff will apply here.
I'm not that familiar with CPLDs myself. A few 7400s I can handle though.
Good to hear the news about the Bus Blaster V1, I'll be eff-fiving Seeed Studio so I don't miss it. The PCB I got them to make is ready to ship, and Ponoko already shipped my laser cut sheets. :-D
It's 3.3V, AT91SAM7XC512. I was actually originally planning on getting the FT2232 breakout board and then building a buffer + header attachment myself using a perfboard and some 7400s, but it was out of stock. I actually thought it would've been smart for you to simply provide everything on the Bus Blaster as an attachment for the breakout board instead.
I also have an Altera USB-Blaster clone, but I'm not sure how straight forward it will be to get it working with OpenOCD to do work with ARM, or how to get it working with CrossWorks which is a backup plan.
I only have PayPal right now, DigiKey or Mouser requires me to call in some favors.
So they had them working and they just stopped working on a different computer? Hopefully something good happens soon.
My PCB is an ARM7 project and I can't do anything with unless I have a JTAG debugger Hopefully this gets resolved soon
What happens to the entire batch if the failure was due to a hardware issue or unknown issue instead of a driver or software issue? I'd take one for a heavy discount.
Video and instructions at http://www.instructables.com/id/Music-P ... arm-Clock/ I know most of you will simply glance at the first page and maybe skim through the rest. This Instructable has 18 steps (with demo examples for each building block) and 5 appendices, with about 90 files and pictures, including logic analyzer files/screencaps, expected terminal output, USB device dumps. I sincerely hope you explore all my efforts. I covered everything from SD cards, FAT file system, USB mass storage, IR remote control, LCDs, RTCs, and decoding MP3s. It's built using a Teensy++ and encased into a SparkFun shipping box.
cool, I already have my own version done using USnooBie and a bargraph on a breadboard, I should really document it
or... since everybody and their dog has a smartphone except me... a pager motor vibrator for a laptop? need to look up the current I can suck through the expresscard slot later
