MPC5xxx中的主题 Re: Serial bootloader example for MPC5634M

Serial bootloader example for MPC5634M

raphc63 — Sat, 12 Sep 2015 09:30:54 GMT

Hi everyone,

I recently bought a MPC563xM StarterTRAK Development Kit. MPC5634M is not supported by RAppID, that's the reason why I want to code my own bootloader for reading, erasing, and writing data on flasH.
Is there a documentation with simple examples of serial bootloader for MPC56xx or MPC55xx which are similar. It will be very helpful for me, this is the first bootloader I have to code.

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Mon, 21 Sep 2015 12:33:10 GMT

Hi,

take a look at:

https://community.freescale.com/servlet/JiveServlet/download/427962-279359/bootloader.zip

It is written directly for MPC5634M.

Regards,

Lukas

Re: Serial bootloader example for MPC5634M

raphc63 — Wed, 07 Oct 2015 16:18:19 GMT

Thanks Lukas. I try to understand this project but I have a question.

There are outstring generate by the main program like this example :

OutStr("\f\r\n**********************************************\r\n");

OutStr("\r\nMPC55xx/56xx Bootloader v1.0\r\n");

OutStr("\r\n**********************************************\r\n");

Where can I get this outstr on my PC ? And how can I answer to swich menu choice ? When I execute the program I have no control window.

Thanks

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Thu, 08 Oct 2015 07:17:34 GMT

Hi,

you need some kind of terminal emulation program like Microsoft HyperTerminal or similar. For example, I use this one (it is freeware):

https://sites.google.com/site/terminalbpp/Terminal20141030.zip

Then you need serial COM port on your PC or USB to serial bridge.

"And how can I answer to swich menu choice ?" - Just send a character from terminal to microcontroller...

Regards,

Lukas

Re: Serial bootloader example for MPC5634M

raphc63 — Thu, 08 Oct 2015 15:27:38 GMT

Ok thanks Lukas, this terminal works perfectly.

I tried the bootloader that you gave me and it works almost fine. In Codewarrior the baudrate for serial communication seems to be set to 115200baud

Or at this baud I had no communication. I used a logic analyzer and I found the effective baudrate is 80000 and now it works with Terminal. But I don't understand why the baudrate is less than 11500. Maybe my system clock is not set properly ? ( I don't change anything in the code and it supposed to be 80Mhz )

Also I have some random message error as you can see here ( I reset several time to show the random effect ) :

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Fri, 09 Oct 2015 04:57:17 GMT

Hi,

what is the crystal frequency on your board? It looks like you use 8MHz crystal, don't you? My application expects 12MHz crystal. There's note in InitSysclk function:

Sysclk = 80MHz running from PLL with 12 MHz crystal reference.

Change it to:

void initSysclk (void) {

FMPLL.ESYNCR2.R = 0x00000002;

FMPLL.ESYNCR1.R = 0xF0000028;

while (FMPLL.SYNSR.B.LOCK != 1) {}; /* Wait for FMPLL to LOCK */

FMPLL.ESYNCR2.R = 0x00000001; /* Fsys =80Mhz */

}

Then it should work.

Lukas

Re: Serial bootloader example for MPC5634M

raphc63 — Fri, 09 Oct 2015 11:38:57 GMT

Thanks it works well :smileywink: Yes I have a 8 Mhz crystal.

This code example will be a good start for me I have just to create a Reading flash function and use CAN instead of serial communication. Do you know if there are existing example project for MPC5634M or other MPC56XX of CAN communication function ?

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Tue, 13 Oct 2015 05:59:57 GMT

Hi,

basic SW example for CAN communication can be found in application note AN2865:

http://www.freescale.com/files/32bit/doc/app_note/AN2865.pdf

MPC5500 and MPC5600 Simple Cookbook Code

Regards,

Lukas

Re: Serial bootloader example for MPC5634M

alexvinchev — Mon, 25 Apr 2016 14:56:39 GMT

Hi lukaszadrapa,

is there any chance to find such example project for MPC5748G (for GHS if possible)?

In which way it should differ from boorloader for MPC5634M?

Regards,

Aleksandar

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Tue, 26 Apr 2016 04:41:22 GMT

Hello Aleksandar,

I do not have such project for MPC5748G.

The principle is still the same but rework is necessary, of course. What has changed is the memory map, the flash sits at another addresses. There's LINFlex module instead of eSCI, so the functions for serial communication must be changed. (FYI: I will share simple project which includes simple UART communication this or next week). The flash module is different. If it helps, I already shared these two examples for flash programming:

Example MPC5748G Flash RW

Example MPC5748G Flash RW SSD

Lukas

Re: Serial bootloader example for MPC5634M

alexvinchev — Tue, 26 Apr 2016 05:39:35 GMT

Hi Lukas,

I really appreciate your guidance. The two projects for Flash R/W will help of course.

Flash partitioning is bothering me more, this was the reason to ask for example. There are quite much different flash regions and sizes, from where I should pick some part, but which exactly... If you can say few words regarding this, will be very helpful.

Regarding the UART, I've already ported ChibiOS RTOS with CAN & UART drivers (based on AN4830 examples) on MPC5748G, so there is no need to hurry (for me), I think I'll handle UART communication by myself.

Regards,

Aleksandar

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Tue, 26 Apr 2016 07:00:10 GMT

In case of MPC5634M, there were following options where to put boot header (RCHW):

In the example project, I allocated first 64KB for bootloader and the rest of flash for application. That means the RCHW for bootloader is at address 0x0000_0000, for application at 0x0001_0000.

In case of MPC5748G, we can put boot header at:

So, boot header for bootloader can be placed at 0x00F8_C000. If 80Kb is enough for your bootloader, you can place boot header for application at 0x00FE_0000 (or any other, depends on you). Then you have to change the linker files accordingly.

Next point is the Read-While-Write (RWW) partitioning on flash. As you know, we can't access the flash partition which is currently being programmed or erased. The code must run from another partition or from RAM. Here is the partitioning of MPC5748G flash:

The disadvantage is that the partitions do not create continuous space (for example, partition 0 is split to four non-continuous sections), so we have to be careful where to run the code from to avoid RWW issues.

If you need anything else, just let me know...

Lukas

Re: Serial bootloader example for MPC5634M

alexvinchev — Tue, 26 Apr 2016 09:55:33 GMT

Thank you very much Lukas!

Very helpful advice (again)!

I think I'll sacrifice 0x74000 bytes till 0x01000000 for bootloader and the rest will be for application. This way I'll have no worries regarding RWW issues, because my application will always reside in partitions 6-9 and never touch partitions 0-3.

Does this sounds like a good idea to you?

In case I want to debug application without bootloader, I will use dedicated link file, which will place the boot record in the search area of BAF.

Aleksandar

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Tue, 26 Apr 2016 10:56:50 GMT

Yes, that's a good idea. If you don't have memory constraints, this is the best option.

Lukas

Re: Serial bootloader example for MPC5634M

buraksoner — Thu, 16 Jun 2016 18:12:08 GMT

Hello Lukas,

Although this project seems to be written for MPC5634M (which contains the C90LC, right?), the SSD seems to be for the C90FL flash module. I've concluded this after I saw the EraseFlash function was trying to "enable" (I guess that means select-for-erase?) blocks which are signified by bits 22-23 of the LMSR.

unsigned char EraseFlash(void)

{

shadowFlag = FALSE;

/* Erase all blocks (except area occupied by bootloader) in low and mid addr space of flash array 0 */

lowEnabledBlocks = 0x000003F8;

0x000003F8 -> bits 22->28 are set.

Screenshot from ref manual below:

Also, of course, there are some other differences between the C90FL and the C90LC.

Am I correct in this analysis?

I've downloaded the "MPC56xx C90LC Flash Standard Software Driver (REV 1.0.3)" from NXP software center but inside it the user manual states that the document is prepared for C90FL devices! Is the API for C90FL and C90LC really the same?!

If not, where can I find the SSD explicitly for C90LC?

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Fri, 17 Jun 2016 05:17:20 GMT

Hi,

API of SSD drivers is the same for C90LC and C90FL.

There's C90LC flash on MPC5634M. C90FL was used on first revisions (prototypes) of chip. Regarding appendix, there's note in Table A-2:

"MPC56xx C90LC Flash Standard Software Driver (REV 1.0.3)" - Yes, this one should be used.

To find correct SSD drivers for a device, find the web page of device, for example:

MPC563xM|32-bit MCU|Powertrain|NXP

MPC564xL|32-bit MCU|Chassis-Safety|NXP

Then go to "Software & Tools" tab:

Then search for "Middleware - Device Drivers":

And here you can find the drivers for the device:

Regards,

Lukas

Re: Serial bootloader example for MPC5634M

buraksoner — Fri, 17 Jun 2016 06:05:02 GMT

Lukas,

Thanks for the explanation.

One humble suggestion: Perhaps, the fact that the SSDs are the same for C90LC and C90FL can be stated somewhere accesible. As the SSDs are just a bunch of hex numbers in c-files or srecords, no conclusion can be made by just comparing drivers obtained from two different sources -> I've compared the API c-files (which contain just arrays made up of some hex numbers which respresent the API functions) under the "SSD_driver" folder in the serial bootloader example to all of the "c-array_driver" files provided under all (cw, diab, ghs) and (BookE and vle) combinations in the SSD v1.0.3 provided from the NXP website and none are matching..

Regarding your answer, I assume there would only be some cosmetic changes which result in different hex numbers in those c-files but nothing functional is different. Am I correct?

Thanks for the help,

Burak

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Fri, 17 Jun 2016 07:43:14 GMT

It is mentioned in document which I attached to the bootloader:

When you download the drivers, the package always contains user guide and release notes, so I think it's enough.

Instead of comparing the c-arrays, it is much better way to download appropriate drivers and use them in your project.

Lukas

Re: Serial bootloader example for MPC5634M

bjrajendra — Wed, 08 Nov 2017 09:42:39 GMT

Thanks Lukas,

It's a kick start for me to start the bootloader module. One thing confirm me.

1) Once the user application deletes the Key, and after reset, bootloader program will execute. During the bootloader project execution, as the key was deleted by the previous user application, Immediately after the completion of program code we need to add key 0xFFFF0000FFFF0000ULL has to be loaded back to address 0x0017FFF8. Is it right?

Because the bootloader project you provided doesn't have this part of the code.

Thanks,

Raju

Re: Serial bootloader example for MPC5634M

lukaszadrapa — Wed, 08 Nov 2017 14:36:36 GMT

Hi,

this is should be part of project for user application. You can find in main.c:

/* constant in flash used to start the bootloader/user application */
#define BOOT_KEY_ADDRESS    0x0017FFF8UL
#define BOOT_KEY                    0xFFFF0000FFFF0000ULL
#define DESTROY_BOOT_KEY    0x0000000000000000ULL

/* Set a constant in flash - BOOT_KEY for bootloader.
"key" is added to FORCEACTIVE section in linker file to ensure
that the constant is not stripped by the linker */
#pragma push
#pragma section all_types ".__key_segment" ".__key_segment"
unsigned long long key = BOOT_KEY;
#pragma pop

And then at the end of *.mot file:

S30D0017FFF8FFFF0000FFFF0000E8

So, the key is programmed to flash by bootloader together with other data...

Regards,

Lukas