S32K144 Unified Bootloader Configuration for CAN UDS Update

[padmaja]

Hi,

    I am working with the NXP Unified Bootloader source code on the S32K144 EVB using S32 Design Studio. My objective is to integrate the bootloader on the MCU and then update the application firmware via CAN using UDS . I would like to confirm whether any source files or configurations must be modified before flashing the bootloader. For example, set CAN parameters such as CAN IDs and baud rate, or modify HAL/driver porting files for the S32K144 EVB? Or can the bootloader be flashed and evaluated on the EVB as provided without any modifications?

After programming the bootloader, I would like to validate that it is running correctly and test application flashing over CAN. Could you please describe the recommended validation procedure, including how to force bootloader mode, how to confirm bootloader execution (for example via UART logs, CAN responses, or debugger), and how the bootloader jumps to the application ?

Additionally, I need guidance on how the application project should be built so that it works with the bootloader, including the correct application flash start address, linker settings, vector table location, and any startup code changes required. Finally, I would like to know the typical PC-side tools used for UDS flashing with S32K144  and recommended CAN interface hardware  for testing the Unified Bootloader over CAN.

[Julián_AragónM]

Hi @padmaja,

I’m sorry to say that Unified bootloader shared on the community is only unofficial demo provided AS IS with no guarantees and no support. Currently we do not have resources to support this demo. I will try to answer your questions through their documentation, but if follow-ups appear, please contact their support page instead.

The application can be flashed to the MCU and start testing the ECU-BUS functionalities. You do not need to modify the CAN IDs, baud rate, etc. You can refer to both Unified Bootloader – User Guide & their UDS Bootloader Implementation Guide.

CAN bootloader need to be downloaded into MCU prior using Open bus tool. This can be done through S32DS by compiling the project. You can also upload the elf/binary file, as mentioned in this community post: HOWTO: download separate elf/srec/hex file to microcontroller using S32 Design Studio.

Using Open bus tool, you can then download Application via CAN bus. PEAK CAN bus interface is supported. The APP project is included with the unified bootloader package.

There should be also JSON file which need to be loaded by the tool. This JSON file includes information about the flash driver (flash_api.bin) and APP firmware (APP firmware format can be S19/hex/binary). 

Best regards,
Julián