Data write aborted for MKL17Z64VFM4 on LPU0

[jimmytseng]

Hi all:

I'm using MKL17Z64VFM4.

I have following problem when wrote a program.

command: blhost.exe -p COM3 -- write-memory 0 GPL1052.bin

Ping responded in 1 attempt(s)

Inject command 'write-memory'

Preparing to send 28500 (0x6f54) bytes to the target.

Successful generic response to command 'write-memory'

Data phase write aborted by status 0x5 Unknown error code (5)

Error: read_start_byte() timedout after 5.020 seconds

Response status = 10004 (0x2714) No response packet from target device.

Wrote 2624 of 28500 bytes.

How to check what is the problem?

Thanks!

Jimmy

[isaacavila]

Hello Jimmy,

I assume you are using Kinetis Bootloader and are trying to connect to Kinetis Updater through UART interface, aren't you?

If so, it seems to be a problem related to UART interface (maybe baud rate?), have you tried by using another protocol to communicate with Kinetis Updater: USB for example?

regards,

Isaac

[jimmytseng]

Hi Issac:

I am use Kinetis Bootloader  connect to Kinetis Updater through UART interface,

I try to baud rate 38400 is program OK.  I use  baud rate 57600 program fail. But reference recommend baud rate 57600.

[isaacavila]

Hello Jimmy,

Yes, It is recommended to use 57600 for baud rate, however, for KL17 autobaud is implemented on LPUART, so it should work well using different  baud rates, in fact, i tested FRDM-KL27Z and entering in ROM bootloader mode via UART and connecting using different baud rate values and it could connect correctly.

you can update your application when UART is configured to 38400 and you cannot when setting 57600, can't you?

Regards,

Isaac

[jimmytseng]

Hi Issac:

I agree with your opinion using different baud rate can connect correctly.

I have tried KL03, KL17 and KL22. I found KL03 and KL22 success rate is higher then KL17, but not 100% programming pass.

Say update application is blhost.

Thanks for your helps.

[isaacavila]

Hello Jimmy,

Have you tried by using another peripheral such as USB in order to see if problem is found only when UART is used? Also, there is a newer Kinetis Bootloader version (2.0.0), maybe you can test this version and see if problem are still presented. (Kinetis Bootloader|NXP )

Hope this helps,

Regards,

Isaac