Hi Zach,
I can confirm that the amt_jtagaccel problem exists for me too, and that
Ferdinands patch does fix it. This is on linux with ft2232_libftdi:
./configure --enable-maintainer-mode --enable-ft2232_libftdi \
--enable-parport --enable-parport_ppdev --enable-amtjtagaccel \
--disable-shared
Target is lh79520.
I have been using Amontec chameleon with jtag_accel firmware, also
Amontec jtag-key. The chameleon has always given an incorrect ID code
for me, when compared to the jtag-key (also when compared to an Abatron
BDI2000).
With the patch, the ID code is correct.
It sucessfully programs flash.
GDB debugging seems to work. I am unable to confirm it is perfect
because it has always been flaky for me on this target.
Thanks,
John Devereux
Zach Welch <z...@superlucidity.net> writes:
> Without further confirmation of this patch's correctness, I do not want
> to add it until after the 0.2.0 branch release. I have been trying to
> push that out for most of the week, but it would be good to include this
> fix if it is indeed required.
>
> Can you perhaps provide a little more explanation regarding why you
> believe this patch to be correct? Sorry for having to ask, but I need
> to learn the details in order to make an informed decision about it.
>
> On Fri, 2009-07-03 at 22:16 +0200, Ferdinand Postema wrote:
>> Hello,
>>
>> I found the bug by myself. I have made a patch file to correct it.
>> Is it possible to incorporate this patch into the source code?
>>
>> Ferdinand Postema
>>
>>
>> Ferdinand Postema schreef:
>> > First I want to say that I am very happy with the OpenOCD-software! I
>> > like it very much.
>> >
>> > I have a Chameleon POD from Amontec. This dongle can be programmed to
>> > act as a Wiggler-cable, but also as a JTAG Accelerator interface.
>> > I use it in combination with an ARM processor and a FPGA. Both are
>> > supplied by Propox.
>> >
>> > When I use the Wiggler JTAG interface, I get the following information:
>> > Info : JTAG tap: at91sam9260.cpu tap/device found: 0x0792603f
>> > (Manufacturer: 0x01f, Part: 0x7926, Version: 0x0)
>> > When I use the Amontec JTAG Accelerator Interface, I get the following
>> > information:
>> > Info : JTAG tap: at91sam9260.cpu tap/device found: 0x03c9301f
>> > (Manufacturer: 0x00f, Part: 0x3c93, Version: 0x0)
>> > It looks like the whole word is shifted 1 bit. I think the Wiggler
>> > interface is correct.
>> >
>> > I also tried my FPGA module and got the following ID's:
>> > Manuf. Chip wiggler amtjtagaccel
>> > Processor: Atmel AT91SAM9260 0x0792603f 0x03c9301f
>> > Platform Flash: Xilinx XCF01S 0xF5044093 0x7A822049
>> > FPGA: Xilinx XC3S200 0x01414093 0x80A0A049
>> >
>> > The ID of the FPGA is not only shifted 1 bit to the right, but is also
>> > OR-ed with 0x80000000
>> > The wiggler ID is correct
>> >
>> > Can you correct this?
>> >
>> > Kind regards,
>> >
>> > Ferdinand Postema
>> > (The Netherlands)
>> >
>> plain text document attachment (openocd_wrong_id_code.patch)
>> Index: src/jtag/amt_jtagaccel.c
>> ===================================================================
>> --- src/jtag/amt_jtagaccel.c (revision 2461)
>> +++ src/jtag/amt_jtagaccel.c (working copy)
>> @@ -92,8 +92,8 @@
>> static uint8_t amt_jtagaccel_tap_move[6][6][2] =
>> {
>> /* RESET IDLE DRSHIFT DRPAUSE
>> IRSHIFT IRPAUSE */
>> - {{0x1f, 0x00}, {0x0f, 0x00}, {0x8a, 0x04}, {0x0a, 0x00}, {0x06, 0x00},
>> {0x96, 0x00}}, /* RESET */
>> - {{0x1f, 0x00}, {0x00, 0x00}, {0x85, 0x08}, {0x05, 0x00}, {0x8b, 0x08},
>> {0x0b, 0x00}}, /* IDLE */
>> + {{0x1f, 0x00}, {0x0f, 0x00}, {0x05, 0x00}, {0x0a, 0x00}, {0x06, 0x00},
>> {0x96, 0x00}}, /* RESET */
>> + {{0x1f, 0x00}, {0x00, 0x00}, {0x04, 0x00}, {0x05, 0x00}, {0x06, 0x00},
>> {0x0b, 0x00}}, /* IDLE */
>> {{0x1f, 0x00}, {0x0d, 0x00}, {0x00, 0x00}, {0x01, 0x00}, {0x8f, 0x09},
>> {0x8f, 0x01}}, /* DRSHIFT */
>> {{0x1f, 0x00}, {0x0c, 0x00}, {0x08, 0x00}, {0x00, 0x00}, {0x8f, 0x09},
>> {0x8f, 0x01}}, /* DRPAUSE */
>> {{0x1f, 0x00}, {0x0d, 0x00}, {0x07, 0x00}, {0x97, 0x00}, {0x00, 0x00},
>> {0x01, 0x00}}, /* IRSHIFT */
>> _______________________________________________
>> Openocd-development mailing list
>> Openocd-development@lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/openocd-development
>
> _______________________________________________
> Openocd-development mailing list
> Openocd-development@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/openocd-development
>
--
John Devereux
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
