[U-Boot] Default base for numbers
Hello,
I've stumbled over the fact that the length parameter for sha1sum uses 16 as default base, which I found a bit confusing.
E.g. ------------------------- U-Boot>> tftp $loadaddr uImage ... done Bytes transferred = 1976384 (1e2840 hex) U-Boot>> sha1sum $loadaddr 1976384 SHA1 for 00800000 ... 02176383 ==> 8d9cc7b167b6d1471d73d46cfc3b374091de88a6 U-Boot>> sha1sum $loadaddr 0x1e2840 SHA1 for 00800000 ... 009e283f ==> fde54f7409c785b7929d36624f77f71abd30282a ------------------------- (The second one is correct)
Is the base 16 as default for numbers common for commands in u-boot or is that just a problem of md5sum and sha1sum?
Regards,
Alexander
Dear Alexander Holler,
In message 4D3E8F9D.7040901@ahsoftware.de you wrote:
I've stumbled over the fact that the length parameter for sha1sum uses 16 as default base, which I found a bit confusing.
Read the documentation.
Is the base 16 as default for numbers common for commands in u-boot or is that just a problem of md5sum and sha1sum?
With very few exceptions all commands use base 16 input. I recommend you start reading the manual.
Best regards,
Wolfgang Denk
Am 25.01.2011 10:16, schrieb Wolfgang Denk:
Dear Alexander Holler,
In message4D3E8F9D.7040901@ahsoftware.de you wrote:
I've stumbled over the fact that the length parameter for sha1sum uses 16 as default base, which I found a bit confusing.
Read the documentation.
Is the base 16 as default for numbers common for commands in u-boot or is that just a problem of md5sum and sha1sum?
With very few exceptions all commands use base 16 input. I recommend you start reading the manual.
Thanks for the pointer, if someone else is interested, it is described in chapter 5.9. U-Boot Command Line Interface. Easy to find. ;)
Regards,
Alexander
Hi,
I change my uboot version and after it the uboot don't starts the same linux kernel:
## Booting kernel from Legacy Image at 10060000 ... Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1178673 Bytes = 1.1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
*****LOG END*****
It's a board simular to the at91rm9200dk. I start the kernel with
bootcmd2=setenv bootargs root=/dev/mtdblock9 rootfstype=squashfs ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
run bootcmd2
Can anybody give me a hint where I had to search for the error?
Mit freundlichen Grüßen
Maik Hänig
Dear Maik Hänig,
Hi,
I change my uboot version and after it the uboot don't starts the same linux kernel:
## Booting kernel from Legacy Image at 10060000 ...
_________________________________________????????
Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1178673 Bytes = 1.1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OKStarting kernel ...
*****LOG END*****
It's a board simular to the at91rm9200dk. I start the kernel with
bootcmd2=setenv bootargs root=/dev/mtdblock9 rootfstype=squashfs ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
______________________________________________________________________????????
run bootcmd2
First, I don't understand why those two addresses are not the same.
Then, are you sure your "bootcmd2" ist really what you think it is? Try a "printenv" and see whats really there.
Should you not have a "console=xxx" in your kernel parameters?
Besides once "Starting kernel ..." shows, u-boot is about to give control to the kernel, all future output would be from the kernel itself, probably needing a sane "console=xxx" parameter.
Best Regards, Reinhard
Dear Reinhard,
sorry I copied the wrong log:
U-Boot 2010.09 (Jan 24 2011 - 17:45:54)
I2C: ready DRAM: 64 MiB Flash: 32 MiB In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ## Booting kernel from Legacy Image at 30060000 ... Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1084127 Bytes = 1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
I have to kernel Images in flash. The bootcmd is copied from printenv. With the uboot version 2009.01 it works well. Is it nessesary to set a console parameter in the bootcmd in uboot version 2010.09?
Mit freundlichen Grüßen
Maik Hänig
Am 25.01.2011 11:54, schrieb Reinhard Meyer:
Dear Maik Hänig,
Hi,
I change my uboot version and after it the uboot don't starts the same linux kernel:
## Booting kernel from Legacy Image at 10060000 ...
_________________________________________????????
Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1178673 Bytes = 1.1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OKStarting kernel ...
*****LOG END*****
It's a board simular to the at91rm9200dk. I start the kernel with
bootcmd2=setenv bootargs root=/dev/mtdblock9 rootfstype=squashfs ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
______________________________________________________________________????????
run bootcmd2
First, I don't understand why those two addresses are not the same.
Then, are you sure your "bootcmd2" ist really what you think it is? Try a "printenv" and see whats really there.
Should you not have a "console=xxx" in your kernel parameters?
Besides once "Starting kernel ..." shows, u-boot is about to give control to the kernel, all future output would be from the kernel itself, probably needing a sane "console=xxx" parameter.
Best Regards, Reinhard
Dear Reinhard Meyer,
I tried it with:
setenv bootargs root=/dev/mtdblock9 rootfstype=jffs2 console=ttyS4 ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
but nothing the error is still there. The console is set in the board init of the linux kernel.
I changed only the uboot verion. The linux kernel and the rootfilesystem are the same.
Mit freundlichen Grüßen
Maik Hänig
Am 25.01.2011 12:03, schrieb Maik Hänig:
Dear Reinhard,
sorry I copied the wrong log:
U-Boot 2010.09 (Jan 24 2011 - 17:45:54)
I2C: ready DRAM: 64 MiB Flash: 32 MiB In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ## Booting kernel from Legacy Image at 30060000 ... Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1084127 Bytes = 1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
I have to kernel Images in flash. The bootcmd is copied from printenv. With the uboot version 2009.01 it works well. Is it nessesary to set a console parameter in the bootcmd in uboot version 2010.09?
Mit freundlichen Grüßen
Maik Hänig
Am 25.01.2011 11:54, schrieb Reinhard Meyer:
Dear Maik Hänig,
Hi,
I change my uboot version and after it the uboot don't starts the same linux kernel:
## Booting kernel from Legacy Image at 10060000 ...
_________________________________________????????
Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1178673 Bytes = 1.1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OKStarting kernel ...
*****LOG END*****
It's a board simular to the at91rm9200dk. I start the kernel with
bootcmd2=setenv bootargs root=/dev/mtdblock9 rootfstype=squashfs ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
______________________________________________________________________????????
run bootcmd2
First, I don't understand why those two addresses are not the same.
Then, are you sure your "bootcmd2" ist really what you think it is? Try a "printenv" and see whats really there.
Should you not have a "console=xxx" in your kernel parameters?
Besides once "Starting kernel ..." shows, u-boot is about to give control to the kernel, all future output would be from the kernel itself, probably needing a sane "console=xxx" parameter.
Best Regards, Reinhard
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Dear Maik Hänig,
Am 25.01.2011 12:18, schrieb Maik Hänig:
Dear Reinhard Meyer,
I tried it with:
setenv bootargs root=/dev/mtdblock9 rootfstype=jffs2 console=ttyS4 ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
but nothing the error is still there. The console is set in the board init of the linux kernel.
I changed only the uboot verion. The linux kernel and the rootfilesystem are the same.
I guess you have a board with specific kernel and specific u-boot. So maybe the machtype does not match?
regards
Andreas Bießmann
Andreas Bießmann,
I guess you have a board with specific kernel and specific u-boot. So maybe the machtype does not match?
Yes. Where can I found the mach type in uboot source?
Best regards / Mit freundlichen Grüßen
Maik Hänig
Dear Andreas Bießmann,
I guess you have a board with specific kernel and specific u-boot. So maybe the machtype does not match?
thanks, you was right it was a mach-type problem. I had set the wrong mach-type in my board init.
The problem with the uboot version 2010.12 hasn't changed.
Best regards / Mit freundlichen Grüßen
Maik Hänig
Dear Maik Hänig,
please do not hijack a thread!
Am 25.01.2011 12:03, schrieb Maik Hänig:
Dear Reinhard,
sorry I copied the wrong log:
U-Boot 2010.09 (Jan 24 2011 - 17:45:54)
Ok, you use 2010.09. This was last release before relocate changes. Therefore it has no connection with the relocation stuff.
I2C: ready DRAM: 64 MiB Flash: 32 MiB In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ## Booting kernel from Legacy Image at 30060000 ... Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1084127 Bytes = 1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
I have to kernel Images in flash. The bootcmd is copied from printenv. With the uboot version 2009.01 it works well.
Is it nessesary to set a console parameter in the bootcmd in uboot version 2010.09?
We don't know your configuration. What tells your working setup in kernel log messages about 'Command line'? -> /proc/cmdline
Mit freundlichen Grüßen
Maik Hänig
Am 25.01.2011 11:54, schrieb Reinhard Meyer:
Dear Maik Hänig,
Hi,
I change my uboot version and after it the uboot don't starts the same linux kernel:
## Booting kernel from Legacy Image at 10060000 ...
_________________________________________????????
Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1178673 Bytes = 1.1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OKStarting kernel ...
*****LOG END*****
It's a board simular to the at91rm9200dk. I start the kernel with
What is your board exactly? Is it currently in official u-boot or do you have another tree? at91rm9200dk is most likely broken with current u-boot (2010.12) and will be removed for 2011.03. So if you have a at91rm9200dk at hand please try to get the current u-boot working with that board and provide patches. You may see my patches for at91rm9200ek which at least make at91rm9200ek boot from SDRAM when setup correctly with an jtag (-> booting with at91bootstrab should also work but is untested).
regards
Andreas Bießmann
Dear Andreas Bießmann,
please do not hijack a thread!
sorry I didn't want do this. I wanted to give some more information.
Ok, you use 2010.09. This was last release before relocate changes. Therefore it has no connection with the relocation stuff.
yes I. I tried to make a patch for 2010.12 but the uboot don't starts so I tried in the first step the version before. It is a similar board to the at91rm9200dk. It hangs in the low level_init file. But I have only a keil jtag debugger and couldn't debug it. or is there any possibility to use it with the gdb?
I found the problem in the board.c of the arm architecture. But can't see why. Line 303 is reached but line 312 not. Also line 306 is not reached. I don't know why, maybe you can give me a hint?
I think if the problem is found the problem with the at91rm9200dk is also found.
Is it nessesary to set a console parameter in the bootcmd in uboot version 2010.09?
We don't know your configuration. What tells your working setup in kernel log messages about 'Command line'? -> /proc/cmdline
I only give the MAC and the running image in the cmdline. I think the problem must be in the uboot.
What is your board exactly? Is it currently in official u-boot or do you have another tree? at91rm9200dk is most likely broken with current u-boot (2010.12) and will be removed for 2011.03. So if you have a at91rm9200dk at hand please try to get the current u-boot working with that board and provide patches. You may see my patches for at91rm9200ek which at least make at91rm9200ek boot from SDRAM when setup correctly with an jtag (-> booting with at91bootstrab should also work but is untested).
It isn't in official u-boot tree. You can have a look in the patch.
Best regards / Mit freundlichen Grüßen
Maik Hänig
Hi,
I change my uboot version and after it the uboot don't starts the same linux kernel:
## Booting kernel from Legacy Image at 10060000 ... Image Name: Linux Kernel Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1178673 Bytes = 1.1 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
*****LOG END*****
It's a board simular to the at91rm9200dk. I start the kernel with
bootcmd2=setenv bootargs root=/dev/mtdblock9 rootfstype=squashfs ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
run bootcmd2
Can anybody give me a hint where I had to search for the error?
Mit freundlichen Grüßen
Maik Hänig
participants (5)
-
Alexander Holler -
Andreas Bießmann -
Maik Hänig -
Reinhard Meyer -
Wolfgang Denk