S32K144_RAppID_Bootloader_RBF_Files_Settings

cancel
Showing results for 
Search instead for 
Did you mean: 

S32K144_RAppID_Bootloader_RBF_Files_Settings

Jump to solution
509 Views
Narudol-T
Contributor III

Dear Sir,

I am using RAppID bootloader for S32K144 & MPC5744p for CAN-UART Flash.

However, I cannot find any release note of S32K144 settings parameters in " S32K144.rbf " file.

 

Ex;

Which CAN_PORT are they using ? Which Buad_Rate is conconfigured ?

What memory address map are allocated ?

 

Can you help point me the direction to the file_link ?

 

Best regards,

Narudol T.

0 Kudos
1 Solution
495 Views
mikedoidge
NXP Employee
NXP Employee

Hello,

I can share the following information:

Device

Communication supported

Device tested

RBF file

Boot-loader areas

CAN(500Kb/s)

UART(115200b/s)

S32K116

CAN0

(PTE4-PTE5)

UART0

(PTB0-PTB1)

PS32K116MLF- Q048

S32K116.rbf

0x00000000 - 0x00001FFF

S32K118

CAN0

(PTE4-PTE5)

UART1

(PTC8-PTC9)

PS32K118LAMLH

S32K118.rbf

0x00000000 - 0x00001FFF

S32K142

CAN0

(PTE4-PTE5)

UART0

(PTC2-PTC3)

PS32K142LAMLH

S32K142.rbf

0x00000000 - 0x00001FFF

S32K144

CAN0

(PTE4-PTE5)

UART0

(PTC2-PTC3)

PS32K144HFVLL-0N77P-Q100
PS32K144UAVLL-0N47T-Q100
PS32K144UAVLLA 0N57U-Q100

S32K144.rbf

0x00000000 - 0x00001FFF

S32K146

CAN0

(PTE4-PTE5)

UART1

(PTC6-PTC7)

PS32K146UAVLQ-0N73V

S32K146.rbf

0x00000000 - 0x00001FFF

S32K148

CAN0

(PTE4-PTE5)

UART1

(PTC6-PTC7)

PS32K148UAVLU-0N20V

S32K148.rbf

0x00000000 - 0x00001FFF

 

and

Device

Communication supported

Device tested

RBF file

Boot-loader areas

CAN

(500Kb/s)

UART

(115200b/s)

rchw

m_text

MPC5744P

CAN0

(PB0-PB1)

UART2

(PF14-PF15)

MPC5744P-FML09 1N15P

MPC5744P-FMLQ8 0N65H

PPG5744P-FMMM8 0N65H

MPC5744P.rbf

0x00F98000 - 0x00F98004

0x00F98008 - 0x00F9FFFF

 

Hope that helps!

 

Best Regards,

Mike

View solution in original post

5 Replies
496 Views
mikedoidge
NXP Employee
NXP Employee

Hello,

I can share the following information:

Device

Communication supported

Device tested

RBF file

Boot-loader areas

CAN(500Kb/s)

UART(115200b/s)

S32K116

CAN0

(PTE4-PTE5)

UART0

(PTB0-PTB1)

PS32K116MLF- Q048

S32K116.rbf

0x00000000 - 0x00001FFF

S32K118

CAN0

(PTE4-PTE5)

UART1

(PTC8-PTC9)

PS32K118LAMLH

S32K118.rbf

0x00000000 - 0x00001FFF

S32K142

CAN0

(PTE4-PTE5)

UART0

(PTC2-PTC3)

PS32K142LAMLH

S32K142.rbf

0x00000000 - 0x00001FFF

S32K144

CAN0

(PTE4-PTE5)

UART0

(PTC2-PTC3)

PS32K144HFVLL-0N77P-Q100
PS32K144UAVLL-0N47T-Q100
PS32K144UAVLLA 0N57U-Q100

S32K144.rbf

0x00000000 - 0x00001FFF

S32K146

CAN0

(PTE4-PTE5)

UART1

(PTC6-PTC7)

PS32K146UAVLQ-0N73V

S32K146.rbf

0x00000000 - 0x00001FFF

S32K148

CAN0

(PTE4-PTE5)

UART1

(PTC6-PTC7)

PS32K148UAVLU-0N20V

S32K148.rbf

0x00000000 - 0x00001FFF

 

and

Device

Communication supported

Device tested

RBF file

Boot-loader areas

CAN

(500Kb/s)

UART

(115200b/s)

rchw

m_text

MPC5744P

CAN0

(PB0-PB1)

UART2

(PF14-PF15)

MPC5744P-FML09 1N15P

MPC5744P-FMLQ8 0N65H

PPG5744P-FMMM8 0N65H

MPC5744P.rbf

0x00F98000 - 0x00F98004

0x00F98008 - 0x00F9FFFF

 

Hope that helps!

 

Best Regards,

Mike

492 Views
Narudol-T
Contributor III

Hi @mikedoidge 

 

Yes this helped a lot, thank you very much.

May I also ask more detail about device package ?

 

As I saw table include tested device as well.

For example S32K144 .... mostly are 100pin package.

 

But This bootloader also work with 48-64pin package as well, right ?

(As long as the PORT channel&number are correct)

 

Best regards,

Narudol T.

0 Kudos
487 Views
mikedoidge
NXP Employee
NXP Employee

Yes, you are correct. It works for the other pin packages, but wasn't specifically tested on them. So if the package contains the same ports then it leaves just the board design as the remaining factor.

Mike

481 Views
Narudol-T
Contributor III

HI @mikedoidge 

 

I see, may I ask another question as I saw you listed other S32K1xx device as well.

However, the bootloader utility have only S32K144 device.

How would I get those file/bootloader as well like S32K118 ?

 

Many Thanks,

Narudol T.

 

0 Kudos
462 Views
mikedoidge
NXP Employee
NXP Employee

Hello @Narudol-T,

There was some effort made some years ago to create a new version of the RAppID Bootloader, but it was never released. This version contained separate files for each member of a device family. This is why you see the separate filenames listed in the table I shared. The table is from a document that was created as part of this never released version, but it is useful in supporting questions from users, like yourself. The file for S32K144 should work just as well for S32K118. The differences between the devices should not impact the flash algorithm. The core and relevant peripherals are the same. The difference in UART ports (0 vs. 1) is due to the UART to USB connection on evaluation board. If you are using the S32K118EVB, then you would need to use UART1 instead of UART0 for the RAppID Bootloader. If you have a custom board, it would depend upon which UART was used to connect to the serial interface.

Hope that answers your question.

Mike

0 Kudos