Kinetis Microcontrollers中的主题 Re: Kinetis Flash Tool with an Update image failure (cumulative write)

Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Thu, 13 Jul 2017 07:46:11 GMT

Hi all,

I successfully ported the KBOOT V2 from the TWR-MKV58F22 Bootloader to my MKV58F1M0VLL24 MCU on a custom board (Using KDS V3.2). Neraly everything is working as expected, except a strange update-behaviour with the KinetisFlashTool.

Updating my application binary to the target address sometimes succeeds and sometimes fails with the kStatusMemoryCumulativeWrite errormessage. I observerd this behaviour especially then, when there is already an application binary on the target flash, which I am going to erase and replace with my new application (in my example, the new application binary is the same binary as the one already placed on the flash... I just want to test everything to avoid later upcoming bugs, so the content of my binary shouldn't be of interest). When the error message occurs, I try to erase the whole flash memory in order to prevent cumulative memory writing as mentioned in the MCU's reference manual. Since now, every time I erased the whole memory, the KinetisFlashTool just responded with "Erase all memory of internal flash. Completed!", so I expected the erasing to be successful.

Nevertheless after trying to Update my "new" application binary to the "freshly erased flash memory", the same cumulative write error occurs. The only workaround for this problem is to reset the device via the KinetisFlashTool followed by normally clicking the Update Button...

After this procedure, when I reset the device, connect to KinetisFlashTool and try to Update the application binary again, the already mentioned error occurs again. And again, erasing the whole flash memory doesn't help at all.

Since I didn't found any similar question about this, I am wondering if I am missing any important step while updating my application binaries?

I would really appreciate some help to understand what is going wrong with the updating procedure on my MCU...

With kind regards,

Julian

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Fri, 14 Jul 2017 02:25:38 GMT

Hello Julian Schork,

When you use the KinetisFlash Tool, please select the erase all to unlock, just like the following picture:

Then try it again.

If you still have problem, please also attach the problem picture about your kinetisFlash Tool.

Have a great day,
Kerry

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

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Fri, 14 Jul 2017 06:54:04 GMT

Hello Kerry Zhou,

thank you for your quick response!

Unfortunatelly using the "Erase All to Unlock" Feature doesn't solve the problem. As mentioned before, even erasing the whole memory (starting from application address) before updating my binary doesn't solve this issue. I attached a screenshot of the Kinetis Flash Tool where the error occured.

Restarting the device via the "Reset" Button in the Kinetis Flash Tool solves the issue for the moment, but the next time I am trying to update my binary, the same error occurs. Additionally, closing the KinetisFlashTool also resets the device, so starting the KinetisFlashTool again causes the needed reset to update my binary as well. I attached you another two pictures where I first ran into the error and then solved the issue as mentioned.

Do you have any further suggestions to solve this issue?

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Mon, 17 Jul 2017 08:04:13 GMT

Hello Julian Schork,

It seems your porting code missed something.

Could you do the debug in your bootloader? then check when the problem happens, where the code is stopping?

Have a great day,
Kerry

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Mon, 17 Jul 2017 12:17:24 GMT

Hello Kerry Zhou,

Thanks again for your support.

I found something really peculiar while debugging the bootloader up to the point where the "mem_is_erased"-Check fails.
In the function mem_is_erased (memory.c), the bootloader checks whether the flash from the application start address is really erased (all the bits set to 1).

Considering the General Registers, the Memory and instructionswise stepping through the code, the following occured:

in the disassembly at 100059ac, the address is loaded to the r3 register which you can see in the General Registers (lighted yellow in the picture below)

in the next step at Disassembly 100059ae the value at the address, stored in r3 should be loaded to the r3 register. This is where the problem occurs. If you take a look at address 1000A000 in the lower section of the picture, you see that the value is FFFFFFFFF... But if I take one step further:

You can see that in r3 the value 0x0 is stored. Of course this causes the condition (*start != 0xFF) to be true, ending in the isMemoryErased = false problem.

Additionally I want to mention that taking a look at the sourcecode at the same time (e.g. with the help of the Variables View), the variable content seems correct, because start = 0x1000a000 and *start = 0xff. Nevertheless the condition is said to be true... (in the below picture, the "Variables View" shows the source code variables at the debug-point in the picture above at isMemoryErased = false;)

Does this make any sense to you?

I already checked the errata-sheet, but there is no similar issue...

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Tue, 18 Jul 2017 01:53:19 GMT

Hello Julian Schork,

Thank you for your effort.

Now, check these points:

1. the IDE project optimization

Select the optimization level to none, and try again.

2. Check the C code address, and start, whether the address is correct. Do it step by step, whether the address will jump to the abnormal area.

3. After build, please check the bootloader code size, make sure it is not exceed to the application address.

Any updated information, please let me know!

Have a great day,
Kerry

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Tue, 18 Jul 2017 07:36:30 GMT

Hello Kerry Zhou,

I really appreciate your fast support!

The compiler optimization was already turned off...

After building the bootloader(debug build), the bootloader codesize is at 37.380 bytes (text-section for application code):

arm-none-eabi-size --format=berkeley "MKV58F1M0VLL24_Bootloader.elf"
text data bss dec hex filename
37380 364 5120 42864 a770 MKV58F1M0VLL24_Bootloader.elf

By way of comparison, the bootloader codesize of the release build is way smaller because of compiler optimization in size (-Os):

arm-none-eabi-size --format=berkeley "MKV58F1M0VLL24_Bootloader.elf"
text data bss dec hex filename
22620 356 5088 28064 6da0 MKV58F1M0VLL24_Bootloader.elf

Nevertheless, the Problem occurs in both builds.

By the way, this is the MEMORY specification of my bootloader:

MEMORY
{
m_itcm                (RX) : ORIGIN = 0x00000000, LENGTH = 0x00010000
m_interrupts          (RX) : ORIGIN = 0x10000000, LENGTH = 0x00000400
m_flash_config        (RX) : ORIGIN = 0x10000400, LENGTH = 0x00000010
m_text                (RX) : ORIGIN = 0x10000410, LENGTH = 0x000FFBF0
m_data                (RW) : ORIGIN = 0x20000000, LENGTH = 0x00020000
m_ocram               (RW) : ORIGIN = 0x2F000000, LENGTH = 0x00010000
}

and this is the one for my application:

MEMORY
{
m_data                (RW) : ORIGIN = 0x00000400, LENGTH = 0x0000FC00
m_interrupts          (RX) : ORIGIN = 0x1000A000, LENGTH = 0x000003C0
m_bca                 (RX) : ORIGIN = 0x1000A3C0, LENGTH = 0x00000040
m_text                (RX) : ORIGIN = 0x1000A400, LENGTH = 0x000F5C00
m_data_2              (RW) : ORIGIN = 0x20000000, LENGTH = 0x00020000
m_data_3              (RW) : ORIGIN = 0x2F000000, LENGTH = 0x00010000
}

In addition, BL_APP_VECTOR_TABLE_ADDRESS is set to 0x1000A000, which suits the address stated in the Kinetis Flash Tool.

Do you see any further possible problem sources?

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Tue, 18 Jul 2017 07:51:04 GMT

Hello Julian Schork,

In debug mode:

Relocate the app address to 0X1000C000, because the generate code size is a770 , it is larger than 0XA000.

Please modify both bootloader and app address to 0X1000C000, then try agian, and debug, whether the former problem still happens, and also check the mem_is_erased function, whether the address jump still abnormal?

Have a great day,
Kerry

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Tue, 18 Jul 2017 08:00:39 GMT

Hello Kerry Zhou,

I adapted the app address to 0x1000F000 to give the bootloader more space than even needed. Sadly this doesn't change anything in the behaviour while updating the application binary...

Bootloader Memory specification:

Application Memory specification:

MEMORY
{
m_data                (RW) : ORIGIN = 0x00000400, LENGTH = 0x0000FC00
m_interrupts          (RX) : ORIGIN = 0x1000F000, LENGTH = 0x000003C0
m_bca                 (RX) : ORIGIN = 0x1000F3C0, LENGTH = 0x00000040
m_text                (RX) : ORIGIN = 0x1000F400, LENGTH = 0x000F5C00
m_data_2              (RW) : ORIGIN = 0x20000000, LENGTH = 0x00020000
m_data_3              (RW) : ORIGIN = 0x2F000000, LENGTH = 0x00010000
}

BL_APP_VECTOR_TABLE_ADDRESS set to 0x1000F000...

Kinetis Flash Tool targer address: 0x1000F000

I also checked he mem_is_erased function... the behaviour is still abnormal.

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Tue, 18 Jul 2017 08:07:24 GMT

Hello Julian Schork,

When you debug mem_is_erased , could you check the address, and start in the function mem_is_erased, and give me the step by step, until the problem happens picture?

Have a great day,
Kerry

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Tue, 18 Jul 2017 08:25:13 GMT

Hello Kerry Zhou,

these are the step by step screenshots when the error occurs:

Again I would like to mention, that this error doesn't occur after resetting the device and connect it again... Only if I update the binary, connect again to the bootloader and try to update again, the error occurs until I again restart the device.

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Tue, 18 Jul 2017 08:37:30 GMT

Hi Julian Schork,

Thank you for your details!

You said: "Again I would like to mention, that this error doesn't occur after resetting the device and connect it again... Only if I update the binary, connect again to the bootloader and try to update again, the error occurs until I again restart the device."

Do you mean, you already download an app before, then connect it again, and try to download the new app, it will have problem?

After you download the app, do you try to power off the board, then power on it again, then connect to the kinetisflash Tool, whether this situation have problem?

Have a great day,
Kerry

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Tue, 18 Jul 2017 08:41:21 GMT

picture 12 and picture 13 is really very strange.

start address is 0x1000f000, the data is 0xff, but in the asm, it makes the data as 0.

I also need time to do the consideration.

Could you share your modified bootloader to me?

Have a great day,
Kerry

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Tue, 18 Jul 2017 08:49:58 GMT

Hello Kerry Zhou,

you are right. I download the app and after that run the bootloader again and download the app.

Powering on and off also doesn't change anything. If I restart the device then, the error is gone until I repeat the steps.

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Tue, 18 Jul 2017 08:56:18 GMT

Hello Kerry Zhou,

here is my bootloader porting...

Thanks again very much for your support!

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Tue, 18 Jul 2017 09:05:02 GMT

Hello Kerry Zhou,

I want to make an other addition:

when I try to update my application and the update fails with the cumulative write error, I can't access my application again (which is what I expect, because it should be erased)... so it should all depend on this strange behaviour of the asm code.

With kinds regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Tue, 25 Jul 2017 07:51:04 GMT

Hello Kerry Zhou,

do you have any news regarding the flashing-problem?

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Tue, 25 Jul 2017 08:06:13 GMT

Hello Julian,

Really so sorry for my later reply because of overloaded before.

Your question, I need to contact with our according department, so I still need time to give you feedback.

I will work on it ASAP, please wait patiently, thank you.

Have a great day,
Kerry

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

SMNJS — Fri, 11 Aug 2017 15:12:17 GMT

Hello Kerry,

I would like to let you know that I tested an other custom board with the MKV58F1M0VLL24 MCU and the ported bootloader. The flashing-problem occured on the second board with the second MCU as well, so it doesn't seem to be an individual case...

Do you have any news for me so far?

With kind regards,

Julian Schork

Re: Kinetis Flash Tool with an Update image failure (cumulative write)

kerryzhou — Tue, 15 Aug 2017 08:46:59 GMT

Hi Julian,

Thank you for your updated information, I think there still have some problem in the software, not the hardware.

Now, after discuss this question to my colleagues, could you help to do these test?

1. KDS memory checking, not variable

The following picture is the debug result from your side:

Just like this:

The same debug position in your picture, check memory, just to make sure the 0X1000F000 is 0XFF or not? Our IDE department also need this data.

2. Please try to use the blhost to download the application code

You can find blhost in folder:NXP_Kinetis_Bootloader_2_0_0\bin\Tools\blhost\win

You can refer to document: Kinetis Bootloader Demo Application User's Guide.pdf, page 7, chapter 4 The host utility application.

This document can be found in :NXP_Kinetis_Bootloader_2_0_0\doc

If you use this step by step downloading, whether you have the same question?

Because I don't have the MKV58F1M0VLL24 board, I can't test it directly on my side.

Have a great day,
Kerry