how to flash barebox and set root variable?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am quite new to barebox. Before I had little bit experience in u-Boot.

My Barebox version is: barebox 2012.03.0-00162-g3f84abc-dirty (Sep 24 2012 - 10:51:42)

I can mount a Linaro freescale mx53 sd-card setup. I think it has one Fat8 partion, because Fat32 and Fat16 are not recognized by my barebox version.

When I boot the uImage, it complains about not setting the "root=" parameter, when I give it as an argument it does not work.

In my u-Boot setup all I need to do was write:

setenv bootcmd "fatload mmc 0:2 0x70800000 uImage;bootm" setenv bootargs "console=tty0 console=ttymxc0,115200n8 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro"

Maybe this is a version isuue? I managed to build the latest kernel what is the procedure to "flash" the new barebox.bin? Can I use the cp command for this, or do I need to flash it via OCD? If so what are good tools in linux to achieve that task?

OK a lot of questions. Most probably already answered, but had not found google.

What board do you have? Is it one supported by barebox or do you have your own patches?

What to do next depends on the environment you have. Please send the output of 'ls -l /env'.

Using a more recent version of barebox probably is a good idea. We gained a lot of interesting features in the last year.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Sascha,

thank you very much for your help.

Quoted 2 lines

What board do you have? Is it one supported by barebox or do you have your own patches?

The board is a imx536 based [1]. The expansion board for this is self made. We connect RX, TX, Ground to a OCD-Adapter [2] and are able to communicate with barebox.

My Barebox version is: barebox 2012.03.0-00162-g3f84abc-dirty (Sep 24 2012 - 10:51:42) it was already flashed in nor when we recieved the board.

What to do next depends on the environment you have. Please send the output of 'ls -l /env'.

I haven't downloaded the CD images they provide. Do you know whether there are barebox sources provided on the CDs?

Hello Sascha,

Quoted 2 lines

What to do next depends on the environment you have. Please send the output of 'ls -l /env'.

that would be:

drwxrwxrwx 0 . drwxrwxrwx 0 .. -rwxrwxrwx
1230 config drwxrwxrwx 0 bin

contents of /env/bin is:

-rwxrwxrwx 817 _update_help -rwxrwxrwx 447
update_nfs -rwxrwxrwx 1362 update -rwxrwxrwx 285 mv
-rwxrwxrwx 3445 boot -rwxrwxrwx 590 init -rwxrwxrwx
21 hush_hack -rwxrwxrwx 571 _boot_help -rwxrwxrwx 702
_update

and ls -l /dev prints:

cr-------- 4294967295 zero crw------- 536870912 ram0 crw-------
11108 defaultenv crw------- 4294967295 mem crw------- 64
phy0 crw------- 3616538624 disk0 crw------- 4193792 disk0.0
crw------- 54525952 disk0.1 crw------- 8388608 nor0 crw-------
917504 self0 crw------- 131072 env0 crw------- 917504
nor0.barebox crw------- 131072 nor0.bareboxenv crw-------
7340032 nor0.kernel

well, have tried to make an barebox.bin start disk with the cat barebox.bin > /dev/sdX, but not sure how to proceed to run from sd-card.

On a different try, I copied barebox.bin on a fat12 sd partition and tried to update on the mounted partion:

update -t barebox -d nor -f barebox.bin

but the syntax is:

type update -t barebox -d <nor|nand> [-m tftp|xmodem|nfs] [-f imagename] to update barebox into flash

"-m" does not give my disk as source, so I guess I have to get tftp to work..

Quoted 2 lines

I haven't downloaded the CD images they provide. Do you know whether there are barebox sources provided on the CDs?

On CD there is basically buildroot and the config files for barebox I have attached to this mail.

Just to recall: my problem is that i do not know how to provide "root=" parameter to my barebox environemnt. I load the zImage by mounting partition by hand and running "bootm".

Thanks for help, Greetings,

Adam

_______________________________________________ barebox mailing list [email protected]
http://lists.infradead.org/mailman/listinfo/barebox

One thing to add:

I managed to run tftpd-hpa server on my debian box and tried to update kernel to nor0.kernel. I run:

flashing barebox.bin to /dev/nor0.kernel

Unknown command 'tftp' - try 'help'

Quoted 3 lines

flashing barebox.bin to /dev/nor0.kernel

Quoted 2 lines

Unknown command 'tftp' - try 'help'

Seems tftp command is not compiled in. Ensure that you have CONFIG_CMD_TFTP in your .config.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 5 lines · Alexander Shiyan

Quoted 3 lines

flashing barebox.bin to /dev/nor0.kernel

Quoted 2 lines

Unknown command 'tftp' - try 'help'

Seems tftp command is not compiled in. Ensure that you have CONFIG_CMD_TFTP in your .config.

Thanks Alexander,

but my barebox binary is gone :(. Have been a bit careles... I would need to flash the binary over my OCD USB controller, but do not realy have a clue how to do this.
I am waiting for support reply for this ICnova iMX536 SODIMM module, they should give me some steps how to proceed.

Quoted 9 lines · Adam Furmanczuk

Quoted 9 lines

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Quoted 5 lines · Alexander Shiyan

Quoted 5 lines

Quoted 3 lines

Quoted 3 lines

flashing barebox.bin to /dev/nor0.kernel

Quoted 2 lines

Quoted 2 lines

Unknown command 'tftp' - try 'help'

Seems tftp command is not compiled in. Ensure that you have CONFIG_CMD_TFTP in your .config.

Quoted 7 lines

Quoted 7 lines

Thanks Alexander,

but my barebox binary is gone :(. Have been a bit careles... I would need to flash the binary over my OCD USB controller, but do not realy have a clue how to do this. I am waiting for support reply for this ICnova iMX536 SODIMM module, they should give me some steps how to proceed.

Connect your board via USB to a host. Do you see a device? If yes,
enable CONFIG_ARCH_IMX_USBLOADER in a recent barebox. After
compiling you will have scripts/imx/imx-usb-loader which you can use to recover via USB.

Quoted 7 lines · Adam Furmanczuk

Quoted 4 lines · Alexander Shiyan

Quoted 2 lines

flashing barebox.bin to /dev/nor0.kernel

Quoted 1 line

Unknown command 'tftp' - try 'help'

Seems tftp command is not compiled in. Ensure that you have CONFIG_CMD_TFTP in your .config.

Thanks Alexander,

Quoted 5 lines

but my barebox binary is gone . Have been a bit careles... I would need to flash the binary over my OCD USB controller, but do not realy have a clue how to do this. I am waiting for support reply for this ICnova iMX536 SODIMM module, they should give me some steps how to proceed.

[...] CONFIG_ARCH_IMX_USBLOADER in a recent barebox. After compiling you will have scripts/imx/imx-usb-loader

********* *POCZATEK CZESCI SZYFROWANEJ / PODPISANEJ* *********

Quoted 14 lines · Sascha Hauer

Quoted 14 lines

Quoted 12 lines · Adam Furmanczuk

Quoted 12 lines · Alexander Shiyan

Quoted 4 lines

Quoted 4 lines

Quoted 2 lines

Quoted 2 lines

flashing barebox.bin to /dev/nor0.kernel

Quoted 1 line

Quoted 1 line

Unknown command 'tftp' - try 'help'

Seems tftp command is not compiled in. Ensure that you have CONFIG_CMD_TFTP in your .config.

Thanks Alexander,

but my barebox binary is gone . Have been a bit careles... I would need to flash the binary over my OCD USB controller, but do not realy have a clue how to do this. I am waiting for support reply for this ICnova iMX536 SODIMM module, they should give me some steps how to proceed.

Quoted 2 lines

Quoted 2 lines

[...] CONFIG_ARCH_IMX_USBLOADER in a recent barebox. After compiling you will have scripts/imx/imx-usb-loader

Hi Sascha,

I have included the option: CONFIG_ARCH_IMX_USBLOADER=y then run make clean and then make again, but there is no such file, tried to search recursively for similar file in barebox top directory with:
find ./ -iname \*usb-loader\*

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 17 lines · Adam Furmanczuk

********* *POCZATEK CZESCI SZYFROWANEJ / PODPISANEJ* *********

Quoted 14 lines · Sascha Hauer

Quoted 14 lines

Quoted 12 lines · Adam Furmanczuk

Quoted 12 lines · Alexander Shiyan

Quoted 4 lines

Quoted 4 lines

Quoted 2 lines

Quoted 2 lines

flashing barebox.bin to /dev/nor0.kernel

Quoted 1 line

Quoted 1 line

Unknown command 'tftp' - try 'help'

Seems tftp command is not compiled in. Ensure that you have CONFIG_CMD_TFTP in your .config.

Thanks Alexander,

but my barebox binary is gone . Have been a bit careles... I would need to flash the binary over my OCD USB controller, but do not realy have a clue how to do this. I am waiting for support reply for this ICnova iMX536 SODIMM module, they should give me some steps how to proceed.

Quoted 9 lines

Quoted 2 lines

Quoted 2 lines

[...] CONFIG_ARCH_IMX_USBLOADER in a recent barebox. After compiling you will have scripts/imx/imx-usb-loader

Hi Sascha,

I have included the option: CONFIG_ARCH_IMX_USBLOADER=y then run make clean and then make again, but there is no such file, tried to search recursively for similar file in barebox top directory with:
find ./ -iname \*usb-loader\*

My bad, i got the latest git snaphot (699-bcc9) and there is USBLOADER.. have still some issues with compiling it. There is "memory bank" error [1]. Have seen there was a patch recently, but do not know the option to enable/disable

Quoted 31 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Quoted 18 lines · Adam Furmanczuk

********* *POCZATEK CZESCI SZYFROWANEJ / PODPISANEJ* *********

Quoted 15 lines · Sascha Hauer

Quoted 15 lines

Quoted 13 lines · Adam Furmanczuk

Quoted 13 lines · Alexander Shiyan

Quoted 4 lines

Quoted 4 lines

Quoted 2 lines

Quoted 2 lines

flashing barebox.bin to /dev/nor0.kernel

Quoted 1 line

Quoted 1 line

Unknown command 'tftp' - try 'help'

Seems tftp command is not compiled in. Ensure that you have CONFIG_CMD_TFTP in your .config.

Thanks Alexander,

but my barebox binary is gone . Have been a bit careles... I would need to flash the binary over my OCD USB controller, but do not realy have a clue how to do this. I am waiting for support reply for this ICnova iMX536 SODIMM module, they should give me some steps how to proceed.

Quoted 9 lines

Quoted 2 lines

Quoted 2 lines

[...] CONFIG_ARCH_IMX_USBLOADER in a recent barebox. After
compiling you will have scripts/imx/imx-usb-loader

Hi Sascha,

I have included the option: CONFIG_ARCH_IMX_USBLOADER=y then run make clean and then make again, but there is no such file, tried to search recursively for similar file in barebox top directory with: find ./ -iname \*usb-loader\*

Quoted 4 lines

My bad, i got the latest git snaphot (699-bcc9) and there is USBLOADER.. have still some issues with compiling it. There is "memory bank" error [1]. Have seen there was a patch recently, but do not know the option to enable/disable

When CONFIG_ARCH_IMX_USBLOADER is enabled in your config you can do:

make scripts/imx/

This should build the tool only.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 12 lines · Sascha Hauer

Quoted 4 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Quoted 1 line · Adam Furmanczuk

********* *POCZATEK CZESCI SZYFROWANEJ / PODPISANEJ* *********

When CONFIG_ARCH_IMX_USBLOADER is enabled in your config you can do:

make scripts/imx/

This should build the tool only.

In the current 699-bcc9 branch i run:

make ARCH=arm freescale_mx53_loco_defconfig

than i edit the .config by hand and set CONFIG_ARCH_IMX_USBLOADER=y when running: make scripts/imx

it tells me no goals. nothing to do.

I run gcc on your script file directly, but the libush.h is misssing I should get it from the MX53 loco project?

Quoted 25 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Quoted 5 lines · Sascha Hauer

Quoted 3 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 12.06.2013 08:12, Adam Furmanczuk wrote:

Quoted 9 lines

Quoted 2 lines

Quoted 2 lines

********* *POCZATEK CZESCI SZYFROWANEJ / PODPISANEJ*
*********

When CONFIG_ARCH_IMX_USBLOADER is enabled in your config you can do:

make scripts/imx/

This should build the tool only.

In the current 699-bcc9 branch i run:

make ARCH=arm freescale_mx53_loco_defconfig

than i edit the .config by hand and set CONFIG_ARCH_IMX_USBLOADER=y when running: make scripts/imx

Quoted 4 lines

it tells me no goals. nothing to do.

I run gcc on your script file directly, but the libush.h is misssing I should get it from the MX53 loco project?

You need this from the host. On debian for example the packet is named libusb-1.0-0-dev.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, I compiled with gcc imx-usb-loader.c -I/usr/include/libusb-1.0/ And had some "undefined reference" errors [1]. Probably have to adjust some path when running in barebox/scripts/imx/ directory?

I use also debian (wheezy) as host. Details about libusb-dev package [2].

Quoted 9 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, I compiled with gcc imx-usb-loader.c -I/usr/include/libusb-1.0/ And had some "undefined reference" errors [1]. Probably have to adjust some path when running in barebox/scripts/imx/ directory?

I use also debian (wheezy) as host. Details about libusb-dev package [2].

Ok, here is exactly what to do:

export ARCH=arm
export CROSS_COMPILE=/path/to/arm-linux-gcc-
make freescale_mx51_babbage_defconfig
make menuconfig
System Type --->
i.MX specific settings --->
[*] compile imx-usb-loader
make

This should compile without errors and the imx-usb-loader tool should be compiled, provided you have the libusb host tool installed.

Quoted 19 lines · Adam Furmanczuk

Quoted 18 lines

Quoted 10 lines

Quoted 10 lines

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

OK, I compiled with gcc imx-usb-loader.c -I/usr/include/libusb-1.0/ And had some "undefined reference" errors [1]. Probably have to adjust some path when running in barebox/scripts/imx/ directory?

I use also debian (wheezy) as host. Details about
libusb-dev package [2].

Ok, here is exactly what to do:

export ARCH=arm export CROSS_COMPILE=/path/to/arm-linux-gcc- make freescale_mx51_babbage_defconfig make menuconfig System Type ---> i.MX specific settings ---> [*] compile imx-usb-loader make

Quoted 3 lines

Quoted 3 lines

This should compile without errors and the imx-usb-loader tool should be compiled, provided you have the libusb host tool installed.

Probably some usb-related headers on Adam system placed in non-standard directories, since tool is not builded or makes some errors. Maybe we need to use pkg-config for these stuffs?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I restate this question from my previous thread "how to flash and set root variable". Thanks very much to Sascha and Alexander for introducing into barebox building and flashing.

I have a basic scenario. Want to boot uImage and then hand over to the root partition. With u-Boot this was very easy:

setenv bootargs "console=tty0 console=ttymxc0,115200n8 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro"

With barebox however, when I boot the uImage, it complains about not setting correct "root=".:

[ 1.718527] VFS: Cannot open root device "(null)" or
unknown-block(0,0): error -6
[ 1.726226] Please append a correct "root=" boot option; here are the

available partitions:

Now what i do in Barbox is the following;

(hint enter to go into console)
barebox@myhost:/ mkdir /media2
barebox@myhost:/ mount /dev/disk0.1 fat /media2 barebox@myhost:/ bootm /media2/uImage root=/dev/mmcblk0p3 rootfstype=ext4

Hi Adam,

Quoted 18 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

I restate this question from my previous thread "how to flash and set root variable". Thanks very much to Sascha and Alexander for introducing into barebox building and flashing.

I have a basic scenario. Want to boot uImage and then hand over to the root partition. With u-Boot this was very easy:

setenv bootargs "console=tty0 console=ttymxc0,115200n8 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro"

With barebox however, when I boot the uImage, it complains about
not setting correct "root=".:

[ 1.718527] VFS: Cannot open root device "(null)" or 

Quoted 8 lines

unknown-block(0,0): error -6 [ 1.726226] Please append a correct
"root=" boot option; here are the available partitions:

Now what i do in Barbox is the following;

(hint enter to go into console) barebox@myhost:/ mkdir /media2 barebox@myhost:/ mount /dev/disk0.1 fat /media2 barebox@myhost:/
bootm /media2/uImage root=/dev/mmcblk0p3 rootfstype=ext4

the bootm command evaluates the 'bootargs' environment variable, so before executing bootm do a:

export bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"

(sidenote: This is not documented with 'help bootm', shame on us. Try the 'magicvar' command instead which lists all variables with special meanings)

Sascha

Quoted 26 lines

Quoted 14 lines

I restate this question from my previous thread "how to flash and set root variable". Thanks very much to Sascha and Alexander for introducing into barebox building and flashing.

I have a basic scenario. Want to boot uImage and then hand over to the root partition. With u-Boot this was very easy:

setenv bootargs "console=tty0 console=ttymxc0,115200n8 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro"

With barebox however, when I boot the uImage, it complains about
not setting correct "root=".:

[ 1.718527] VFS: Cannot open root device "(null)" or 

Quoted 8 lines

unknown-block(0,0): error -6 [ 1.726226] Please append a correct
"root=" boot option; here are the available partitions:

Now what i do in Barbox is the following;

(hint enter to go into console) barebox@myhost:/ mkdir /media2 barebox@myhost:/ mount /dev/disk0.1 fat /media2 barebox@myhost:/
bootm /media2/uImage root=/dev/mmcblk0p3 rootfstype=ext4

the bootm command evaluates the 'bootargs' environment variable, so before executing bootm do a:

Quoted 8 lines

export bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"

(sidenote: This is not documented with 'help bootm', shame on us. Try the 'magicvar' command instead which lists all variables with special meanings)

Sascha

Hi Sascha,

it does not seem to work for me, I typed:

mkdir /mnt/disk1
bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"
mount /dev/disk0.1 fat /mnt/disk1
bootm /mnt/disk1/uImage

I choose different values for root, like "mmcblk0p3","/dev/mmcblk0p1", "b303" ...

I am running MX53QSB with barebox 2013.05 build get this output:

VFS: Cannot open root device "(null)" or unknown-block(2,0) Please append a correct "root=" boot option; here are the available partitions:
b300 3872256 mmcblk0 driver: mmcblk
b301 512 mmcblk0p1
b302 16384 mmcblk0p2
b303 3854336 mmcblk0p3

Kernel panic - not syncing: VFS: Unable to mount root fs on

unknown-block(2,0)

Note: Unknown block is always (2,0) no matter what i try to specify.

This problem might be related to mx53 architecture only.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 33 lines · Sascha Hauer

Hi Adam,

Quoted 18 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

I restate this question from my previous thread "how to flash and set root variable". Thanks very much to Sascha and Alexander for introducing into barebox building and flashing.

I have a basic scenario. Want to boot uImage and then hand over to the root partition. With u-Boot this was very easy:

setenv bootargs "console=tty0 console=ttymxc0,115200n8 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro"

With barebox however, when I boot the uImage, it complains about
not setting correct "root=".:

[ 1.718527] VFS: Cannot open root device "(null)" or 

Quoted 8 lines

unknown-block(0,0): error -6 [ 1.726226] Please append a correct
"root=" boot option; here are the available partitions:

Now what i do in Barbox is the following;

(hint enter to go into console) barebox@myhost:/ mkdir /media2 barebox@myhost:/ mount /dev/disk0.1 fat /media2 barebox@myhost:/
bootm /media2/uImage root=/dev/mmcblk0p3 rootfstype=ext4

the bootm command evaluates the 'bootargs' environment variable, so before executing bootm do a:

Quoted 8 lines

export bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"

(sidenote: This is not documented with 'help bootm', shame on us. Try the 'magicvar' command instead which lists all variables with special meanings)

Sascha

Hi Sascha,

it does not seem to work for me, I typed:

mkdir /mnt/disk1
bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"
mount /dev/disk0.1 fat /mnt/disk1
bootm /mnt/disk1/uImage

I choose different values for root, like "mmcblk0p3","/dev/mmcblk0p1", "b303" ...

I am running MX53QSB with barebox 2013.05 build get this output:

Quoted 55 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Quoted 37 lines · Sascha Hauer

Hi Adam,

Quoted 23 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

I restate this question from my previous thread "how to flash and set root variable". Thanks very much to Sascha and Alexander for introducing into barebox building and flashing.

I have a basic scenario. Want to boot uImage and then hand over to the root partition. With u-Boot this was very easy:

setenv bootargs "console=tty0 console=ttymxc0,115200n8 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro"

With barebox however, when I boot the uImage, it complains about not setting correct "root=".:

[ 1.718527] VFS: Cannot open root device "(null)" or 

unknown-block(0,0): error -6 [ 1.726226] Please append a correct "root=" boot option; here are the available partitions:

Quoted 6 lines

Now what i do in Barbox is the following;

(hint enter to go into console) barebox@myhost:/ mkdir /media2 barebox@myhost:/ mount /dev/disk0.1 fat /media2 barebox@myhost:/ bootm /media2/uImage root=/dev/mmcblk0p3 rootfstype=ext4

the bootm command evaluates the 'bootargs' environment variable, so before executing bootm do a:

Quoted 8 lines

export bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"

(sidenote: This is not documented with 'help bootm', shame on us. Try the 'magicvar' command instead which lists all variables with special meanings)

Sascha

Hi Sascha,

it does not seem to work for me, I typed:

Quoted 8 lines

mkdir /mnt/disk1 bootargs="root=/dev/mmcblk0p3 rootfstype=ext4" mount /dev/disk0.1 fat /mnt/disk1 bootm /mnt/disk1/uImage

I choose different values for root, like
"mmcblk0p3","/dev/mmcblk0p1", "b303" ...

I am running MX53QSB with barebox 2013.05 build get this output:

The kernel normally prints the commandline during startup. Could you post it?

Then, are you using some defconfig or do you you have out of tree patches?

Also, could you post the output of 'devinfo global'?

Sascha

-----BEGIN PGP SIGNED MESSAGE-----
Hi Sascha, hi Alexander,

rootwait parameter in bootargs did not helped. I compiled barebox and kernel Image from busybox. I added in busybox extra defconfig parameter for the imx53 board for barebox. No extra pachtes. Have sdma module in root partion in /lib directory, but it never change-roots to that partition anyway.

With u-Boot the same bootargs are OK. My new project requires to use barebox.

Output of devinfo global [1] and bootlog [2]

Greetings,

Adam

[1] http://pastebin.com/yyQjtpbT

barebox@Freescale i.MX53 LOCO:/ devinfo global
resources:
driver: none
bus: none

Parameters:
system.reset = POR
bootm.image =
bootm.oftree =
bootm.initrd =
dhcp.rootpath =
dhcp.tftp_server_name =
dhcp.bootfile =
dhcp.oftree_file =
dhcp.vendor_id =
dhcp.client_id =
dhcp.user_class =
dhcp.client_uuid =

hostname = loco
user = none
autoboot_timeout = 3
boot.default = net
allow_color = true
linux.bootargs.base = console=ttymxc0,115200
linux.bootargs.dyn.ip =
linux.bootargs.dyn.root =

[2] http://pastebin.com/4PxUnm0Q

barebox@Freescale i.MX53 LOCO:/mkdir /mnt/disk1 barebox@Freescale i.MX53 LOCO:/ bootargs="root=/dev/mmcblk0p3 rootwait rootfstype=ext4"
barebox@Freescale i.MX53 LOCO:/ mount /dev/disk0.1 fat /mnt/disk1 barebox@Freescale i.MX53 LOCO:/ bootm /mnt/disk1/uImage

   Image Name:   Linux-2.6.35.3
   Created:      2013-06-13  14:17:14 UTC
   OS:           Linux
   Architecture: ARM
   Type:         Kernel Image
   Compression:  uncompressed
   Data Size:    2945628 Bytes = 2.8 MiB

Load Address: 70008000
Entry Point: 70008000

Loading OS U-Boot uImage '/mnt/disk1/uImage'
commandline: console=ttymxc0,115200
arch_number: 3273
Linux version 2.6.35.3 (testserver@Server6) (gcc version 4.7.3

(Buildroot 2013.05) ) #1 PREEMPT Thu Jun 13 16:17:07 CEST 2013
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX53 LOCO Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
250880
Kernel command line: console=ttymxc0,115200

Quoted 8 lines · Adam Furmanczuk

-----BEGIN PGP SIGNED MESSAGE----- Hi Sascha, hi Alexander,

rootwait parameter in bootargs did not helped. I compiled barebox and kernel Image from busybox. I added in busybox extra defconfig parameter for the imx53 board for barebox. No extra pachtes. Have sdma module in root partion in /lib directory, but it never change-roots to that partition anyway.

Quoted 4 lines

With u-Boot the same bootargs are OK. My new project requires to use barebox.

Output of devinfo global [1] and bootlog [2]

Please send these inline next time so that people digging through the archives can see what we are talking about.

Quoted 12 lines

Greetings,

Adam

[1] http://pastebin.com/yyQjtpbT

barebox@Freescale i.MX53 LOCO:/ devinfo global resources: driver:
none bus: none

Quoted 7 lines

Parameters: system.reset = POR bootm.image = bootm.oftree = bootm.initrd = dhcp.rootpath = dhcp.tftp_server_name = dhcp.bootfile = dhcp.oftree_file = dhcp.vendor_id = dhcp.client_id = dhcp.user_class = dhcp.client_uuid = hostname = loco user = none autoboot_timeout = 3 boot.default = net allow_color = true linux.bootargs.base = console=ttymxc0,115200 linux.bootargs.dyn.ip = linux.bootargs.dyn.root =

Ok, that's the information I was looking for.

The bootm command either uses the 'bootargs' variable or if exists, all variables beginning with "linux.bootargs.".

So to change your bootargs do:

linux.bootargs.base="console=ttymxc0,115200 ignore_loglevel whatever"

You can also add new variables:

global linux.bootargs.debug="earlyprintk"

And what you are currently looking for:

global linux.bootargs.root="root=/dev/mmcblk0p3 rootwait"

Quoted 13 lines

[2] http://pastebin.com/4PxUnm0Q

barebox@Freescale i.MX53 LOCO:/mkdir /mnt/disk1 barebox@Freescale i.MX53 LOCO:/ bootargs="root=/dev/mmcblk0p3 rootwait rootfstype=ext4" barebox@Freescale i.MX53 LOCO:/ mount /dev/disk0.1 fat /mnt/disk1 barebox@Freescale i.MX53 LOCO:/ bootm
/mnt/disk1/uImage Image Name: Linux-2.6.35.3 Created:
2013-06-13 14:17:14 UTC OS: Linux Architecture: ARM
Type: Kernel Image Compression: uncompressed Data Size:
2945628 Bytes = 2.8 MiB Load Address: 70008000 Entry Point:
70008000

Quoted 3 lines

Loading OS U-Boot uImage '/mnt/disk1/uImage' commandline:
console=ttymxc0,115200 arch_number: 3273 Linux version 2.6.35.3 (testserver@Server6) (gcc version 4.7.3

Quite an old Kernel for a new project...

Quoted 7 lines

(Buildroot 2013.05) ) #1 PREEMPT Thu Jun 13 16:17:07 CEST 2013
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Freescale MX53 LOCO Board Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 250880 Kernel command line:
console=ttymxc0,115200