KW38 available memory with OTA client

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

KW38 available memory with OTA client

1,579件の閲覧回数
Honken
Contributor I

Hi,

Does anyone know how much free space there is left on KW38 running internal memory and included the OTA client feature?

regards,

0 件の賞賛
返信
2 返答(返信)

1,528件の閲覧回数
Honken
Contributor I

Ok, but how big is the ota client part that need to be included in the app? Is it allocating all of the 256k-bootloader?

regards,

0 件の賞賛
返信

1,565件の閲覧回数
nxf56274
NXP Employee
NXP Employee

Hi,

The client mcu flash memory has two parts -- bootloader + ota client. At first, the bootloader will go to ota client to communicate with your server. The server send data to client and the client writes data to flexnvm(256k). When transfer completely, the client will go to bootloader and erase the ota client. Write the flexnvm's data to flash. Then bootloader will go to new application. So if your new program doesn't have the ota function, this example can only use once. The flash memory you can use is (256k - bootloader).

 

Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 days after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 件の賞賛
返信