RAppID Boot Loader Utility - additional info (MPC5744P)

cancel
Showing results for 
Search instead for 
Did you mean: 

RAppID Boot Loader Utility - additional info (MPC5744P)

548 Views
frend
Contributor I

Hi, I am using DEVKIT-MPC5744P board (latest openSDA firmware -> v1.10), S32PA v2017.r1 on win10. 
Bootloader ( MPC5744P.rbf ) provided with RAppID Bootloader Utility (v1.6.7.35) is flashed on uC.

There are 2 issues/questions:
1. I cannot load program using openSDA connection (even-thou it's clearly possible by others -> Model-Based design toolbox for example). Do you have any idea how to solve this ? I'm not using any of jumpers for boot configuration (J35,J34,J33 aka FAP/ABS2/ABS0) since bootloader utility doesn't use BAM. Other jumpers on board are also at default setup. I cannot even load program using external USB-UART converter on these pins (PD9/PD12 - when trying board is power with external 12V not usb !). Uart communication  for FreeMaster works OK using LinFlex1 and openSDA. :smileygrin:

2. Now I'm using external USB-UART converter to load program using LinFlex0 on pins PB2/PB3 and it works . What is strange is that there is none documentation on which of the units (LinFlex/FlexCan) are active and on what pin configuration when provided bootloader program is running . Is it possible to get this information?
e.g. :
Linflex0  - 115200 8N1 - PB2_PB3
Linflex1  - 115200 8N1 - PD9_PD12
FlexCan 0 - 100k - PB0_PB1  (?)

FlexCan 1  (?)

0 Kudos
1 Reply

185 Views
frend
Contributor I

For anyone that is having the same issues: problem is with bootloader program ( MPC5744P.rbf ) witch apparently uses LinFlex0 on PB2_PB3. To use  DEVKIT-MPC5744 with RAppID Boot Loader Utility (without external USB-UART converter)  you must flash to uC different .rbf file ( MPC5744P_DEVKIT.rbf ). Luckily for us NXP (Freescale) doesn't mentions it anywhere. Plus MPC5744P_DEVKIT.rbf file is only included in RappID Boot Loader Utility included in  Model-Based Design Toolbox.

My question about witch can/uart units and pins are configured in bootloader program still stands !

0 Kudos