Hi,
Yes, rappid software should be still usable for S32K144.
There are several issues that may end-up with the error message you posted.
1) make sure the rbf file is programmed in the target system (over jtag)
if the device is erased with only rappid bootloader and there is no Application loaded the bootloader waits infinite time waiting for data over SCI/CAN.
If you already programed an app with bootloader header there is typically few second timeout (this is configurable). So if you do not initiate s-record transfer before timeout you get this error message.
2) The Rappid botlader firmware (.rbf) uses specific pinmux configuration so it works typically with NXP EVBs (e.g. S32K144EVB)
If you have a custom board with different pins used to communicate via SCI you cannot use existing rbf. You might try to use an alternative if it is available:
https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/RAppID-Bootloader-custom-rbf-files/ta-...
Hope it helps.
Stan
