• Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 566 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Updated DM355.cfg for OpenOCD?

Benjamin West
Prodigy 20 points

I've been trying to get the Olimex USB JTAG pod and OpenOCD v0.1.0 to work with the DM355 eval board.

I had been using this wiki page as a guide...
http://wiki.davincidsp.com/index.php?title=Debugging_on_DaVinci_using_Olimex_dongle

Likewise, I was using this page for advice on installing OpenOCD on Ubuntu v8.10:
http://openhardware.net/Embedded_ARM/OpenOCD_JTAG/

However, the problem appears to be that the DM355.cfg offered on davincidsp.com uses obsolete syntax.  In particular, this is what I get using the DM355.cfg data provided with OpenOCD v0.1,0.  Might anyone have tips for updating DM355.cfg syntax?

$ sudo openocd -f DM355.cfg
Open On-Chip Debugger 0.1.0 (2009-01-24-18:18) Release


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: https://kc8apf@svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.1.0/src/openocd.c $
OLD SYNTAX: DEPRECATED - translating to new syntax
jtag newtap CHIP TAP -irlen 4 -ircapture 0x1 -irvalue 0x0
Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)
jtag newtap stm32 cortexm3  ....., thus creating the tap: "stm32.cortexm3"
jtag newtap stm32 boundry  ....., and the tap: "stm32.boundery"
And then refer to the taps by the dotted name.
NEW COMMAND:
OLD SYNTAX: DEPRECATED - translating to new syntax
jtag newtap CHIP TAP -irlen 4 -ircapture 0x1 -irvalue 0x0
Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)
jtag newtap stm32 cortexm3  ....., thus creating the tap: "stm32.cortexm3"
jtag newtap stm32 boundry  ....., and the tap: "stm32.boundery"
And then refer to the taps by the dotted name.
NEW COMMAND:
OLD SYNTAX: DEPRECATED - translating to new syntax
jtag newtap CHIP TAP -irlen 6 -ircapture 0x1 -irvalue 0x0
Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)
jtag newtap stm32 cortexm3  ....., thus creating the tap: "stm32.cortexm3"
jtag newtap stm32 boundry  ....., and the tap: "stm32.boundery"
And then refer to the taps by the dotted name.
NEW COMMAND:
Runtime error, file "DM355.cfg", line 24:
    bad option "arm926ejs": must be one of count, create, current, names, number, or types

  • Intellectual 870 points

    Get the current sources using subversion.  There's now a ti_dm355.cfg ...

    > scan_chain
     TapName            | Enabled |   IdCode      Expected    IrLen IrCap  IrMask Instr    
---|--------------------|---------|------------|------------|------|------|------|---------
 0 | dm355.etb          |    Y    | 0x2b900f0f | 0x2b900f0f | 0x04 | 0x01 | 0x0f | 0x0f
 1 | dm355.arm          |    Y    | 0x07926001 | 0x07926001 | 0x04 | 0x01 | 0x0f | 0x0c
 2 | dm355.jrc          |    Y    | 0x0b73b02f | 0x0b73b02f | 0x06 | 0x01 | 0x3f | 0x3f

    The ETM and ETB are wired up too, so you can experiment with the trace module.  You'll have to roll your own board glue for now though, including all the nasty lowlevel stuff like setting up PLLs, clocks, and memory timings.