[uClinux-dev] Colilo hangs

Greg Evans gevans at vigilhealth.com
Tue Mar 11 13:44:52 EST 2003

Thanks for getting back to me so quickly. I followed your instructions and I
still could not get Colilo to boot on reset. The one thing that was
bothering me was that whether I had JP13 on the M5272C3 board configured for
pins 1-2 or pins 2-3, DBUG always booted. I looked through the M5272C3
User's Manual and sure enough JP13 was mentionned as the jumper for this
very application. It's not that I doubted Motorola, but I took a look at the
board and noticed that there was a table scribed on the underside of the
pcb. There, I found that JP5 is used to switch between booting from
0xFFE00000 and 0xFFF00000 (Hmmm documentation error!). Anyways, I switch JP5
from pins 1-2 to 2-3 and reset the board. What do you know -- the Colilo
prompt came up!!!!

Just in case there is someone out there who may have the same problem: do
not forget to check your board. Mine is a DigitalDNA from Motorola RE10795B
Rev. 2.2. If yours is the same make and you are experiencing the same
problem, then chances are JP5 is the jumper you want.

Greg Evans
gevans at vigilhealth.com

----- Original Message -----
From: "Heiko Degenhardt" <heiko.degenhardt at sentec-elektronik.de>
To: <uclinux-dev at uclinux.org>
Sent: Monday, March 10, 2003 11:31 PM
Subject: Re: [uClinux-dev] Colilo hangs

> Hi Greg,
> * On Mon, Mar 10, 2003 at 03:37:41PM -0800, Greg Evans wrote:
> > I have been working with the M5272C3 development board with
> > uClinux-dist 20020927. I want to have Motorola's DBUG left in
> > flash at 0xFFE00000 and install Colilo at 0xFFF00000. Using CF
> > FLASHER, I programmed flash with colilo.bin file starting at
> > 0xFFF00000. Next I programmed flash with a compressed file of
> > image.bin (uclinux-dist) located at address 0xFFF40000 (note: I am
> > using the M5272C3-1MB file for Colilo).
> I don't know something about the M5272C3-1MB file, but your setup is
> quiet comparable to our setup of colilo (MCF5272 based board, too).
> > Both binaries are programmed without any errors.
> Ok.
> > How can I get Colilo to work with the M5272C3?
> We do it the following way: We want to boot either colilo/uClinux or
> dBUG, debending on a jumper on our board (I think on the C3 board it
> is jumper 13).
> We build colilo for the 0xFFE00000 range.
> Than we flash the image to 0xFFF00000, and the (compressed) uClinux
> image at 0xFFF40000 (the adresses, the image size etc. are adjusted
> in main.c).
> You can see the firs two words that the Coldfire looks up after
> booting in dBUG:
> dBUG> md fff00000
> FFF00000:  0000 0000 FFE0 0400 FFE0 046C FFE0 046C...
> The "FFE0 0400" is the initial program counter. There you'll find
> the startup code of colilo:
> dBUG> dis fff00400
> FFF00400: 4E71                 NOP
> FFF00402: 46FC 2700            MOVE      #0x2700,SR
> FFF00406: 203C FFE0 0000       MOVE.L    #0xFFE00000,D0
> FFF0040C: 4E7B 0801            MOVEC     D0,VBR
> ...
> (I had to use fff00400 as address, because this will be the address
> 0xFFE00400 if we boot from the other flash sector).
> That doesn't answer your question why the colilo doesn't start
> with "go fff00400" (may be this has something to do with the register
> setup of dBUG and colilo, or it starts the image and then dies or
> whatever). But I think that wouldn't be the default way to
> start it anyway.
> May be you should try to do the following:
> - Enable the CONFIG_UI and BOOTDEBUG in the Makefile
> - Build colilo for the adress 0xffe00000
> - Flash it to 0xfff00000 (with JP 13 set between pins 1 and 2)
> - Set JP 13 between pins 2 and 3
> - Reset the board
> Now you should see the colilo prompt. If so you can play with
> it to load the image etc. If not you seem to have a problem with
> the colilo binary itself.
> If you have further questions, please email me and I'll try to help
> you further.
> Rgds.
> Heiko.
> _______________________________________________
> uClinux-dev mailing list
> uClinux-dev at uclinux.org
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by uclinux-dev at uclinux.org

More information about the uClinux-dev mailing list