[U-Boot-Users] 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,
On Wednesday 02 May 2007 18:42, Robert S. Grimes wrote:
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 =====================================================================
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
Stefan Roese wrote:
Hi Bob,
On Wednesday 02 May 2007 18:42, Robert S. Grimes wrote:
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 =====================================================================
On Thursday 03 May 2007 13:55, Robert S. Grimes wrote:
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. ;-)
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.
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...).
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 =====================================================================
Stefan Roese wrote:
On Thursday 03 May 2007 13:55, Robert S. Grimes wrote:
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. ;-)
Right!
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.
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
Thanks.
Best regards, Stefan
===================================================================== DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk Office: Kirchenstr. 5, D-82194 Groebenzell, Germany =====================================================================
On 3 May 2007 at 14:16, Stefan Roese wrote:
On Thursday 03 May 2007 13:55, Robert S. Grimes wrote:
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. ;-)
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.
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...).
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
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.
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.
Thanks.
Best regards, Stefan
Regards, Wolfgang
participants (4)
-
Robert S. Grimes -
Robert S. Grimes -
Stefan Roese -
w.wegner＠astro-kom.de