Ups. After fixing my script, reset now works.
However, I still get the following error. It looks like it finds the chip
for a while, but then it gets a read error, after which it finds it again:
Info : CMSIS-DAP: FW Version = 1.0
Info : SWCLK/TCK = 0 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : Connecting under reset
Info : DAP_SWJ Sequence (reset: 50+ '1' followed by 0)
Info : CMSIS-DAP: Interface ready
Info : clock speed 1000 kHz
Info : IDCODE 0x0bc11477
Info : MKL25Z128VLK4.cpu: hardware has 2 breakpoints, 2 watchpoints
Error: CMSIS-DAP: Read Error (0x04)
Polling target MKL25Z128VLK4.cpu failed, GDB will be halted. Polling again
in 100ms
Polling target MKL25Z128VLK4.cpu succeeded again
Error: CMSIS-DAP: Read Error (0x04)
Polling target MKL25Z128VLK4.cpu failed, GDB will be halted. Polling again
in 100ms
Polling target MKL25Z128VLK4.cpu succeeded again
Error: CMSIS-DAP: Read Error (0x04)
Polling target MKL25Z128VLK4.cpu failed, GDB will be halted. Polling again
in 100ms
Polling target MKL25Z128VLK4.cpu succeeded again
Error: CMSIS-DAP: Read Error (0x04)
Polling target MKL25Z128VLK4.cpu failed, GDB will be halted. Polling again
in 100ms
Polling target MKL25Z128VLK4.cpu succeeded again
Error: CMSIS-DAP: Read Error (0x04)
Polling target MKL25Z128VLK4.cpu failed, GDB will be halted. Polling again
in 100ms
Polling target MKL25Z128VLK4.cpu succeeded again
- Thomas
On Thu, Sep 19, 2013 at 11:21 AM, Spencer Oliver <s...@spen-soft.co.uk>wrote:
> On 19/09/13 17:34, Thomas Schmid wrote:
>
>> Yes, the above binary locks oocd out. However, using the mbed tool I can
>> still flash the board (with the drag and drop method).
>>
>> I agree, it "should" be open-drain. There is a 10k pullup, but clearly
>> on my board something fights against it. Maybe the app configures that
>> I/O line with a pull-down? I will add a stronger pull-up to see what
>> happens.
>>
>> I also have to retract my earlier statement. I still had that small
>> patch that forced the rst line down in my code. That's what made the rst
>> line toggle. I attached my openocd.cfg file. All I do to run openocd is:
>> openocd -f openocd.cfg
>>
>> I saw that you added a LOG_INFO statement if we connect under reset. I
>> don't see that one in my output:
>>
>>
> because your reset_config line is incorrect, try
>
> reset_config srst_only srst_nogate connect_assert_srst
>
> Spen
>
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
