MC333771C TPL Init code breaks application code when using a bootloader

[Poley]

Hi all, I am trying to use a bootloader for my PCB which uses a S32K148. However, when running code from 0x3000 start location rather than 0x0000 due to the bootloder the app;ication code running on the MCU freezes when TPL initialization is triggered. I have tested this with the MC33771C config set to initialize at startup and the application code never progresses past the first call for INIT and resets every 3s due to the watchdog so I assume some clocks are still running but it just locks up the step time maybe?

I have also tested this with the code triggereing MC33771C INIT 1s after startup to prove this and when powered on the code runs fine for 1s until it gets the the MC33771C triggered INIT and just crashes the running code. This is extremely critical and would appreciate any help with this. I am assuming there is something in the SW driver that is now looking at a now BL section of memory or elsewhere. This is not an issue when using a single CMU through SPI. Only TPL.

Many thanks!

[JozefKozon]

Hi Poley,

please refer to the section 9.3 in the MC33771C full datasheet. The MC33771C must be initialized with a new CID value. By default CID is set to 0, and you need to change 

JozefKozon_0-1714631870120.pngJozefKozon_1-1714631964880.png

For the MC33771C an S32K144 MCU is recommended to be used.

We have an FRDM33771CSPEVB, S32K144EVB MCU board and BATT-14CEMULATOR. Please consider this EVBs for evaluation of the MC33771C. Please refer to the UM11402 attached. 

JozefKozon_2-1714632166323.png

We have a GUI (Graphic User Interface), which can be used for easy evaluation of the mentioned EVBs.

JozefKozon_3-1714632337345.png

With Best Regards,

Jozef

[Poley]

Hi @JozefKozon 

Thanks for the response!

I already have the S32k144 and s32k148 communication with multiple MC33771C boards. Both evaluation be custom boards. My issue is not the init routine for CID’s but more that when I use a custom linker script for my code to allow for a bootloader in the first segment of memory. As soon as I call the init function for the SW driver my application code crashes and stays frozen until I do a power cycle. So there must be something in the SW driver that I am missing that causes issues when there is a bootloader on the MCU.

thanks!

[JozefKozon]

Hi Poley,

thank you for additional information. According to your description, it looks to be an issue more of an IDE, than of the MCU or BCC (Battery Cell Controller). Which IDE you are using? Is it our S32DS? 

With Best Regards,

Jozef