[U-Boot] u-boot for imx27 Board

[U-Boot] u-boot for imx27 Board

[Lejin K Joy]

Hi,

 

I was trying to use u-boot for imx27 board. But I was not able to find uboot
for the same board. Only one available is
<http://git.denx.de/?p=u-boot/u-boot-v2.git;a=summary> u-boot/u-boot-v2.git
but I was not able to download the same using the git tool. Any help would
be appreciated.

 

Thanks,

Lejin

[U-Boot] u-boot for imx27 Board

[Sascha Hauer]

On Thu, Aug 21, 2008 at 02:35:43PM +0530, Lejin K Joy wrote:
> Hi,
> 
>  
> 
> I was trying to use u-boot for imx27 board. But I was not able to find uboot
> for the same board. Only one available is
> <http://git.denx.de/?p=u-boot/u-boot-v2.git;a=summary> u-boot/u-boot-v2.git
> but I was not able to download the same using the git tool. Any help would
> be appreciated.

Try

# git clone git://git.denx.de/u-boot-v2.git

or if you are behind a firewall

# git clone http://git.denx.de/u-boot-v2.git

might help

Sascha


-- 
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

[U-Boot] u-boot for imx27 Board

[Lejin K Joy]

Thanks a lot Sascha,

I was able to downlaod it and  I was compiling it. If you have worked on the
same platform kindly give your valuable inputs.

I am compiling the U-boot for imx27ads board.

I have set the env variables using  the following commands : 

#ln -s arm cross_arch            [I also tried setting it to machi-imx. This
also is not helping]
#ln -s arm cross_compile

(I am perfoeming the compilation from RedHat Linux Machine.) 

After this on giving make menuconfig it shows me the option for selecting
the imx27 board and I was able to save the configurations as imx27_config
file. There is not default config file for this board. 

But after this when I try Folowing message is displayed :

#  make arm_ imx27_config file  
	
	make: *** No rule to make target `/u-boot-v2/arch//Makefile

# make 

	Makefile:1228: *** default environment path empty.  Stop.

Could  you please give some input.

Thanks,
Lejin


-----Original Message-----
From: Sascha Hauer [mailto:s.hauer at pengutronix.de] 
Sent: Thursday, August 21, 2008 5:51 PM
To: Lejin K Joy
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] u-boot for imx27 Board

On Thu, Aug 21, 2008 at 02:35:43PM +0530, Lejin K Joy wrote:
> Hi,
> 
>  
> 
> I was trying to use u-boot for imx27 board. But I was not able to find
uboot
> for the same board. Only one available is
> <http://git.denx.de/?p=u-boot/u-boot-v2.git;a=summary>
u-boot/u-boot-v2.git
> but I was not able to download the same using the git tool. Any help would
> be appreciated.

Try

# git clone git://git.denx.de/u-boot-v2.git

or if you are behind a firewall

# git clone http://git.denx.de/u-boot-v2.git

might help

Sascha


-- 
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

[U-Boot] u-boot for imx27 Board

[Sascha Hauer]

On Thu, Aug 21, 2008 at 06:54:53PM +0530, Lejin K Joy wrote:
> 
> Thanks a lot Sascha,
> 
> I was able to downlaod it and  I was compiling it. If you have worked on the
> same platform kindly give your valuable inputs.
> 
> I am compiling the U-boot for imx27ads board.

I just updated mx27ads support and added a defconfig file, so please do
a 'git pull'.

> 
> I have set the env variables using  the following commands : 
> 
> #ln -s arm cross_arch            [I also tried setting it to machi-imx. This
> also is not helping]
> #ln -s arm cross_compile

Sorry, documentation is a bit outdated here, the links do not work any
more. You have to specify architecture and cross compiler on the command
line:

ARCH=arm CROSS_COMPILE=/whereever/it/is/arm-..-gcc make mx27ads_defconfig
ARCH=arm CROSS_COMPILE=/whereever/it/is/arm-..-gcc make menuconfig
ARCH=arm CROSS_COMPILE=/whereever/it/is/arm-..-gcc make

This should give you a uboot.bin which you can try on your board. If you
already have a bootloader (redboot?) on your board which you want to
keep, it's best to start U-Boot from RAM first. Load it somewhere to RAM
and jump there (don't know how to do this with redboot though).

Regards,
  Sascha


-- 
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

[U-Boot] u-boot for imx27 Board

[Lejin K Joy]

 

 

Dear Sascha,

 

Thanks for your wonderful support and guidance. Unfortunately I am stuck up
towards the end of building.

 

 

Could you kindly suggest me the arm cross compiler's link /name using which
you have compiled the u-boot. I am using obsolete-gcc-3.3.2.tar.bz2
compiler. 

 

First two steps was successful  but got stuck up in the final make. Please
find the errors attached. Could you please share your inputs in this
regards.

 

(Attached below Outputs)

 

Thanking you,

Lejin

 

---------------------

 

1)  

 

[root at localhost u-boot-v2]# ARCH=arm
CROSS_COMPILE=/Lijin/usr/local/arm/3.3.2/bin/arm-linux- make
mx27ads_defconfig

*

* Linux Kernel Configuration

*

Select your board

  1. mx1ads (MACH_MX1ADS)

  2. Synertronixx scb9328 (MACH_SCB9328)

  3. phyCORE-i.MX27 (MACH_PCM038)

> 4. Freescale i.MX27ADS (MACH_IMX27ADS)

  5. eco920 (MACH_ECO920)

  6. Hilscher Netx nxdb500 (MACH_NXDB500)

  7. phyCORE-i.MX31 (MACH_PCM037)

  8. Texas Instruments' OMAP based platforms (MACH_OMAP)

  9. Atmel AT91SAM9260-EK (MACH_AT91SAM9260_EK)

  10. Ronetix PM9263 (MACH_PM9263)

choice[1-10]: 4

clko command (IMX_CLKO) [Y/n/?] y

*

* Arm specific settings

*

Send commandline to kernel (CMDLINE_TAG) [Y/n/?] y

send memory definition to kernel (SETUP_MEMORY_TAGS) [Y/n/?] y

send initrd params to kernel (INITRD_TAG) [N/y/?] n

*

* General Settings

*

*

* memory layout

*

TEXT_BASE (TEXT_BASE) [0xa7f00000] 0xa7f00000

select memory layout

> 1. use default memory layout (MEMORY_LAYOUT_DEFAULT)

  2. manually assign a memory layout (MEMORY_LAYOUT_FIXED)

choice[1-2]: 1

Stack size (STACK_SIZE) [0x8000] 0x8000

malloc area size (MALLOC_SIZE) [0x400000] 0x400000

Prompt for broken or incomplete code (BROKEN) [N/y] n

Prompt for experimental code (EXPERIMENTAL) [N/y] n

run machine low-level init (MACH_DO_LOWLEVEL_INIT) [Y/n/?] y

U-Boot command prompt (PROMPT) [uboot:] uboot:

Default baudrate (BAUDRATE) [115200] 115200

Enable long help texts (LONGHELP) [Y/n] y

Buffer size for input from the Console (CBSIZE) [1024] 1024

max. Number of arguments accepted for monitor commands (MAXARGS) [16] 16

Select your shell

> 1. hush parser (SHELL_HUSH)

  2. Simple parser (SHELL_SIMPLE)

choice[1-2]: 1

hush globbing support (GLOB) [N/y/?] n

hush PS2 (PROMPT_HUSH_PS2) [> ] >

Enable command line editing (CMDLINE_EDITING) [Y/n] y

  Enable auto completion (AUTO_COMPLETE) [Y/n] y

Generate the crc32 table dynamically (DYNAMIC_CRC_TABLE) [Y/n/?] y

print error values as text (ERRNO_MESSAGES) [Y/n] y

print timestamp information from images (TIMESTAMP) [Y/n/?] y

Enable full console support (CONSOLE_FULL) [Y/n/?] y

  activate first console on startup (CONSOLE_ACTIVATE_FIRST) [Y/n/?] y

Open Firmware flat device tree support (OF_FLAT_TREE) [N/y] n

Enable Partitions (PARTITION) [Y/n] y

Compile in default environment (DEFAULT_ENVIRONMENT) [Y/n/?] y

  Default environment path (DEFAULT_ENVIRONMENT_PATH) [board/imx27ads/env]
board/imx27ads/env

*

* Debugging

*

enable debug symbols (DEBUG_INFO) [N/y/?] n

verbose flash handling (ENABLE_FLASH_NOISE) [N/y/?] n

verbose partition handling (ENABLE_PARTITION_NOISE) [N/y/?] n

verbose device handling (ENABLE_DEVICE_NOISE) [N/y/?] n

*

* Commands

*

*

* scripting

*

edit (CMD_EDIT) [Y/n] y

sleep (CMD_SLEEP) [Y/n] y

saveenv (CMD_SAVEENV) [Y/n] y

loadenv (CMD_LOADENV) [Y/n] y

export (CMD_EXPORT) [Y/n] y

printenv (CMD_PRINTENV) [Y/n] y

readline (CMD_READLINE) [Y/n] y

true (CMD_TRUE) [Y/n] y

false (CMD_FALSE) [Y/n] y

*

* file commands

*

ls (CMD_LS) [Y/n] y

rm (CMD_RM) [Y/n] y

cat (CMD_CAT) [Y/n] y

mkdir (CMD_MKDIR) [Y/n] y

rmdir (CMD_RMDIR) [Y/n] y

cp (CMD_CP) [Y/n] y

pwd (CMD_PWD) [Y/n] y

cd (CMD_CD) [Y/n] y

mount (CMD_MOUNT) [Y/n] y

umount (CMD_UMOUNT) [Y/n] y

*

* console

*

clear (CMD_CLEAR) [Y/n] y

echo (CMD_ECHO) [Y/n] y

*

* memory

*

loadb (CMD_LOADB) [N/y] n

meminfo (CMD_MEMINFO) [Y/n] y

md and mw (CMD_MEMORY) [Y/n] y

crc (CMD_CRC) [Y/n] y

mtest (CMD_MTEST) [Y/n] y

  alternative mtest implementation (CMD_MTEST_ALTERNATIVE) [Y/n] y

*

* flash

*

protect/erase (CMD_FLASH) [Y/n] y

nand (CMD_NAND) [N/y] n

*

* booting

*

bootm (CMD_BOOTM) [Y/n] y

  bootm with zlib support (CMD_BOOTM_ZLIB) [N/y] n

  bootm with bzlib support (CMD_BOOTM_BZLIB) [N/y] n

  show image information (CMD_BOOTM_SHOW_TYPE) [Y/n] y

reset (CMD_RESET) [Y/n] y

go (CMD_GO) [Y/n] y

timeout (CMD_TIMEOUT) [Y/n] y

addpart/delpart (CMD_PARTITION) [Y/n] y

test (CMD_TEST) [Y/n/?] y

version (CMD_VERSION) [Y/n] y

help (CMD_HELP) [Y/n] y

devinfo (CMD_DEVINFO) [Y/n] y

*

* Networking Support

*

Networking Support             (NET) [Y/n] y

  bootp support (NET_BOOTP) [Y/n] y

    dhcp support (NET_DHCP) [Y/n] y

  rarp protocol support (NET_RARP) [N/y] n

  sntp support (NET_SNTP) [N/y] n

  nfs support (NET_NFS) [N/y] n

  ping support (NET_PING) [Y/n] y

  tftp support (NET_TFTP) [Y/n] y

*

* Drivers

*

*

* serial drivers

*

i.MX serial driver (DRIVER_SERIAL_IMX) [Y/n] y

NS16550 serial driver (DRIVER_SERIAL_NS16550) [N/y/?] n

*

* Network drivers

*

smc911x ethernet driver (DRIVER_NET_SMC911X) [N/y/?] n

i.MX27 Ethernet driver (DRIVER_NET_IMX27) [Y/n] y

*

* SPI drivers

*

Enable SPI driver support (SPI) [Y/n] y

  i.MX SPI Master driver (DRIVER_SPI_IMX) [Y/n] y

  MC13783 a.k.a. PMIC driver (DRIVER_SPI_MC13783) [Y/n] y

*

* flash drivers

*

cfi flash driver (DRIVER_CFI) [Y/n/?] y

  new cfi flash driver (DRIVER_CFI_NEW) [Y/n/?] y

Support Intel flash chips (DRIVER_CFI_INTEL) [N/y] n

support AMD flash chips (DRIVER_CFI_AMD) [Y/n] y

Support  8-bit buswidth (DRIVER_CFI_BANK_WIDTH_1) [Y/n/?] y

Support 16-bit buswidth (DRIVER_CFI_BANK_WIDTH_2) [Y/n/?] y

Support 32-bit buswidth (DRIVER_CFI_BANK_WIDTH_4) [Y/n/?] y

Support 64-bit buswidth (DRIVER_CFI_BANK_WIDTH_8) [N/y/?] n

use cfi driver with buffer write (CFI_BUFFER_WRITE) [Y/n] y

*

* NAND support

*

NAND support                   (NAND) [N/y] n

*

* Filesystem support

*

cramfs support (FS_CRAMFS) [N/y] n

ramfs support (FS_RAMFS) [Y/n] y

devfs support (FS_DEVFS) [Y/n] y

#

# configuration written to .config

#

 

--------------------------------------

2) 

[root at localhost u-boot-v2]# ARCH=arm
CROSS_COMPILE=/Lijin/usr/local/arm/3.3.2/bin/arm-linux-  make menuconfig

scripts/kconfig/mconf arch/arm/Kconfig

 

 

*** End of U-Boot configuration.

*** Execute 'make' to build U-Boot or try 'make help'.

 

------------------------------

 

3)

 

[root at localhost u-boot-v2]# ARCH=arm
CROSS_COMPILE=/Lijin/usr/local/arm/3.3.2/bin/arm-linux-  make

scripts/kconfig/conf -s arch/arm/Kconfig

  SYMLINK include/asm-arm/arch -> include/asm-arm/arch-imx

  SYMLINK include/asm-arm/proc -> include/asm-arm/proc-armv

  CHK     include/linux/version.h

  UPD     include/linux/version.h

  CHK     include/linux/utsrelease.h

  UPD     include/linux/utsrelease.h

  SYMLINK include/asm -> include/asm-arm

  SYMLINK include/config.h -> board/imx27ads/config.h

  CC      scripts/mod/empty.o

cc1: error: invalid option `abi=apcs-gnu'

make[2]: *** [scripts/mod/empty.o] Error 1

make[1]: *** [scripts/mod] Error 2

make: *** [scripts] Error 2

 

 

---------------------------------------------

 

 

 

 

-----Original Message-----
From: Sascha Hauer [mailto:s.hauer at pengutronix.de] 
Sent: Thursday, August 21, 2008 8:49 PM
To: Lejin K Joy
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] u-boot for imx27 Board

 

On Thu, Aug 21, 2008 at 06:54:53PM +0530, Lejin K Joy wrote:

> 

> Thanks a lot Sascha,

> 

> I was able to downlaod it and  I was compiling it. If you have worked on
the

> same platform kindly give your valuable inputs.

> 

> I am compiling the U-boot for imx27ads board.

 

I just updated mx27ads support and added a defconfig file, so please do

a 'git pull'.

 

> 

> I have set the env variables using  the following commands : 

> 

> #ln -s arm cross_arch            [I also tried setting it to machi-imx.
This

> also is not helping]

> #ln -s arm cross_compile

 

Sorry, documentation is a bit outdated here, the links do not work any

more. You have to specify architecture and cross compiler on the command

line:

 

ARCH=arm CROSS_COMPILE=/whereever/it/is/arm-..-gcc make mx27ads_defconfig

ARCH=arm CROSS_COMPILE=/whereever/it/is/arm-..-gcc make menuconfig

ARCH=arm CROSS_COMPILE=/whereever/it/is/arm-..-gcc make

 

This should give you a uboot.bin which you can try on your board. If you

already have a bootloader (redboot?) on your board which you want to

keep, it's best to start U-Boot from RAM first. Load it somewhere to RAM

and jump there (don't know how to do this with redboot though).

 

Regards,

  Sascha

 

 

-- 

 Pengutronix - Linux Solutions for Science and Industry

   Handelsregister:  Amtsgericht Hildesheim, HRA 2686

     Hannoversche Str. 2, 31134 Hildesheim, Germany

   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

[U-Boot] u-boot for imx27 Board

[Robert Schwebel]

Hi,

On Thu, Aug 21, 2008 at 09:43:53PM +0530, Lejin K Joy wrote:
> Could you kindly suggest me the arm cross compiler's link /name using
> which you have compiled the u-boot. I am using
> obsolete-gcc-3.3.2.tar.bz2 compiler. 

We usually build the MX27 stuff with a generic arm-v4 cross toolchain,
built with OSELAS.Toolchain-1.1.1. You can compile such a toolchain
yourself easily with ptxdist, look here for the details:

http://www.pengutronix.de/oselas/toolchain/index_en.html

rsc
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

[U-Boot] u-boot-v2 for imx27 Board

[Lejin K Joy]

Hi,

I was running U-boot-v2 on imx27ads board and it's hanging up on the
terminal after the following display. 

--------
U-Boot 2.0.0-rc5-git (Sep 22 2008 - 23:05:39)

Board: Freescale i.MX27 ADS
---------

Also I am using Intel P30 strata flash. When the MTD cfi driver is enabled
in the menuconfig U-boot gives the following message and hangs up.

------------
U-Boot 2.0.0-rc5-git (Sep 22 2008 - 23:05:39)

Board: Freescale i.MX27 ADS
cfi_probe: cfi_flash base: 0xc0000000 size: 0x02000000
------------

Please provide your suggestions.


Thanks,
Lejin


-----Original Message-----
From: Robert Schwebel [mailto:r.schwebel at pengutronix.de] 
Sent: Friday, August 22, 2008 12:17 AM
To: Lejin K Joy
Cc: 'Sascha Hauer'; u-boot at lists.denx.de
Subject: Re: [U-Boot] u-boot for imx27 Board

Hi,

On Thu, Aug 21, 2008 at 09:43:53PM +0530, Lejin K Joy wrote:
> Could you kindly suggest me the arm cross compiler's link /name using
> which you have compiled the u-boot. I am using
> obsolete-gcc-3.3.2.tar.bz2 compiler. 

We usually build the MX27 stuff with a generic arm-v4 cross toolchain,
built with OSELAS.Toolchain-1.1.1. You can compile such a toolchain
yourself easily with ptxdist, look here for the details:

http://www.pengutronix.de/oselas/toolchain/index_en.html

rsc
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Lejin K Joy]

Hi All,

I am successfully able to get the U-boot prompt on my board based on
IMX27ads. 

However I am facing the following issue. Please help me out :

I want to load the Linux Kernel Zimage on to RAM. As per the documentation
we have used the following command to load zImage using Kermit protocol.

" U-boot-v2> loadb -c zImage "

(Also tried " U-boot-v2> loadb -f zImage ")

Which successfully downloads zimage to the file with default offset set as
0x00000000.....

a) But I am not able to understand to which location in RAM this image is
written to? b) Please let me know how exactly to load kernel image to
specific location on RAM?
c) Also how we can change the default location since the user is not given
an option to mention the address.
d) How to load the file " zImage" to RAM?

I was intending to do the following steps :

	>> loadb 0x100000 zimage
	>> loadb 0x1000000 ramdisk.gz 
	>> bootm 0x100000 0x1000000

Please help me out as I am using U-boot-V2 for the first time.

I am attaching the loadb.c file which I am using currently. Are there any
patches 

Waiting for your responses.

Thanks,
Lejin

-----Original Message-----
From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On
Behalf Of Lejin K Joy
Sent: Tuesday, September 23, 2008 9:49 PM
To: 'Robert Schwebel'; 'Sascha Hauer'
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] u-boot-v2 for imx27 Board


Hi,

I was running U-boot-v2 on imx27ads board and it's hanging up on the
terminal after the following display. 

--------
U-Boot 2.0.0-rc5-git (Sep 22 2008 - 23:05:39)

Board: Freescale i.MX27 ADS
---------

Also I am using Intel P30 strata flash. When the MTD cfi driver is enabled
in the menuconfig U-boot gives the following message and hangs up.

------------
U-Boot 2.0.0-rc5-git (Sep 22 2008 - 23:05:39)

Board: Freescale i.MX27 ADS
cfi_probe: cfi_flash base: 0xc0000000 size: 0x02000000
------------

Please provide your suggestions.


Thanks,
Lejin


-----Original Message-----
From: Robert Schwebel [mailto:r.schwebel at pengutronix.de] 
Sent: Friday, August 22, 2008 12:17 AM
To: Lejin K Joy
Cc: 'Sascha Hauer'; u-boot at lists.denx.de
Subject: Re: [U-Boot] u-boot for imx27 Board

Hi,

On Thu, Aug 21, 2008 at 09:43:53PM +0530, Lejin K Joy wrote:
> Could you kindly suggest me the arm cross compiler's link /name using
> which you have compiled the u-boot. I am using
> obsolete-gcc-3.3.2.tar.bz2 compiler. 

We usually build the MX27 stuff with a generic arm-v4 cross toolchain,
built with OSELAS.Toolchain-1.1.1. You can compile such a toolchain
yourself easily with ptxdist, look here for the details:

http://www.pengutronix.de/oselas/toolchain/index_en.html

rsc
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9


_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Nishanth Menon]

Lejin K Joy said the following on 09/25/2008 05:06 AM:
> I want to load the Linux Kernel Zimage on to RAM. As per the documentation
> we have used the following command to load zImage using Kermit protocol.
>
> " U-boot-v2> loadb -c zImage "
>
> (Also tried " U-boot-v2> loadb -f zImage ")
>
> Which successfully downloads zimage to the file with default offset set as
> 0x00000000.....
>   
U-Boot V2 uses a filesystem. when you did loadb -c -f zImage, it
downloaded the image to the file called zImage. zImage is stored within
the ramfs filesystem. (the concepts are very similar to an OS with
restrictions). This is slightly different from what you want to achieve
I think.
> a) But I am not able to understand to which location in RAM this image is
> written to? b) Please let me know how exactly to load kernel image to
> specific location on RAM?
>   
Look for the device node which shows the RAM/NOR/NAND you need. this
might be /dev/mem or (in my OMAP3430 case) /dev/ram0 - also see "help
loadb". Loadb takes the following options:
-f file - where to download to
-o offset - what offset to download - defaults to 0
-b baud - baudrate at which to download - defaults to console baudrate
-c - Create file if it is not present - default disabled
In your case, lets say: your ram starts at 0x80000000 and is denoted by
/dev/ram0. If you want to download to offset 0x3000 in ram, you can do
loadb -f /dev/ram0 -o 0x3000. this will essentially download to 0x80003000.

+ you now have the flexibility of downloading straight to NOR, NAND or
to even a file within u-boot v2's ramfs!! - so you can store and share
commonly used scripts modules etc.. tons of similar flexibility exists.
> c) Also how we can change the default location since the user is not given
> an option to mention the address.
>   
as explained above.
> d) How to load the file " zImage" to RAM?
>   
if you want to copy a file from ramfs to a "specific location" just do
the cp command!
> I was intending to do the following steps :
>
> 	>> loadb 0x100000 zimage
> 	>> loadb 0x1000000 ramdisk.gz 
> 	>> bootm 0x100000 0x1000000
>
> Please help me out as I am using U-boot-V2 for the first time.
>   
Does the above explanation help? in u-boot-v2, you can infact run "help
<command name>" or do a make docs And if you have graphviz latex etc
installed, you will get a html documentation in Documentation/html.

Note: I created a few useful platform independent tools for U-boot
(should work for both U-boot v2 and V1). they are available in [1].
>
> -----Original Message-----
> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On
> Behalf Of Lejin K Joy
> Sent: Tuesday, September 23, 2008 9:49 PM
> To: 'Robert Schwebel'; 'Sascha Hauer'
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] u-boot-v2 for imx27 Board
>   
Try not to top post. see [2] and mailing list ettiquette.
Regards,
Nishanth Menon

[1] http://code.google.com/p/omap-u-boot-utils/
[2] http://en.wikipedia.org/wiki/Posting_style

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Lejin K Joy]

-----Original Message-----
From: Nishanth Menon [mailto:menon.nishanth at gmail.com] 
Sent: Thursday, September 25, 2008 4:33 PM
To: Lejin K Joy
Cc: 'Robert Schwebel'; 'Sascha Hauer'; wd at denx.de; u-boot at lists.denx.de
Subject: Re: [U-Boot]working with loadb & bootm on u-boot-v2 for imx27ads
Board

Lejin K Joy said the following on 09/25/2008 05:06 AM:
> I want to load the Linux Kernel Zimage on to RAM. As per the documentation
> we have used the following command to load zImage using Kermit protocol.
>
> " U-boot-v2> loadb -c zImage "
>
> (Also tried " U-boot-v2> loadb -f zImage ")
>
> Which successfully downloads zimage to the file with default offset set as
> 0x00000000.....
>   
U-Boot V2 uses a filesystem. when you did loadb -c -f zImage, it
downloaded the image to the file called zImage. zImage is stored within
the ramfs filesystem. (the concepts are very similar to an OS with
restrictions). This is slightly different from what you want to achieve
I think.
> a) But I am not able to understand to which location in RAM this image is
> written to? b) Please let me know how exactly to load kernel image to
> specific location on RAM?
>   
Look for the device node which shows the RAM/NOR/NAND you need. this
might be /dev/mem or (in my OMAP3430 case) /dev/ram0 - also see "help
loadb". Loadb takes the following options:
-f file - where to download to
-o offset - what offset to download - defaults to 0
-b baud - baudrate at which to download - defaults to console baudrate
-c - Create file if it is not present - default disabled
In your case, lets say: your ram starts at 0x80000000 and is denoted by
/dev/ram0. If you want to download to offset 0x3000 in ram, you can do
loadb -f /dev/ram0 -o 0x3000. this will essentially download to 0x80003000.

+ you now have the flexibility of downloading straight to NOR, NAND or
to even a file within u-boot v2's ramfs!! - so you can store and share
commonly used scripts modules etc.. tons of similar flexibility exists.
> c) Also how we can change the default location since the user is not given
> an option to mention the address.
>   
as explained above.
> d) How to load the file " zImage" to RAM?
>   
if you want to copy a file from ramfs to a "specific location" just do
the cp command!
> I was intending to do the following steps :
>
> 	>> loadb 0x100000 zimage
> 	>> loadb 0x1000000 ramdisk.gz 
> 	>> bootm 0x100000 0x1000000
>
> Please help me out as I am using U-boot-V2 for the first time.
>   
Does the above explanation help? in u-boot-v2, you can infact run "help
<command name>" or do a make docs And if you have graphviz latex etc
installed, you will get a html documentation in Documentation/html.

Note: I created a few useful platform independent tools for U-boot
(should work for both U-boot v2 and V1). they are available in [1].
>
> -----Original Message-----
> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de]
On
> Behalf Of Lejin K Joy
> Sent: Tuesday, September 23, 2008 9:49 PM
> To: 'Robert Schwebel'; 'Sascha Hauer'
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] u-boot-v2 for imx27 Board
>   
Try not to top post. see [2] and mailing list ettiquette.
Regards,
Nishanth Menon

[1] http://code.google.com/p/omap-u-boot-utils/
[2] http://en.wikipedia.org/wiki/Posting_style

----------------------------------------------------------------------------
--------

Hi Nishanth,

Thanks for your inputs. 

Still I am one step behind. I was successfully able to download the Zimage
by following command; but I am failing at the command to execute the image
loaded to RAM which has base address 0xc0000000. The "go" command displays
"## Starting application at 0xA0100000 ..." and hang up.

---------------
uboot:/ loadb -f /dev/ram0 -o 0x100000
## Ready for binary (kermit) download to 0x00100000 offset on /dev/ram0
device a
t 115200 bps...
## Total Size      = 0x0014deb9 = 1367737 Bytes

uboot:/ go 0xa0100000
## Starting application at 0xA0100000 ...

-----------

Please find the detailed boot log below : I cant correctly execute the  the
"bootm" command as well. Please guide : 

------------
U-Boot 2.0.0-rc5-git (Sep 25 2008 - 16:57:32)

Board: Freescale i.MX27 ADS
mpll:     265999329 Hz
spll:     239999725 Hz
arm:      177332886 Hz
perclk1:    8866644 Hz
perclk2:   17733288 Hz
perclk3:   44333221 Hz
perclk4:   17733288 Hz
clkin26:   26000000 Hz
ahb:       44333221 Hz
ipg:       22166610 Hz
Stack space : 0xa7af8000 -> 0xa7b00000 (size 32 kB)
Open /dev/env0 No such file or directory
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...
set parameter: No such device
set parameter: No such device
set parameter: No such device
set parameter: No such device
no such device: /dev/nor0

Hit any key to stop autoboot:  0
set parameter: No such device
set parameter: No such device
set parameter: No such device
set parameter: No such device
Current ethernet device not set!
Current ethernet device not set!
Bad Magic Number
uboot:/ printenv
locals:
kernel=net
root=net
ip=dhcp
uimage=uImage-mx27ads
jffs2=root-mx27ads.jffs2
autoboot_timeout=3
nfsroot=/tmp/imx27ads
bootargs=console=ttymxc0,115200
mtdparts=128k(uboot)ro,128k(ubootenv),1536k(kernel),-(root)
rootpart=/dev/mtdblock3
globals:
PATH=/env/bin

uboot:/ loadb -f /dev/ram0 -o 0x100000
## Ready for binary (kermit) download to 0x00100000 offset on /dev/ram0
device a
t 115200 bps...
## Total Size      = 0x0014deb9 = 1367737 Bytes

uboot:/ bootm
Usage:
boot application image

uboot:/ bootm -h
bootm advanced options:
 -r <initrd>    specify an initrd image
 -a <arch>      use architecture number <arch>

uboot:/ bootm -a ARM 2 -r /dev/ram0
use initrd /dev/ram0
Bad Magic Number

uboot:/ go 0xA0100000
## Starting application at 0xA0100000 ...
--------------

Please guide.

Thanks for your support,
Lejin

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Nishanth Menon]

On Thu, Sep 25, 2008 at 8:04 AM, Lejin K Joy <lejin@spacomp.com> wrote:
>
> ---------------
> uboot:/ loadb -f /dev/ram0 -o 0x100000
Do you have /dev/ram0? is it mapped to 0xa0000000? there could be
issues with mach-types.. I am not sure though.. I am not entirely sure
about imx boot procedure(I am an OMAP guy ;) )..but it could be uImage
you need there? I am not too sure.. does the piggy relocate the
kernel? I am not too sure.. probably the kernel details would help..

> ## Ready for binary (kermit) download to 0x00100000 offset on /dev/ram0
> device a
> t 115200 bps...
> ## Total Size      = 0x0014deb9 = 1367737 Bytes
>
> uboot:/ go 0xa0100000
Should'nt this be bootm 0xa0100000?

Regards,
Nishanth Menon

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Lejin K Joy]

-----Original Message-----
From: Nishanth Menon [mailto:menon.nishanth at gmail.com] 
Sent: Thursday, September 25, 2008 7:07 PM
To: Lejin K Joy
Cc: Robert Schwebel; Sascha Hauer; wd at denx.de; u-boot at lists.denx.de
Subject: Re: [U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads
Board

On Thu, Sep 25, 2008 at 8:04 AM, Lejin K Joy <lejin@spacomp.com> wrote:
>
> ---------------
> uboot:/ loadb -f /dev/ram0 -o 0x100000
Do you have /dev/ram0? is it mapped to 0xa0000000? there could be
issues with mach-types.. I am not sure though.. I am not entirely sure
about imx boot procedure(I am an OMAP guy ;) )..but it could be uImage
you need there? I am not too sure.. does the piggy relocate the
kernel? I am not too sure.. probably the kernel details would help..

> ## Ready for binary (kermit) download to 0x00100000 offset on /dev/ram0
> device a
> t 115200 bps...
> ## Total Size      = 0x0014deb9 = 1367737 Bytes
>
> uboot:/ go 0xa0100000
Should'nt this be bootm 0xa0100000?

Regards,
Nishanth Menon

-----------------------------


Hi All,

The " bootm 0xa0100000"  option is not helping.... It's displaying "could
not open : No Such file or directory" And the help  says the option is bootm
[option] image. But nothing helps.

The image being tried is getting loaded on the same board when board is
flashed with redboot using the following commands.

	1) load -r -b 0x100000 -m xmodem zimage
	2) load -v -r -b 0x01000000 -m xmodem  ramdisk.gz 
	3) exec -r 0x001000000 -s 0x00600000 -b 0x100000 -l 0x00200000 -c
"init=/linuxrc console=ttymxc0,115200 root=/dev/ram"

If any suggestions, please share..!!

Thanks,
Lejin

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Lejin K Joy]

-----Original Message-----
From: Nishanth Menon [mailto:menon.nishanth at gmail.com] 
Sent: Thursday, September 25, 2008 4:33 PM
To: Lejin K Joy
Cc: 'Robert Schwebel'; 'Sascha Hauer'; wd at denx.de; u-boot at lists.denx.de
Subject: Re: [U-Boot]working with loadb & bootm on u-boot-v2 for imx27ads
Board

Lejin K Joy said the following on 09/25/2008 05:06 AM:
> I want to load the Linux Kernel Zimage on to RAM. As per the documentation
> we have used the following command to load zImage using Kermit protocol.
>
> " U-boot-v2> loadb -c zImage "
>
> (Also tried " U-boot-v2> loadb -f zImage ")
>
> Which successfully downloads zimage to the file with default offset set as
> 0x00000000.....
>   
U-Boot V2 uses a filesystem. when you did loadb -c -f zImage, it
downloaded the image to the file called zImage. zImage is stored within
the ramfs filesystem. (the concepts are very similar to an OS with
restrictions). This is slightly different from what you want to achieve
I think.
> a) But I am not able to understand to which location in RAM this image is
> written to? b) Please let me know how exactly to load kernel image to
> specific location on RAM?
>   
Look for the device node which shows the RAM/NOR/NAND you need. this
might be /dev/mem or (in my OMAP3430 case) /dev/ram0 - also see "help
loadb". Loadb takes the following options:
-f file - where to download to
-o offset - what offset to download - defaults to 0
-b baud - baudrate at which to download - defaults to console baudrate
-c - Create file if it is not present - default disabled
In your case, lets say: your ram starts at 0x80000000 and is denoted by
/dev/ram0. If you want to download to offset 0x3000 in ram, you can do
loadb -f /dev/ram0 -o 0x3000. this will essentially download to 0x80003000.

+ you now have the flexibility of downloading straight to NOR, NAND or
to even a file within u-boot v2's ramfs!! - so you can store and share
commonly used scripts modules etc.. tons of similar flexibility exists.
> c) Also how we can change the default location since the user is not given
> an option to mention the address.
>   
as explained above.
> d) How to load the file " zImage" to RAM?
>   
if you want to copy a file from ramfs to a "specific location" just do
the cp command!
> I was intending to do the following steps :
>
> 	>> loadb 0x100000 zimage
> 	>> loadb 0x1000000 ramdisk.gz 
> 	>> bootm 0x100000 0x1000000
>
> Please help me out as I am using U-boot-V2 for the first time.
>   
Does the above explanation help? in u-boot-v2, you can infact run "help
<command name>" or do a make docs And if you have graphviz latex etc
installed, you will get a html documentation in Documentation/html.

Note: I created a few useful platform independent tools for U-boot
(should work for both U-boot v2 and V1). they are available in [1].
>
> -----Original Message-----
> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de]
On
> Behalf Of Lejin K Joy
> Sent: Tuesday, September 23, 2008 9:49 PM
> To: 'Robert Schwebel'; 'Sascha Hauer'
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] u-boot-v2 for imx27 Board
>   
Try not to top post. see [2] and mailing list ettiquette.
Regards,
Nishanth Menon

[1] http://code.google.com/p/omap-u-boot-utils/
[2] http://en.wikipedia.org/wiki/Posting_style


-------------------------------------------------

Hi,

I am working on freescale IMX-27ADS board using U-boot-v2 bootloader and
linux-2.6.25-rc7 source.I have downloaded U-boot-V2 bootloader into the
board.Now i am trying to boot linux-2.6.25 kernel on this board. I am using
gcc-4.1.2-glibc-2.5-nptl-3 cross compiler toolchain to build uboot.bin and
uImage.

We are using the below procedures to build uImage from linux souce.

1.
ARCH=arm
CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-l
inux-gnueabi/bin/arm-none-linux-gnueabi- make clean

2.ARCH=arm
CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-l
inux-gnueabi/bin/arm-none-linux-gnueabi- make menuconfig

3.ARCH=arm
CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-l
inux-gnueabi/bin/arm-none-linux-gnueabi- make

4.arm-none-linux-gnueabi-objcopy -o binary -R .note -R .comment -S vmlinux
linux.bin

5.gzip -9 linux.bin

6.mkimage   -A arm -O linux -T kernel -C none  -a 0xa1000000 -e 
0xa1000000 -n "linux-2.6.25" -d linux.bin.gz uImage

We are loading uImage to IMX27ADS in kermit mode. We are trying to boot
kernel using bootm command but the kernel got stuck in starting kernel
memory location.
Please find the logfile attachment.

We are laoding uImage on target using the following commands.

1. loadb -f /dev/ram0 -o 0x1000000 uImage

2. bootm /dev/ram0

Please suggest me where i am going wrong. It will be a great help.

Thanks,
Lejin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imxads27_u-boot-v2_log.txt
Type: text/enhanced
Size: 1563 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20081009/7dd91001/attachment.bin 

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Lejin K Joy]

-----Original Message-----
From: Nishanth Menon [mailto:menon.nishanth at gmail.com] 
Sent: Thursday, September 25, 2008 7:07 PM
To: Lejin K Joy
Cc: Robert Schwebel; Sascha Hauer; wd at denx.de; u-boot at lists.denx.de
Subject: Re: [U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads
Board

On Thu, Sep 25, 2008 at 8:04 AM, Lejin K Joy <lejin@spacomp.com> wrote:
>
> ---------------
> uboot:/ loadb -f /dev/ram0 -o 0x100000
Do you have /dev/ram0? is it mapped to 0xa0000000? there could be
issues with mach-types.. I am not sure though.. I am not entirely sure
about imx boot procedure(I am an OMAP guy ;) )..but it could be uImage
you need there? I am not too sure.. does the piggy relocate the
kernel? I am not too sure.. probably the kernel details would help..

> ## Ready for binary (kermit) download to 0x00100000 offset on /dev/ram0
> device a
> t 115200 bps...
> ## Total Size      = 0x0014deb9 = 1367737 Bytes
>
> uboot:/ go 0xa0100000
Should'nt this be bootm 0xa0100000?

Regards,
Nishanth Menon

-----------------------------


Hi All,

The " bootm 0xa0100000"  option is not helping.... It's displaying "could
not open : No Such file or directory" And the help  says the option is bootm
[option] image. But nothing helps.

The image being tried is getting loaded on the same board when board is
flashed with redboot using the following commands.

	1) load -r -b 0x100000 -m xmodem zimage
	2) load -v -r -b 0x01000000 -m xmodem  ramdisk.gz 
	3) exec -r 0x001000000 -s 0x00600000 -b 0x100000 -l 0x00200000 -c
"init=/linuxrc console=ttymxc0,115200 root=/dev/ram"

If any suggestions, please share..!!

Thanks,
Lejin

[U-Boot] working with loadb & bootm on u-boot-v2 for imx27ads Board

[Lejin]

> -----------------------------
> 
> Hi All,
> 
> loadb -f /dev/ram0 -o 0x100000 adn then 
> the " bootm 0xa0100000"  option is not helping.... It's displaying "could
> not open : No Such file or directory" And the help  says the option is bootm
> [option] image. But nothing helps.
> 
> The image being tried is getting loaded on the same board when board is
> flashed with redboot using the following commands.
> 
> 	1) load -r -b 0x100000 -m xmodem zimage
> 	2) load -v -r -b 0x01000000 -m xmodem  ramdisk.gz 
> 	3) exec -r 0x001000000 -s 0x00600000 -b 0x100000 -l 0x00200000 -c
> "init=/linuxrc console=ttymxc0,115200 root=/dev/ram"
> 
> If any suggestions, please share..!!
> 
> Thanks,
> Lejin
> 
---------------------------

Hi All,

If anybody has tried with the bootm option for executing the Linux ZImage 
already loaded on RAM, on u-boot-v2 Please provide your suggestions.

Thanks,
Lejin