Getting Started Porting U-Boot to M5329EVB board
Hi,
I'm getting started porting U-Boot to the Freescale/LogicPD M5329EVB board, based on the ColdFire MCF5329 processor. As suggested in the "U-Boot Porting Guide" in the README file, I've subscribed to this list, and I'm admitting I am (currently) clueless - hence this email!
At this point, my only real question is this - has anybody done this already? If so, can/will you share? Or are you working on a similar port, and would you like to share the load? I'm very open to working with others on this, though if there are no takers, I'll go it alone and post it all later.
Thanks, and take care,
-Bob
Hi Bob,
Quoted 7 lines · Robert S. Grimes
I'm getting started porting U-Boot to the Freescale/LogicPD M5329EVB board, based on the ColdFire MCF5329 processor. As suggested in the "U-Boot Porting Guide" in the README file, I've subscribed to this list, and I'm admitting I am (currently) clueless - hence this email!
At this point, my only real question is this - has anybody done this already?
I have not head of a MCF5329 U-Boot port. You are aware that the MCF52x2 CondFires are supported? So this should be your starting point. Grep for "MCF52" in include/configs/* and you will see what boards are available with this CPU's.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20070503/a3ed9e52/attachment.htm
Hi Stefan,
Yes, I am, and that is where I've started. I currently have got a simple copy to compile cleanly, but none of the device-specific code has been checked to see if it needs to be modified.
Any hints as to where I should start? For example, I'm guessing the serial port is rather important, right? But do I need the interrupts functioning to enable serial communications? In other words, is the serial port interrupt-driven? I'm guessing I need to find "main", follow the hardware initialization code, and that should point me where I need to go...
Thanks,
-Bob
Quoted 28 lines · Stefan Roese
Hi Bob,
Quoted 8 lines · Robert S. Grimes
I'm getting started porting U-Boot to the Freescale/LogicPD M5329EVB board, based on the ColdFire MCF5329 processor. As suggested in the "U-Boot Porting Guide" in the README file, I've subscribed to this list, and I'm admitting I am (currently) clueless - hence this email!
At this point, my only real question is this - has anybody done this already?
I have not head of a MCF5329 U-Boot port. You are aware that the MCF52x2 CondFires are supported? So this should be your starting point. Grep for "MCF52" in
include/configs/*and you will see what boards are available with this CPU's.Best regards,
Stefan=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
Quoted 5 lines · Robert S. Grimes
Yes, I am, and that is where I've started. I currently have got a simple copy to compile cleanly, but none of the device-specific code has been checked to see if it needs to be modified.
Any hints as to where I should start?
start.S is a good point to "start" looking at. ;-)
Quoted 2 lines
For example, I'm guessing the
serial port is rather important, right?
Yes it is. No idea if the serial core on your M5329 is identical to the one used in the already supported M52x2.
Quoted 3 lines
But do I need the interrupts
functioning to enable serial communications? In other words, is the serial port interrupt-driven?
Normally not. Could be that interrupts are need for timer support (timeout handling...).
Quoted 3 lines
I'm guessing I need to find "main",
follow the hardware initialization code, and that should point me where I need to go...
Again start.S.
I have to admit that I am not into the ColdFires right now. With addition of the M5329 to the current U-Boot ColdFire support, we should either
a) Create a new cpu-directly for the M53xx ColdFire family
or
b) Rename the current cpu directory to "mfc5xxx" or something like this
This depends on the similarities of the chips and their internal resources (UART, interrupt controller, ethernet controller..) of course. Solution b) would be my preferred way, if it makes sense.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
Quoted 11 lines · Stefan Roese
Quoted 6 lines · Robert S. Grimes
Yes, I am, and that is where I've started. I currently have got a simple copy to compile cleanly, but none of the device-specific code has been checked to see if it needs to be modified.
Any hints as to where I should start?
start.Sis a good point to "start" looking at. ;-)
Right!
Quoted 5 lines
I have to admit that I am not into the ColdFires right now. With addition of the M5329 to the current U-Boot ColdFire support, we should either
a) Create a new cpu-directly for the M53xx ColdFire family
Quoted 8 lines
or
b) Rename the current cpu directory to "mfc5xxx" or something like this
This depends on the similarities of the chips and their internal resources (UART, interrupt controller, ethernet controller..) of course. Solution b) would be my preferred way, if it makes sense.
Okay, I'll take that under advisement. You know, you pick your poison here - either you get similar code in separate files (solution a) or similar code in separate conditionally-compiled blocks (solution b)...
Thanks for the advice!
-Bob
Quoted 12 lines
Thanks.
Best regards,
Stefan=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
Quoted 28 lines · Stefan Roese
Quoted 5 lines · Robert S. Grimes
Yes, I am, and that is where I've started. I currently have got a simple copy to compile cleanly, but none of the device-specific code has been checked to see if it needs to be modified.
Any hints as to where I should start?
start.Sis a good point to "start" looking at. ;-)Quoted 2 lines
For example, I'm guessing the
serial port is rather important, right?Yes it is. No idea if the serial core on your M5329 is identical to the one used in the already supported M52x2.
Quoted 3 lines
But do I need the interrupts
functioning to enable serial communications? In other words, is the serial port interrupt-driven?Normally not. Could be that interrupts are need for timer support (timeout handling...).
Quoted 3 lines
I'm guessing I need to find "main",
follow the hardware initialization code, and that should point me where I need to go...Again
start.S.
Quoted 8 lines
I have to admit that I am not into the ColdFires right now. With addition of the M5329 to the current U-Boot ColdFire support, we should either
a) Create a new cpu-directly for the M53xx ColdFire family
or
b) Rename the current cpu directory to "mfc5xxx" or something like this
There are some similarities, but I think there are enough dissimilarities to justify creating a new subdirectory.
However, there are already three different "trees" for MCF52xx, so this is maybe not too critical anyways.
Serial ports are identical with different base addresses, but the interrupt controller is only similar. The ethernet controller is completely different, and this is one of the things I did not even touch yet.
Quoted 3 lines
This depends on the similarities of the chips and their internal resources (UART, interrupt controller, ethernet controller..) of course. Solution b) would be my preferred way, if it makes sense.
I already tried creating a port for Cobra5329 (also a small MCF5329 board) and our own MCF5373 board. The tree, based on "git clone" some days ago, can be found at
http://leila.dyna.ping.de/wolfgang/u-boot-git-mcf53xx.tar.bz2
It is basically untested besides being compile-clean, because I am too busy with some other things and still have problems accessing the flash. I already sent this link to Bob, but as I am not too confident in everything being right, I did not want to spread it wide. In case somebody reading this wants to have a look, feel free to grab the tree and see what might be usable.
Quoted 4 lines
Thanks.
Best regards,
Stefan
Regards,
Wolfgang
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · w.wegner at astro-kom.de
Hi Bob,
I started a port to MCF53xx, but it is basically untested. Current state is: compile-clean, ethernet is not implemented (all configuration options involving network have to be disabled), but not tested on a board. I used the MCF52xx for my modifications, as you were already suggested to do.
Hi Wolfgang,
I've followed your directions, which were pretty easy, given I had just done it yesterday for my first attempt. However, when I tried to compile my port of your stuff, it fails in an unexpected area - specifically, it fails attempting to build the tools! To make sure it wasn't my stuff (pretty sure it couldn't have been, but I've been confused before!), I tried to build your cobra5329, using the following:
make clean
make cobra5329_config
make
I got the exact same error, so it's clear it isn't my stuff. Here is the message
make[1]: Entering directory /root/u-boot-git/tools make[1]: *** No rule to make target
`/usr/lib/gcc-lib/i486-linux/3.3.5/include/stddef.h', needed by 'img2srec.o'. Stop.
Seems some incompatibility in our respective gcc setup. BTW, I have Gentoo Linux, and am using gcc 3.4.4 - my libraries show up under /usr/lib/gcc/i686-pc-linux-gnu/3.4.4. I don't know how the u-boot build system determines where to look, but it's clearly looking in the wrong place for me! Any ideas?
BTW: Am I to understand the MCF532x family is approximately equal to the MCF537x family, with respect to porting u-boot?
Thanks!
-Bob
Quoted 52 lines
My problem is that I was not yet able to access the flash on any of my boards (Cobra 5329 EVB and our prototype with MCF5373) and neither dared to use
CONFIG_RUN_FROM_RAM(or whatever this option is called).You can grab my current tree at
http://leila.dyna.ping.de/wolfgang/u-boot-git-mcf53xx.tar.bz2(it is based on what I got some days ago with "git clone", but I do not know if this is really the most actual tree)
To adapt to your board, you should make a new subdirectory in "board", probably starting with cobra5329 as a starting population. Then edit the
Makefilein the main directory (probably also taking the lines for cobra5329 as a starting point) and do a "make M5329EVB" (or whatever you want to call your port).
You definitely have to editcobra5329.c(which you also want to rename ;-) ) in the board/M5329EVB subdirectory to use the correct settings for your SDRAM. Apart from that, you are probably on your own, as I am not any further either. :-(Regards,
WolfgangQuoted 26 lines · Robert S. Grimes
Hi,
I'm getting started porting U-Boot to the Freescale/LogicPD M5329EVB board, based on the ColdFire MCF5329 processor. As suggested in the "U-Boot Porting Guide" in the README file, I've subscribed to this list, and I'm admitting I am (currently) clueless - hence this email!
At this point, my only real question is this - has anybody done this already? If so, can/will you share? Or are you working on a similar port, and would you like to share the load? I'm very open to working with others on this, though if there are no takers, I'll go it alone and post it all later.
Thanks, and take care,
-Bob-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users