Hi Lionel, On 14/04/14 19:47, Lionel Ains wrote: > Lionel Ains <lionel.ains@...> writes: >> I tried the script above (adapting >> tools/openocd/platforms/armada/armada370.tcl to my >> tcl/target/armada370.cfg), and matching the JTAG probe I use. >> However, it seems to fail initializing when it meets the line 32 in >> armada370.cfg, namely "dap apsel 1": >> >> openocd-x64-0.8.0-rc1 -f mirabox.cfg >> Open On-Chip Debugger 0.8.0-rc1 (2014-03-31-08:16) >> Licensed under GNU GPL v2 >> For bug reports, read >> http://openocd.sourceforge.net/doc/doxygen/bugs.html >> Info : only one transport option; autoselect 'jtag' >> adapter speed: 5000 kHz >> Warn : target name is deprecated use: 'cortex_a' >> Info : clock speed 5000 kHz >> Info : JTAG tap: armada370.dap tap/device found: 0x4ba00477 (mfg: 0x23b, >> part: 0xba00, ver: 0x4) >> Warn : Invalid ACK 0 in JTAG-DP transaction >> Warn : Invalid ACK 0 in JTAG-DP transaction >> Runtime Error: openocd-0.8.0-rc1/scripts/target/armada370.cfg:32: >> in procedure 'script' >> at file "embedded:startup.tcl", line 58 >> at file "mirabox.cfg", line 5 >> in procedure 'dap' called at file >> "openocd-0.8.0-rc1/scripts/target/armada370.cfg", line 32 >> >> Thanks, >> >> Lionel > > In fact, I think the issue is coming from the lines just below JTAG tap: > armada370.dap tap/device found: 0x4ba00477: > Warn : Invalid ACK 0 in JTAG-DP transaction > > Greg, in your initial post, your log contains: > Info : JTAG tap: armada370.dap tap/device found: 0x4ba00477 (mfg: > 0x23b, part: 0xba00, ver: 0x4) > Info : armada370.cpu: hardware has 6 breakpoints, 2 watchpoints > Info : number of cache level 1 > Error: mpdir not in multiprocessor format > > I guess this output relates to the specific commands: > target create armada370.cpu cortex_a8 -chain-position armada370.dap > > (that I actually adapted into "target create armada370.cpu cortex_a > -chain-position armada370.dap" because cortex_a8 seems deprecated now) > > But when openocd run this command in my Mirabox setup, I don't have the > "armada370.cpu: hardware has 6 breakpoints, 2 watchpoints" line like your > dump, so there must be something wrong there and the remaining then fails on > the apsel command. I tried to switch to adapter_khz 1000 but I still get > this issue.
I do see that with openocd-0.8.0-rc1 too. On some start ups of openocd it fails just as you describe above - not describing the hardware/ breakpoints/watchpoints. Generally I find if I repower the hardware and then re-run openocd it then find the cpu and print the info on it. I rarely see this behaviour on 0.7.0, but it does happen some times. Regards Greg ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
