Hello,
We made a custom boot loader software to load it via the BAM in UART Mode. We are testing it on the TRK-MPC650P Development Kit. Generally it works, but not always.
We are experiencing a strange issue with the BAM of the MPC560P MCU:
Anybody can help?
Thank you in advance
Solved! Go to Solution.
Hi,
ECC is enabled all the time. It can't be disabled. Single bit errors are automatically corrected and double bit errors are always reported - exception is triggered. All you can do is to enable/disable additional reporting in ECSM module. But you can't disable triggering of exception in case of double bit error. If you access the SRAM outside the downloaded image then I'm sure this is the root cause.
Lukas
Hi,
here is what comes into my mind:
1. The base address of downloaded code must be 0x4000_0100 or higher. It is not possible to use area 0x4000_0000 - 0x4000_00FF.
2. If it works when debugger was connected, it could be caused by watchdog or ECC errors in RAM. Have you disabled watchdog in your bootloader? The RAM memory is initialized when the BAM copies user code to RAM memory. If you want to use RAM memory outside this area (outside the image which is copied to RAM) then it must be initialized explicitly by SW.
3. If it helps, here you can find description how to create RAM image which is downloaded by BAM:
Re: Boot Assist Module (BAM) with FlexCAN MPC5604P
Lukas
Hi Lukas,
Thank you for the quick response.
I think, not initializing the memory outside the downloaded image is the issue - e.g. the stack, and might be related to #3 above. We are updating the boot-loader SW to initialize all RAM that is outside the downloaded image.
I will update again once we have a final confirmation .
Thanks again,
Zouhrab
Hi,
ECC is enabled all the time. It can't be disabled. Single bit errors are automatically corrected and double bit errors are always reported - exception is triggered. All you can do is to enable/disable additional reporting in ECSM module. But you can't disable triggering of exception in case of double bit error. If you access the SRAM outside the downloaded image then I'm sure this is the root cause.
Lukas
Thank you, Lukas!
We have updated the SW to initialize the RAM outside the downloaded image. It works!
Zouhrab