LPC 822 ISP Write to RAM echoes correctly, but OK response never received!

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

LPC 822 ISP Write to RAM echoes correctly, but OK response never received!

ソリューションへジャンプ
1,959件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by schoeler on Mon Apr 11 17:39:15 MST 2016
According to 25.6.1.4 of LPC82X_UM10800, after a command with an acceptable address, length, and count is received, the LPC will respond with CMD_SUCCESS ("0").  At this point, the host then sends a length amount of bytes, and the LPC should respond with "OK<CR><LF>".

There have been some instances of the OK<CR><LF> not occuring, but no confirmation from NXP (for example, https://www.lpcware.com/content/forum/error-isp-lpc812-lost-characters-when-sending-bytes-too-fast-l... comment 14).  This is not listed in the Errata sheet Rev 1.1. 

Has anyone else seen this issue?

Even though there is no return code, a READ from the same location returns all the values I have sent.  So I know the data is in RAM, but there just seems to be no return code, contrary to what is stated in the manual.

Thanks.

ラベル(1)
0 件の賞賛
返信
1 解決策
1,554件の閲覧回数
andreasschnitze
Contributor II

Same here on a LPC15xx.

work around:

I verify the complete download with the ‘Read CRC checksum’ which is described in UM10736.

This could also be done with fractions on the ram address or related flash address after ‘Copy RAM to flash’.

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
1,555件の閲覧回数
andreasschnitze
Contributor II

Same here on a LPC15xx.

work around:

I verify the complete download with the ‘Read CRC checksum’ which is described in UM10736.

This could also be done with fractions on the ram address or related flash address after ‘Copy RAM to flash’.

0 件の賞賛
返信
1,554件の閲覧回数
lpcware
NXP Employee
NXP Employee
bump
0 件の賞賛
返信