Problems with KinetisUpdater and Boot_Loader apps on KW01

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

Problems with KinetisUpdater and Boot_Loader apps on KW01

1,523 Views
fabricetocci
Contributor III

Hi folks,

I would like to serial flash the program on my product based on KW01 module.

I was able to generate and flash with IAR+Ijet the bootlaoder program on KW01 flash memory.

Then I tried flashing apps with Boot_Loader.exe. It works well with .hex file that load code on the first 16bits memory area.

But if the code is larger and needs 32bits addressing, Boot_Loader.exe displayes and logs errors like this

/*****************************  FROM LOG FILE ******************

Current time is 28/01/2016 14:38:39

The s19 file is: C:\Data\Fabrice\Kinetis\KW01_IEEE_802_15_4\app\ieee_802_15_4\Critt_auto\Coordinator\mrb-kw01z128_twr-rf\mrb-kw01z128_twr-rf MQXLite\Exe\user_app_green_blink_Large.hex

Station 1 is trying to enter Boot mode

Error 1 times!

Error 2 times!

Error 3 times!

**********************************************************************

Is there a Boot_Loader.exe that supports 32bits addressing???

Then I tried to use KinetisUppdater.exe from FSL_Kinetis_Bootloader_1_2_0

The device (KW01 board) is USB enumerated but never connect with Kinetis_updater.

Can I use Kinetis_Updater.exe with BootLaoder V1.0?

I hope, someone could provide support or advices.

Regards.

Fabrice

Labels (2)
0 Kudos
7 Replies

1,051 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Fabrice TOCCI:

Fan Yang is right that the KinetisUpdater.exe will only work with the protocol defined by KBOOT​. Unfortunately the KW01 is not supported by KBOOT so far.

You did not mention but I guess you are using the bootloader provided in the next document by colleague Jennie Zhang:

Kinetis Bootloader to Update Multiple Devices in a Network - for Cortex-M0+

The applications for KW01 cannot be loaded without first making some modifications to the linker file as explained in the section User application code and recompiling the project. The instructions are for CodeWarrior; if your application is based on IAR you need to make the corresponding changes (adding offset to vectors + text and reserving space in RAM).

Regards!

Jorge Gonzalez

0 Kudos

1,051 Views
fabricetocci
Contributor III

Hello Jorge,

You are right, I'm using the bootlaoder provided by Jennie Zhang.

This was a nice starting point for me.

I followed the steps described in the User Application Code. I did the changes, I recompiled with IAR

I can flash the bootloader and use the GUI tool included into Jennie pack (Boot_Loader.exe)

I can reflash the app with the files included into Jennie pack (user_app_green_blink.hex) for exemple. Because this app is very small and can fit in less than 64K flash

The problem with this GUI tool is with apps that need more than 64K of flash.

The GUI tool doesn't support 04, Extended Linear Address Record!!

What do I need to change in the GUI SW to support this option?

Regards.

Fabrice Tocci

0 Kudos

1,051 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Fabrice:

Unfortunately I do not know how that GUI works. Please add a comment with your question in the document post and I will send Jennie a message to see if she has an idea about this issue.

Regards!

Jorge Gonzalez

0 Kudos

1,051 Views
fabricetocci
Contributor III

Hello Jorge,

Thank you for your feed back.

Here are some more informations and the .hex files.

user_app_green_blink.hex is the 10K flash app that can be flashed with Boot_Loader.exe

MyWirelessAppCoordinator.hex is a 80K flash app that can't be flashed

An .hex file is a list of lines command with a specified syntax

A line can be describbed as :BBAAAATTHHHHHH.....HHHHCC

Where:

BB is the bytes number included in the line

AAAA is the absolute starting address of the line

TT defines the type

HHHH are the data

CC is the checksum

When the file includes data for a flash bigger than 64K, the file includes a line with a type TT equal to 04 for Extended Linear Address Record

When TT equals 04, the flash loader should move to the next 64K flash block.

.hex file extract, line with type 04 in bold

:10FFE000100001600F4A126880239A430D4B1A607B

:10FFF0000D4A12680D4B1340802252001A430A4BDF

:020000040001F9

:100000001A600B4A5062704700B50200002905D102

:100010000848036818000006C00F00E0002000BD7B

The GUI app included into BootLoader_SW pack doesn't support the TT type.

When a file that includes such line is selected for flash download, Boot_Loader.exe prompt an error message.

Hope you be able to find the root cause with this.

Kind  regards.

Fabrice Tocci

0 Kudos

1,051 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Fabrice:

Thank you for sharing this. But I meant to post this in the comments of Jennie's bootloader document:

Kinetis Bootloader to Update Multiple Devices in a Network - for Cortex-M0+

This way she will receive a notification and can revise your information. I can as well send her a heads-up email to give a check to your issue.

Regards!

Jorge Gonzalez

0 Kudos

1,051 Views
fabricetocci
Contributor III

Hello Jorge,

Thanks for the warning.

Now I added a post in the comments of Jennie's bootloader document:

Kinetis Bootloader to Update Multiple Devices in a Network - for Cortex-M0+

I'll follow with Jennie.

Thanks again for you suppoort.

Regards.

Fabrice Tocci

0 Kudos

1,051 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Fabrice:

Thank you for redirecting your question. I sent the email to Jennie but I just found she is on vacation.

Please have some patience on her response.

Regards!

Jorge Gonzalez

0 Kudos