Well.... Your hints were quite useful. Even if it still buggy.
Øyvind Harboe wrote:
> On Wed, Dec 10, 2008 at 11:21 AM, Andreas Kuehn <[EMAIL PROTECTED]> wrote:
>> Hi!
>>
>> I'm trying to run openocd on an ARM9/uClibc system to access some
>> "client" ARMs and configure them. Therefore, I adapted the at91rm9200
>> interface to my hardware situation. I could verify with a Scope that the
>> signals are there (TCK, TDI, TDO, TMS). Only the openocd gives me some
>> headache. For some reasons I got this output when running from gdb:
>
> The clocking is off somehow. You should have seen 0x000000ff instead
> and you can clearly see that the sometimes the remaining idcodes are
> left/right by one bit.
>
In fact, its a timing problem. I added some LOG_DEBUG lines to the code
and all Warnings dissapeared when running with -d1 or higher.
Unfortunately uClibc has some drawbacks regarding timer stuff which I
desperately need for dealing with the different processor speeds.
BACKGROUND: openocd runs at 200MHz (at91sam9263) and has to connect to
another at91sam9263 which runs at 32kHz after startup. TCK has to be
slower than 32kHz/6 = 5.45kHz. As a result, I have to waste time while
pushing jtag signals. Currently, I use the usleep call to waste the
time, pushing the TCK frequency down to 33Hz. ?-]
Did somebody use something more suitable in relation with uClibc?
>> Info: JTAG device found: 0x0792603f (Manufacturer: 0x01f, Part:0x7926,
>> Version: 0x0)
>> Warning:Unexpected idcode after end of chain! 256 0x000000fe
>> Warning:Unexpected idcode after end of chain! 288 0x0000007f
>> Warning:Unexpected idcode after end of chain! 320 0x000000ff
>> Warning:Unexpected idcode after end of chain! 352 0x0000007f
>> Warning:Unexpected idcode after end of chain! 384 0x800000ff
>> Warning:Unexpected idcode after end of chain! 416 0x000001ff
>> Warning:Unexpected idcode after end of chain! 448 0x800000ff
>> Warning:Unexpected idcode after end of chain! 480 0x000001ff
>> Warning:Unexpected idcode after end of chain! 512 0x000000ff
>> Warning:Unexpected idcode after end of chain! 544 0x800000ff
>> Warning:Unexpected idcode after end of chain! 576 0x000000ff
>> Warning:Unexpected idcode after end of chain! 608 0x800000ff
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00051a3c in interface_jtag_add_dr_out (device_num=0, num_fields=0,
>> num_bits=0x2, value=0xeead8, end_state=TAP_RTI) at jtag.c:732
>> 732 in jtag.c
>
> What SVN version are you running?
>
Sorry about the linenumber. It is revision 1191 and the correct line
number is 714 in jtag.c . The difference is due to my debug lines added
to it.
Nevertheless, the segmentation fault still occurs!
> There isn't really anything on 732 that could segfault.
>
> See also:
>
> http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
>
>>
>>
>> What is the reason for this behavior.
>> a.) Why do I receive "Unexpected idcode"?
>
> your JTAG clock is off.
>
>> b.) Why is that command chain failing?
>>
>> I use openocd svn revision 1191.
>>
>>
>> Regards
>> akuehn
>> _______________________________________________
>> 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
