From: Johnson Yu <johnson.yn83@yahoo.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Integrate AT91 Boot func into U-boot, under A91RM9200 board
Date: Fri, 10 Jul 2009 18:53:39 +0800 [thread overview]
Message-ID: <4A571DB3.2070602@yahoo.co.uk> (raw)
In-Reply-To: <m2bpo70z9i.fsf@ohwell.denx.de>
Hi,
Simply put, my question is:
To port U-boot-2009.06 into an AT91RM9200-based self-produced board, all
the modifications have successfully been done and this latest U-boot
runs on my board, named ceiboard. Normal procedure is, downloading
loader.bin then U-boot.bin and running on RAM, after that loading
boot.bin to FLASH 0x10000000 followed by U-boot.gz on FLASH too, and
then set BMS to boot from external memory--FLASH. So, boot.bin runs
first and it uncompresses U-boot.gz to RAM and jump to that address on RAM.
Now, I don't want this boot.bin thing as a separate file and want it as
part of U-boot.bin, how should I do it??
My solution is:
1) copy entry.S, crt0.S, initboot.c, AT91RM9200.h to
/board/geari/ceiboard/(which is my board location); and change the jump
instruction in crt0.S---not to call the uncompress function, boot(), in
AT91RM9200BOOT/main.c, but to call _start in /cpu/arm920t/start.S ---
and, of course, to not confuse the compiler, I changed _start of start.S
to uboot_start and kept _start in AT91RM9200BOOT/entry.S as the unique
entry point of the program. like below:
b boot ===> b uboot_start (in crt0.S)
2) modify linker script /board/geari/ceiboard/u-boot.lds to:
..text :
{
board/geari/ceiboard/entry.o (.text)
board/geari/ceiboard/crt0.o (.text)
cpu/arm920t/start.o (.text)
*(.text)
}
and with rest of u-boot.lds intact.
then I started compiling, and got some errors:
/home/johnson-yn/GEARI/u-boot-ceiboard/include/asm/arch/AT91RM9200.h:103:
error: expected identifier or ?(? before numeric constant
/home/johnson-yn/GEARI/u-boot-ceiboard/include/asm/arch/AT91RM9200.h:104:
error: expected ?;? before ?AT91_REG?
make[1]: *** [mkimage.o] Error 1
make[1]: Leaving directory `/home/johnson-yn/GEARI/u-boot-ceiboard/tools'
make: *** [tools] Error 2
any suggestions????
Regards,
Johnson. Yu
Detlev Zundel wrote:
> Hi,
>
>
>> I met this compiling error, any idea?
>>
>> /common/env_flash.c:312: undefined reference to `flash_sect_protect'
>> /common/env_flash.c:316: undefined reference to `flash_sect_erase'
>> /common/env_flash.c:329: undefined reference to `flash_sect_protect'
>> make: *** [u-boot] Error 1
>>
>
> Sure you are missing the definition of those functions. Maybe you'd
> care to give us information so we can reproduce this? Is this a
> standard configuration? What version of U-Boot?
>
> Thanks
> Detlev
>
>
___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html
prev parent reply other threads:[~2009-07-10 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3341.1246291212.8190.u-boot@lists.denx.de>
2009-06-29 16:26 ` [U-Boot] Undefined reference to'flash_sect_protect' in env_flash.c Johnson Yu
2009-06-29 16:40 ` Detlev Zundel
2009-06-30 7:35 ` Johnson Yu
2009-06-30 13:37 ` Detlev Zundel
2009-07-10 10:53 ` Johnson Yu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A571DB3.2070602@yahoo.co.uk \
--to=johnson.yn83@yahoo.co.uk \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox