MSPM0L1106: UniFlash with error : Data Block Size less than 1KB!!! Verification Failed for Datablock at0x9F00

Hi Alan,
This seems to be an alignment issue. I would recommend to check your linker file (.cmd,) and make sure you are using the palign command. You can follow the image bellow as an example:

Best Regards,

Diego Abad

Hi Diego Abad,

I am sorry to tell you that my linker file (.cmd) is auto generated from .syscfg file. Is there something wrong?

AlanC.

Hi Alan,
Can you share the .cmd file syscfg generates?

Best Regards,

Diego Abad

Hi Diego Abad,

It seems I cannot attached the .cmd file here. I capture the screen of it for your reference.

FYI, it seems my firmware still can run even with the error displayed after the firmware downloaded by bootloader. 

However, I am not sure about it. Is there any tool or can UniFlash (bootloader mode) to verify the memory in device vs the hex file?

AlanC.

Hi Alan,
I noticed a difference in the default value in the BCR_CONFIG length in your .cmd file compared to the default cmd file. Can you change the value from 0x00000080 to 0x000000FF in the BCR_CONFIG section? As for the tool question, there is a Memory browser option that should show the device's memory.

Best Regards,

Diego Abad

Hi Diego Abad,

I modified the .cmd file according to your suggestion. However, I compared the hex and map files generated. The hex file is same as before and the map file only changed the modifed line about BCR_CONFIG. All the other are same, so the error is still occurred.

About the BCR_CONFIG, should the modified the lenght be 0x100 instead of 0xFF?

For the tool question, is there any feature to verify the device memory vs hex file? The memory browser that you mentioned seems just display the memory for human reading only.

AlanC.

Hi Alan,
Let me consult with my team about this.

Best Regards,

Diego Abad

Hi Alan,
I confirmed with my team that the error you are seeing is a bug. The program should run even when the error shows up. This will be fixed in future release of UNIFLASH. As for the device memory vs hex file verification, this process happens in the background. 

Best Regards,

Diego Abad

Hi Diego Abad,

Thank you for your confirmation.

Can you help to request the features that can verify the device memory with provided firmware file, eg. hex and etc.

And able to dump the device memory into a file.

AlanC.

Hi Alan,
You can dump or "capture" the device memory using the Memory Browser. As for the previous one, this happens in the background. Is there something else you mean by device memory and hex verification?

Best Regards,

Diego Abad

Hi Diego Abad,

Thank you for your reply.

I tried the Memory Browser, and failed resulted. Can you help to give me some suggestion on following questions about the Memory Browser:
1. As I did not set any password, the default password is 32 0xFF, isn't it?
2. With 32 0xFF password, start address=0x00, length = 0x10000, The error messages are resulted : "[ERROR] CORTEX_M0P: [ERROR]Memory readout disabled in BCR Configuration!". What is the problem and how to resolve it?

For the "device memory and hex verification", what I mean is that the feature will read the firmware file, eg. hex, bin and etc, and compare with the device's program memory without program it and provide the result whether they are match or not. If more analysis result on their mis-match will be the best, eg. memory compare window side by side. This is only my suggestion only.

AlanC.

Hi Alan,
1. You are correct

2. Does the error appears when you try to read the memory using the Memory Browser at that specific address?

I'll let the software team know about your suggestion.

Best Regards,

Diego Abad

Hi Diego Abad,

Yes, error appears when I tried to read the memory using the Memory Browser. But the address seems normal. I set the start address to 0x00000000 as below. However, it always reported "Process is failed!" on today testing. Is the setting are wrong?

AlanC.

Hi Alan,
For some reason there is not a memory browser tab there. However, what is happening right now it's that the bootloader invocation is failing. I will try doing it manually (match BSL Invoke pin to whatever logic you enabled to be invoked.)

Best Regards,

Diego Abad

Hi Diego Abad,

Thank you for your support. For your info, I set the DUT to BSL already on each of my test.

AlanC.

Hi Alan,
That seems weird since the error appears to show otherwise. What address were you using before that allow you to write in Flash without any problems?
Best Regards,
Diego Abad

Hi Diego Abad,

I did not success to use Memory Browser to read memory before. For the firmware that I download to device, the memory is generated by SYSCFG. The following is the cmd for your reference.

AlanC.

Hi Alan,
This seems to be the BOOTLOADER version for UNIFLASH. In this case, the absence of the memory browser makes sense (I also don't see a memory browser option.) Let me ask the software team about it.

Best Regards,

Diego Abad

Hi Alan,
Can you mention to me the method you are setting your password? I also will recommend to look over the MSPM0 Bootloader (BSL) Implementation (Rev. C)

Best Regards,

Diego Abad

Hi Diego Abad,

About the password, I did not configure them and leave it as default. The following is the setting of SYSCFG. Am I need to do some configuration?

About the document, I had a read some time ago and I'll review it again later. 

AlanC.

Hi Alan,
Thanks for letting me know. I'll investigate further on Monday.

Best Regards,

Diego Abad