From: Joel H. <jo...@ai...> - 2013-07-15 11:09:41
|
Hi All, I'm tackling a couple of issues that maybe this list can help me with. My setup is a bespoke board with a TI DM368 (very similar to the Davinci DM365) with a Flyswatter 2 adapter. I have two problems: 1. I'm having trouble connecting. The only way I can get it to enumerate the TAPs is if I press the board reset button with the ribbon cable disconnected, then connect the ribbon, then run openocd. If I don't follow this procedure, it times out with "Error: couldn't read enough bytes from FT2232 device (0 < 81)" messages. Any ideas why this would be? 2. My JTAG port doesn't have a SRST pin on it, so I want to use davinci_wdog_reset. Unfortunately this fails because of a problem with the mww command. If I call the offending command in isolation (mww phys 0x01c21c28 0x00004000) with the debug level set to three, I get the following messages printed: Debug: 407 43677 command.c:145 script_debug(): command - ocd_command ocd_command type ocd_mww phys 0x01c21c28 0x00004000 Debug: 408 43677 command.c:145 script_debug(): command - mww ocd_mww phys 0x01c21c28 0x00004000 Debug: 410 43677 command.c:631 run_command(): Command failed with error code -304 User : 411 43678 command.c:669 command_run_line(): in procedure 'mww' I added some printfs to the jim_target_mw function, which showed that the function is never called. It's as if the binding is failing somehow. Any ideas? Best Regards Joel Holdsworth |