On Thursday 30 December 2010 08:27:52 Øyvind Harboe wrote: > Merged. > > Thanks! > > Took it for a spin on AM3517 and that target is no longer > incorrectly identified as an imx51. > > > That target still needs work though: > > oyv...@titan:~/workspace/openocd$ openocd -c "interface ZY1000; > zy1000_server 127.0.0.1;jtag_khz 50" -f board/am3517evm.cfg > Open On-Chip Debugger 0.5.0-dev-00682-g0136977 (2010-12-30-08:23) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > Warn : Adapter driver 'ZY1000' did not declare which transports it > allows; assuming legacy JTAG-only > Info : only one transport option; autoselect 'jtag' > 50 kHz > 10 kHz > trst_only separate trst_push_pull > jtag_speed 6000 => JTAG clk=10 kHz > Info : clock speed 10 kHz > Info : JTAG tap: am35x.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, > part: 0xb7ae, ver: 0x0) > Info : JTAG tap: am35x.dap enabled > Info : am35x.cpu: hardware has 6 breakpoints, 2 watchpoints > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x2800042, MEM_AP_TAR 0x54011140 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x2800042, MEM_AP_TAR 0x54011140 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x2800042, MEM_AP_TAR 0x54011140 > Error: JTAG-DP STICKY ERROR
These errors here, right ... need to investigate. Any pointers possibly ? _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
