KW38 - having a problem from reprogramming a KW38 device using the OTAP Client Software

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

KW38 - having a problem from reprogramming a KW38 device using the OTAP Client Software

Jump to solution
1,581 Views
Lincoln
Contributor III

Hi, 

I am trying to use OTAP Client Software to reprogram kw38, and I referred to this document :KW38 - Reprogramming a KW38 device using the OTAP Client Software 

After I done all the process ,the app shows that transfer successfully.

But kw38 EVB didn't work as expected, instead, it was acting like this:

S__30670850.jpg

What should I do?

 

Thank you for your help!

Labels (1)
0 Kudos
1 Solution
1,516 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi @Lincoln,

Please look at your memory regions, you did not change location of flash and the NVM_region.

mario_castaneda_0-1640280946357.png

Please change the regions as the image below.

mario_castaneda_1-1640281005062.png

Regards,

Mario

 

 

View solution in original post

0 Kudos
7 Replies
1,567 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi @Lincoln,

What is the SDK version that you are working on?

Are you working with the internal or external flash?

Did you disable the low power mode in the image that you are sending?

However, I followed the same process working with the SDK version 2.6.12 and the external flash as default.

Is it possible that you could use the same S19 file created with the OTA ATT example?

Note: After the OTA process you have to wait some seconds for the bootloader to copy the new image to flash.

Regards,

Mario

 

0 Kudos
1,557 Views
Lincoln
Contributor III

Hi @mario_castaneda,

I am working with SDK version 2.6.12 and the external flash as default.

I followed the same process and also the same S19 file created with the glucose_sensor_freertos example.

Besides, I already disable the low power mode in the glucose_sensor_freertos example. 

After the OTA process I was waiting at least 3 mins but the problem still exist.

 

Then I am trying to work with internal flash, some error exist during debug process:

otap_error.png

 

Thank you.

  

0 Kudos
1,535 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi @Lincoln,

I am really sorry, I am working with the 2.6.14 version.

Is it possible that you could use the OTA Bootloader and the OTA Client ATT example as default?

After that, please look at the file attached S19 file and test with your phone.

Please let me know your findings.

Regards,

Mario

0 Kudos
1,528 Views
Lincoln
Contributor III

Hi @mario_castaneda,

I upgrade my SDK version to 2.6.14 and try again as using the OTA Bootloader and the OTA Client ATT example as default.

I found that the test is successful as using your attached S19 file while that would fail with my own generated S19.

I'm confused and don't know what I did wrong because the process I generated the S19 file which is exactly following the document.

The attached file is the example project I am working with, please check it!

 

Thank you!

 

0 Kudos
1,517 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi @Lincoln,

Please look at your memory regions, you did not change location of flash and the NVM_region.

mario_castaneda_0-1640280946357.png

Please change the regions as the image below.

mario_castaneda_1-1640281005062.png

Regards,

Mario

 

 

0 Kudos
1,499 Views
Lincoln
Contributor III

Hi @mario_castaneda,

it works after I change the memory region, thank you very much!

679 Views
leonordo
Contributor I
Why does debug report an error when I modify the flash size according to the image?
error message:
Error in final launch sequence:

Failed to execute MI command:
-target-download
Error message from debugger back end:
Load failed
Failed to execute MI command:
-target-download
Error message from debugger back end:
Load failed
Load failed
0 Kudos