[mc1322x] CodeSourcery , flash loader

[Jon Smirl]

On Tue, May 11, 2010 at 4:07 PM, Andrew Pullin <pullin at berkeley.edu> wrote:
> Actually, as I was writing this, my J-Link EDU came in the mail, and trying
> the same thing with the JLink + OpenOCD seems to produce identical results:
> jump to 0x04.

That's probably because the JLink has the same ft2232 chip inside of
it that is on the econotag.

> So, any idea what's going on? Something to do with a call to a function
> that's in ROM?
> Sorry if this is something "obvious" ; I've never gotten JTAG to work with a
> project before, and I always end up debugging-by-printf... so I'm very
> interesting in getting this to work right.

I'm not sure ARMv4 openocd has been thoroughly tested. Mar, if this is
giving you trouble cc the openocd list. There are ARM experts on that
list.

May be a problem with the machine defines about the memory setup.

>
> -Andrew
>
> On 05/06/2010 04:49 AM, Mariano Alvira wrote:
>>
>> On Wed, May 05, 2010 at 07:09:16PM -0700, Andrew Pullin wrote:
>>
>>>
>>> On 05/02/2010 11:03 AM, Mariano Alvira wrote:
>>>
>>>>
>>>>
>>>
>>> Ah, ok, OpenOCD seems to work, for the most part. If I connect via gdb,
>>> I can load&  run a program as per the instructions on the site.
>>> Unfortunately, debugging doesn't seem to be working? If I do a "break
>>> main", and then "continue", it won't work right:
>>>     Warning:
>>>     Cannot insert breakpoint 8.
>>>     Error accessing memory address 0x400982: Unknown error 4294967295.
>>>
>>> Single instruction stepping seems to work and output the proper source
>>> lines, but OpenOCD occasionally generates "Error: address + size
>>> wrapped(0xfffffffe, 0x00000004)" .
>>>
>>> I'm using a development version of OpenOCD, 0.5.0-dev-00191-gcc5f3c8,
>>> built with --enable-maintainer-mode . Have you gotten breakpoints and
>>> debugging to work fully?
>>>
>>
>> Yes, that should work. OpenOCD does change and break stuff frequently
>> though. What kernel are you running? There is a bug in the ftdi driver
>> for the FT2232H that has been fixed since 2.6.31 --- it caused data to
>> be lost randomly (also caused dropped serial characters). If you
>> aren't running a newer kernel then I'd try that before trying a
>> different version of OpenOCD.
>>
>> I know this commit is good: 0324eb24967088f753bc2fd997b4c18f4ea988c8
>>
>> So if it is Openocd you can bisect against that.
>>
>>
>>>
>>>
>>>>>
>>>>> If the Econotag has onboard JTAG, does that mean that there's a way to
>>>>> do a similar thing with the redbee-dev, not needed a JTAG pod?
>>>>>
>>>>>
>>>>
>>>> Yes, you plug in an EconoTAG and run:
>>>>
>>>>     openocd -f board/redbee-econotag.cfg
>>>>
>>>>
>>>
>>> That seems to work for the Econotag, but the small redbee + dev board
>>> only enumerates one USB->serial device when I plug it in, which seems to
>>> be the communication UART.
>>>
>>
>> Ah, I think I misunderstood/misread your question. The module has it's
>> JTAG pins on the top and no JTAG controller. The dev board doesn't
>> hook into JTAG at all --- so for the redbee + dev combo you need an
>> external JTAG pod.
>>
>> -Mar.
>>
>
>
> _______________________________________________
> mc1322x mailing list
> mc1322x at devl.org
> http://devl.org/cgi-bin/mailman/listinfo/mc1322x
>



-- 
Jon Smirl
jonsmirl at gmail.com