Hi,

I can confirm that the flash reads and writes are working fine, even
at those high speeds.
I would suggest to merge these patches asap, they boost the flashing
speed, and debugging responsiveness tremendously!

Please see my other thread, I have completed a script for the lpc17xx
chips, probably needs a little bit more work, but if you say it is
okay, I'll upload it to gerrit (after I figure out how)

Please note that I have not yet contributed to this project, and have
no experience with gerrit and such.

Regards,
  Ákos Vandra

On 22 May 2012 02:38, Akos Vandra <[email protected]> wrote:
> and yeah, the lpc1768.cfg did not include reset config.
>
> On 22 May 2012 02:37, Akos Vandra <[email protected]> wrote:
>> I don't have an actual kt-link, but a clone designed by myself. The
>> LED is blinking :)
>>
>> On 22 May 2012 02:16, Andreas Fritiofson <[email protected]> 
>> wrote:
>>> On Tue, May 22, 2012 at 1:00 AM, Akos Vandra <[email protected]> wrote:
>>>> Hi Andreas,
>>>>
>>>> with interface kt-link.cfg, target lpc1768.cfg the command
>>>>
>>>> jtag_reset 0 1 gives:
>>>>
>>>> Error: BUG: can't assert SRST
>>>> Runtime Error: openocd.cfg:8:
>>>> in procedure 'program'
>>>> in procedure 'jtag_reset' called at file "openocd.cfg", line 8
>>>>
>>>> I checked the config file, it seems to be okay.
>>>
>>> I don't think that has anything to do with my driver. That message is
>>> printed from core.c before the reset command is even pushed to the
>>> driver. I'm guessing your reset_config somehow doesn't include srst.
>>>
>>> If you have the kt-link, can you check the LED blink? I haven't had a
>>> chance to try it.
>>>
>>> /Andreas

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to