[U-Boot-Users] MCF5271 Port.
I am new to U-Boot. I downloaded u-boot-1.1.6 and plan to use the same on the MCF5271 EVB. My host system has Red Hat 6.
I followed the instructions provided in the readme and I got the following result
[root@em u-boot-1.1.6]# make M5271EVB_config Configuring for M5271EVB board... [root@em u-boot-1.1.6]# make all for dir in tools examples post post/cpu ; do make -C $dir _depend ; done make[1]: Entering directory `/U-Boot/u-boot-1.1.6/tools' ln -s ../common/environment.c environment.c ln -s ../lib_generic/crc32.c crc32.c make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/tools' make[1]: Entering directory `/U-Boot/u-boot-1.1.6/tools' make[1]: Nothing to be done for `_depend'. make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/tools' make[1]: Entering directory `/U-Boot/u-boot-1.1.6/examples' m68k-elf-gcc: hello_world.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: stubs.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' make[1]: *** [.depend] Error 1 make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/examples' make[1]: Entering directory `/U-Boot/u-boot-1.1.6/post' m68k-elf-gcc: cache_8xx.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: cache.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: codec.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: cpu.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: dsp.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: ether.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: i2c.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: memory.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: post.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: rtc.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: spr.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: sysmon.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: tests.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: uart.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: usb.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: watchdog.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' make[1]: *** [.depend] Error 1 make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/post' make[1]: Entering directory `/U-Boot/u-boot-1.1.6/post/cpu' m68k-elf-gcc: asm.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: cmp.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: cmpi.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: two.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: twox.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: three.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: threex.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: threei.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: andi.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: srawi.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: rlwnm.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: rlwinm.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: rlwimi.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: store.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: load.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: cr.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: b.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: multi.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: string.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: complex.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' make[1]: *** [.depend] Error 1 make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/post/cpu' make: *** [depend] Error 2
Can you please help me out.
Regards, Adarsh.
__________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/
In message 371814.45747.qm@web8321.mail.in.yahoo.com you wrote:
I am new to U-Boot. I downloaded u-boot-1.1.6 and plan to use the same on the MCF5271 EVB. My host system has Red Hat 6.
Sounds as if you have a favour for old code. Be aware that problems may be lurking in that corner.
m68k-elf-gcc: hello_world.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: stubs.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ'
... Seems your toolchain is not working. Try another one.
Best regards,
Wolfgang Denk
On 1/29/07, Wolfgang Denk wd@denx.de wrote:
In message 371814.45747.qm@web8321.mail.in.yahoo.com you wrote:
I am new to U-Boot. I downloaded u-boot-1.1.6 and plan to use the same on the MCF5271 EVB. My host system has Red Hat 6.
Sounds as if you have a favour for old code. Be aware that problems may be lurking in that corner.
m68k-elf-gcc: hello_world.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: stubs.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ'
... Seems your toolchain is not working. Try another one.
As Wolfgang says, old toolchains will do this. When trying to compile a recent checkout using the 20010318 Snapgear toolchain, I got the same error. When I upgraded to the 20060615 release, it worked.
Also note that someone recently had a different problem with compiling the 5271 port using the 20060615 toolchain. Here's a link to his post and someone's reply on how to fix it:
http://comments.gmane.org/gmane.comp.hardware.motorola.microcontrollers.cold.... I haven't looked at the issue yet. If you (or anyone) gets a chance, it'd be helpful to know what the issue is and if this is a real fix or just a workaround.
Zachary P. Landau <kapheine <at> gmail.com> writes:
On 1/29/07, Wolfgang Denk <wd <at> denx.de> wrote:
In message <371814.45747.qm <at> web8321.mail.in.yahoo.com> you wrote:
I am new to U-Boot. I downloaded u-boot-1.1.6 and plan to use the same on the MCF5271 EVB. My host system has Red Hat 6.
Sounds as if you have a favour for old code. Be aware that problems may be lurking in that corner.
m68k-elf-gcc: hello_world.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: stubs.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ'
... Seems your toolchain is not working. Try another one.
As Wolfgang says, old toolchains will do this. When trying to compile a
recent
checkout using the 20010318 Snapgear toolchain, I got the same error. When I upgraded to the 20060615 release, it worked.
Also note that someone recently had a different problem with compiling the
5271
port using the 20060615 toolchain. Here's a link to his post and someone's reply on how to fix it:
http://comments.gmane.org/gmane.comp.hardware.motorola.microcontrollers.cold... e/7212.
I haven't looked at the issue yet. If you (or anyone) gets a chance, it'd be helpful to know what the issue is and if this is a real fix or just a workaround.
Hi Zachary,
I have with me m68k-elf-tools-20030314 tool chain. I have one more thing to report. I tried building twice after I posted the message and each time I got different errors. the first time: make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/fs/jffs2' make -C fs/reiserfs/ make[1]: Entering directory `/U-Boot/u-boot-1.1.6/fs/reiserfs' m68k-elf-gcc: reiserfs.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: dev.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: mode_string.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' make[1]: *** [.depend] Error 1 make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/fs/reiserfs' make: *** [fs/reiserfs/libreiserfs.a] Error 2
the second time: make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/fs/reiserfs' make -C fs/ext2/ make[1]: Entering directory `/U-Boot/u-boot-1.1.6/fs/ext2' m68k-elf-gcc: ext2fs.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: dev.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' make[1]: *** [.depend] Error 1 make[1]: Leaving directory `/U-Boot/u-boot-1.1.6/fs/ext2' make: *** [fs/ext2/libext2fs.a] Error 2
Anyways i will try it out with 20060615. Thanks.
Regards, Adarsh.
Adarsh Babu <adarshrbpin <at> yahoo.co.in> writes:
Zachary P. Landau <kapheine <at> gmail.com> writes:
On 1/29/07, Wolfgang Denk <wd <at> denx.de> wrote:
In message <371814.45747.qm <at> web8321.mail.in.yahoo.com> you wrote:
I am new to U-Boot. I downloaded u-boot-1.1.6 and plan to use the same on the MCF5271 EVB. My host system has Red Hat 6.
Sounds as if you have a favour for old code. Be aware that problems may be lurking in that corner.
m68k-elf-gcc: hello_world.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ' m68k-elf-gcc: stubs.o: No such file or directory m68k-elf-gcc: unrecognized option `-MQ'
... Seems your toolchain is not working. Try another one.
As Wolfgang says, old toolchains will do this. When trying to compile a
recent
checkout using the 20010318 Snapgear toolchain, I got the same error.
When I
upgraded to the 20060615 release, it worked.
Also note that someone recently had a different problem with compiling the
5271
port using the 20060615 toolchain. Here's a link to his post and someone's reply on how to fix it:
http://comments.gmane.org/gmane.comp.hardware.motorola.microcontrollers.cold...
e/7212.
I haven't looked at the issue yet. If you (or anyone) gets a chance, it'd
be
helpful to know what the issue is and if this is a real fix or just a workaround.
Hi Zachary,
Well thanks a lot. The 20060615 tool chain along with the suggestion in the link that you sent me did the trick. But now I face a different problem. I did get a neat build and the u-boot.bin file. I flashed the same onto the EVB. But i can't get a u-boot prompt on Minicom. Its just blank and nothing else. I opened the Srec file and compared it with the Srec file I got for MCF5272 with u-boot1.1.2 and seemed pretty ok. Do I have to do something to get it on the console ? is there any other modifications that i need to do other than make M5271EVB_config and make ???
Please help me out.
Regards, Adarsh.
Well thanks a lot for your suggestion of going for the new tool chain. The 20060615 tool chain along with the suggestion in the link that you sent me did the trick. But now I face a different problem. I did get a neat build and the u-boot.bin file. I flashed the same onto the EVB. But i can't get a u-boot prompt on Minicom. Its just blank and nothing else. I opened the Srec file and compared it with the Srec file I got for MCF5272 with u-boot1.1.2 and seemed pretty ok.
Is there something specific that I have to do something to get it on the console ? Are there any other modifications that i need to do other than make M5271EVB_config and make ???
Unfortunately I've never tried u-boot on the M5271EVB. I only added support for the R5200 (a board we did for a customer). According to the Changelog file for u-boot, Marian Balakowicz m8@semihalf.com did the M5271EVB port. That information really should be in the MAINTAINERS file, but it doesn't seem to be.
I guess I'd say start with making sure there aren't any jumpers or switches on the M5271EVB that can change chip selects or anything like that. Another possibility would be that something broke. You could try checking out commit 78b123cd69d485887f33ebd33ba1f9b27f8e6916, where M5271EVB support was first entered in.
Failing that you'll probably have to start tracing execution, trying to find out where it is failing.
Adarsh Babu wrote: [...]
Well thanks a lot. The 20060615 tool chain along with the suggestion in the link that you sent me did the trick. But now I face a different problem. I did get a neat build and the u-boot.bin file. I flashed the same onto the EVB. But i can't get a u-boot prompt on Minicom. Its just blank and nothing else. I opened the Srec file and compared it with the Srec file I got for MCF5272 with u-boot1.1.2 and seemed pretty ok. Do I have to do something to get it on the console ?
Hello Adarsh,
There have been changes to cpu/mcf52x2/start.S since the addition of M5271EVB that broke things for this target - with one of the symptoms being missing console output. This have been fixed recently (commit daa6e418bcc0c717752e8de939c213c790286096), so you could try to (1) follow Zachary's suggestion and use sources as of commit 78b123cd69d485887f33ebd33ba1f9b27f8e6916, or (2) use recent sources (daa6e418bcc0c717752e8de939c213c790286096 and later).
HTH, Bartlomiej
Bartlomiej Sieka <tur <at> semihalf.com> writes:
Adarsh Babu wrote: [...]
Well thanks a lot. The 20060615 tool chain along with the suggestion in
the
link that you sent me did the trick. But now I face a different problem. I
did
get a neat build and the u-boot.bin file. I flashed the same onto the EVB.
But
i can't get a u-boot prompt on Minicom. Its just blank and nothing else. I opened the Srec file and compared it with the Srec file I got for MCF5272
with
u-boot1.1.2 and seemed pretty ok. Do I have to do something to get it on
the
console ?
Hello Adarsh,
There have been changes to cpu/mcf52x2/start.S since the addition of M5271EVB that broke things for this target - with one of the symptoms being missing console output. This have been fixed recently (commit daa6e418bcc0c717752e8de939c213c790286096), so you could try to (1) follow Zachary's suggestion and use sources as of commit 78b123cd69d485887f33ebd33ba1f9b27f8e6916, or (2) use recent sources (daa6e418bcc0c717752e8de939c213c790286096 and later).
HTH, Bartlomiej
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da...
Hi Bartlomiej,
Thanks for the suggestion. I have got the U-boot up for the EVB. I have started to customize U-boot for my board. I have taken the M5271 as an example to develop files for the custom board. There isn't a "flash.c" for the M5271evb in "board/m5271evb". So does the m5271evb port use the "flash.c" present in the common folder ?
Regards, Adarsh.
In message loom.20070208T161330-690@post.gmane.org you wrote:
to develop files for the custom board. There isn't a "flash.c" for the M5271evb in "board/m5271evb". So does the m5271evb port use the "flash.c" present in the common folder ?
No, it uses the CFI flash driver as all boards with CFI conformant flash devices should do.
Best regards,
Wolfgang Denk
Wolfgang Denk <wd <at> denx.de> writes:
In message <loom.20070208T161330-690 <at> post.gmane.org> you wrote:
to develop files for the custom board. There isn't a "flash.c" for the M5271evb in "board/m5271evb". So does the m5271evb port use the "flash.c" present in the common folder ?
No, it uses the CFI flash driver as all boards with CFI conformant flash devices should do.
Best regards,
Wolfgang Denk
Hi,
I created files for the custom board with M5271EVB as the example. I modified the dram init to support the SDRAM we have on the board. I also made changes to the flash base address and the associated to gel with our memory map. when I flashed the u-boot.bin file that I got, the following turned up on the console.
U-Boot 1.2.0 (Feb 13 2007 - 20:15:12)
CPU: Freescale Coldfire MCF5271 at 100 MHz Board: Freescale M5271EVB DRAM: 16 MB FLASH:
The board hung after "FLASH:". The flash on our board is SST39VF6401. From the Flash.h file I learn that SSTxF6401 has been considered and cfi_driver.c will check the CFI conformant device. Can you please suggest the possible areas that I should check or have neglected.
Regards, Adarsh.
Adarsh Babu wrote: [...]
Well thanks a lot. The 20060615 tool chain along with the suggestion in the link that you sent me did the trick. But now I face a different problem. I did get a neat build and the u-boot.bin file. I flashed the same onto the EVB. But i can't get a u-boot prompt on Minicom.
One more thing: I just came across the following in the DULG (5.6. Initialization), seems related:
"If you are running Linux on your host system we recommend either kermit or cu as terminal emulation programs. Do not use minicom, since this has caused problems for many users, especially for software download over the serial port."
Regards, Bartlomiej
participants (5)
-
Adarsh Babu -
adarsh babu
-
Bartlomiej Sieka -
Wolfgang Denk -
Zachary P. Landau