Skip navigation.
Home
The QNX Community Portal

View topic - boot with u-boot - bad magic number

boot with u-boot - bad magic number

Read-only archive of qnx.bsp (Discuss building an image, flashing a board or using a BSP) at inn.qnx.com

boot with u-boot - bad magic number

Postby Radoslaw Dyczek » Tue Feb 14, 2006 2:46 pm

Hi All,

I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which fails
with: "Bad Magic Number". iminfo prints out the same.

I can successfuly boot the image with PIBS but I have to use U-Boot.

Here just a part of my build file:

[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}

Thanks for answers
Radoslaw Dyczek
Radoslaw Dyczek
 

Re: boot with u-boot - bad magic number

Postby Dave Green » Tue Feb 14, 2006 2:46 pm

Does the version of u-boot that you are using support openbios? You might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage

u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,

I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which fails
with: "Bad Magic Number". iminfo prints out the same.

I can successfuly boot the image with PIBS but I have to use U-Boot.

Here just a part of my build file:

[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}

Thanks for answers
Radoslaw Dyczek

--

David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com
Dave Green
 

Re: boot with u-boot - bad magic number

Postby Radoslaw Dyczek » Tue Feb 14, 2006 4:08 pm

Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage

u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,

I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which fails
with: "Bad Magic Number". iminfo prints out the same.

I can successfuly boot the image with PIBS but I have to use U-Boot.

Here just a part of my build file:

[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}

Thanks for answers
Radoslaw Dyczek
Radoslaw Dyczek
 

Re: boot with u-boot - bad magic number

Postby Dave Green » Tue Feb 14, 2006 4:14 pm

Have you tried raw? A raw image is simply a binary image, with a jump instruction at
the beginning, which will jump to startup_vaddr, which is the actual QNX entry point.

The other alternative is to download a binary image, but if you do that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv when you build the
image, and this address will change, each time you make changes to the startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in the build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each time; you can
just download the image to the correct address (whatever is specified by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage

u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,

I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which fails
with: "Bad Magic Number". iminfo prints out the same.

I can successfuly boot the image with PIBS but I have to use U-Boot.

Here just a part of my build file:

[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}

Thanks for answers
Radoslaw Dyczek


--

David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com
Dave Green
 

Re: boot with u-boot - bad magic number

Postby Radoslaw Dyczek » Tue Feb 14, 2006 4:40 pm

Hi Dave!

Thanks for answer.

I tried both: binary and raw.

If I use 'go 300000 (or Entry Point - case binary)' after tftpboot
300000 the system freezes!
if I use bootm or iminfo I get "Bad Magic Number"!

It sound like the image format is not recognized by u-boot.

Cheers
Radoslaw

Dave Green schrieb:
Have you tried raw? A raw image is simply a binary image, with a jump instruction at
the beginning, which will jump to startup_vaddr, which is the actual QNX entry point.

The other alternative is to download a binary image, but if you do that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv when you build the
image, and this address will change, each time you make changes to the startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in the build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each time; you can
just download the image to the correct address (whatever is specified by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage


u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,
I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which fails
with: "Bad Magic Number". iminfo prints out the same.
I can successfuly boot the image with PIBS but I have to use U-Boot.
Here just a part of my build file:
[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}
Thanks for answers
Radoslaw Dyczek
Radoslaw Dyczek
 

Re: boot with u-boot - bad magic number

Postby Radoslaw Dyczek » Tue Feb 14, 2006 4:43 pm

Hi Dave!

Thanks for answer.

I tried both: binary and raw.

If I use 'go 300000 (or Entry Point - case binary)' after tftpboot
300000 the system freezes!
if I use bootm or iminfo I get "Bad Magic Number"!

It sound like the image format is not recognized by u-boot.

Cheers
Radoslaw

Dave Green schrieb:
Have you tried raw? A raw image is simply a binary image, with a jump instruction at
the beginning, which will jump to startup_vaddr, which is the actual QNX entry point.

The other alternative is to download a binary image, but if you do that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv when you build the
image, and this address will change, each time you make changes to the startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in the build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each time; you can
just download the image to the correct address (whatever is specified by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage

u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,
I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which fails
with: "Bad Magic Number". iminfo prints out the same.
I can successfuly boot the image with PIBS but I have to use U-Boot.
Here just a part of my build file:
[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}
Thanks for answers
Radoslaw Dyczek
Radoslaw Dyczek
 

Re: boot with u-boot - bad magic number

Postby Wensheng Zheng » Tue Feb 14, 2006 5:06 pm

I have a EP440C board with U-Boot on it and boot up with raw without a
problem.



Radoslaw Dyczek wrote:
Hi Dave!

Thanks for answer.

I tried both: binary and raw.

If I use 'go 300000 (or Entry Point - case binary)' after tftpboot
300000 the system freezes!
if I use bootm or iminfo I get "Bad Magic Number"!

It sound like the image format is not recognized by u-boot.

Cheers
Radoslaw

Dave Green schrieb:
Have you tried raw? A raw image is simply a binary image, with a jump
instruction at
the beginning, which will jump to startup_vaddr, which is the actual
QNX entry point.
The other alternative is to download a binary image, but if you do
that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv when
you build the
image, and this address will change, each time you make changes to the
startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in the
build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is
startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each time;
you can
just download the image to the correct address (whatever is specified
by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You
might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and
then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage


u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,
I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which
fails with: "Bad Magic Number". iminfo prints out the same.
I can successfuly boot the image with PIBS but I have to use U-Boot.
Here just a part of my build file:
[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}
Thanks for answers
Radoslaw Dyczek
Wensheng Zheng
 

Re: boot with u-boot - bad magic number

Postby Wensheng Zheng » Tue Feb 14, 2006 5:34 pm

Which board are you using?
Many reason can cause the board freeze, basically different board needs
different startup.

Radoslaw Dyczek wrote:
Hi Dave!

Thanks for answer.

I tried both: binary and raw.

If I use 'go 300000 (or Entry Point - case binary)' after tftpboot
300000 the system freezes!
if I use bootm or iminfo I get "Bad Magic Number"!

It sound like the image format is not recognized by u-boot.

Cheers
Radoslaw

Dave Green schrieb:
Have you tried raw? A raw image is simply a binary image, with a jump
instruction at
the beginning, which will jump to startup_vaddr, which is the actual
QNX entry point.
The other alternative is to download a binary image, but if you do
that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv when
you build the
image, and this address will change, each time you make changes to the
startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in the
build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is
startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each time;
you can
just download the image to the correct address (whatever is specified
by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You
might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and
then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage


u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,
I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which
fails with: "Bad Magic Number". iminfo prints out the same.
I can successfuly boot the image with PIBS but I have to use U-Boot.
Here just a part of my build file:
[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}
Thanks for answers
Radoslaw Dyczek
Wensheng Zheng
 

Re: boot with u-boot - bad magic number

Postby Pierre AUBERT » Wed Feb 15, 2006 10:05 am

Hi Radoslaw,

Radoslaw Dyczek wrote:

Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

I must use mkimage. This tool adds a header and a CRC to your image. I
use an elf image + mkimage and
I use u-boot with success to start QNX.

Good luck ...

Thanks for every hint!
Radoslaw

Dave Green schrieb:

Does the version of u-boot that you are using support openbios? You
might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and
then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage

u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:

Hi All,


I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which
fails with: "Bad Magic Number". iminfo prints out the same.


I can successfuly boot the image with PIBS but I have to use U-Boot.


Here just a part of my build file:


[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}


Thanks for answers
Radoslaw Dyczek

Pierre AUBERT
 

Re: boot with u-boot - bad magic number

Postby Radoslaw Dyczek » Thu Feb 16, 2006 8:14 am

I'm using the 440ep bamboo board
and QNX also adapted the startup code for our board.
QNX is also running perfectly (using the PIBS loader).

Yesterday I was on the Embedded World in Nurnberg and I talked to U-Boot
people. They said that in most cases you need to use the mkimage to add
additiobnal header. The bootm command also make some "cleanup" before it
jumps into the startup entry point. So jumping directly with "go" is
not enough.. (they say)
I will try it out and report my research

Thanks for help

Wensheng Zheng schrieb:
Which board are you using?
Many reason can cause the board freeze, basically different board needs
different startup.

Radoslaw Dyczek wrote:
Hi Dave!

Thanks for answer.

I tried both: binary and raw.

If I use 'go 300000 (or Entry Point - case binary)' after tftpboot
300000 the system freezes!
if I use bootm or iminfo I get "Bad Magic Number"!

It sound like the image format is not recognized by u-boot.

Cheers
Radoslaw

Dave Green schrieb:
Have you tried raw? A raw image is simply a binary image, with a jump
instruction at
the beginning, which will jump to startup_vaddr, which is the actual
QNX entry point.
The other alternative is to download a binary image, but if you do
that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv when
you build the
image, and this address will change, each time you make changes to
the startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in the
build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is
startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each
time; you can
just download the image to the correct address (whatever is specified
by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You
might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and
then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage


u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,
I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which
fails with: "Bad Magic Number". iminfo prints out the same.
I can successfuly boot the image with PIBS but I have to use U-Boot.
Here just a part of my build file:
[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}
Thanks for answers
Radoslaw Dyczek
Radoslaw Dyczek
 

Re: boot with u-boot - bad magic number

Postby Wensheng Zheng » Thu Feb 16, 2006 1:52 pm

Make sure U-Boot clears all the TLB, otherwise you will get TLB parity
error, which is a machine check exception, and cause the system hangs.
I saw this happens on another 440 board with U-Boot, and we have to
clear the TLB in the startup.





Radoslaw Dyczek wrote:
I'm using the 440ep bamboo board
and QNX also adapted the startup code for our board.
QNX is also running perfectly (using the PIBS loader).

Yesterday I was on the Embedded World in Nurnberg and I talked to U-Boot
people. They said that in most cases you need to use the mkimage to add
additiobnal header. The bootm command also make some "cleanup" before it
jumps into the startup entry point. So jumping directly with "go" is
not enough.. (they say)
I will try it out and report my research

Thanks for help

Wensheng Zheng schrieb:
Which board are you using?
Many reason can cause the board freeze, basically different board
needs different startup.

Radoslaw Dyczek wrote:
Hi Dave!

Thanks for answer.

I tried both: binary and raw.

If I use 'go 300000 (or Entry Point - case binary)' after tftpboot
300000 the system freezes!
if I use bootm or iminfo I get "Bad Magic Number"!

It sound like the image format is not recognized by u-boot.

Cheers
Radoslaw

Dave Green schrieb:
Have you tried raw? A raw image is simply a binary image, with a
jump instruction at
the beginning, which will jump to startup_vaddr, which is the actual
QNX entry point.
The other alternative is to download a binary image, but if you do
that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv
when you build the
image, and this address will change, each time you make changes to
the startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in
the build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is
startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each
time; you can
just download the image to the correct address (whatever is
specified by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs
something like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios?
You might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and
then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage


u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,
I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which
fails with: "Bad Magic Number". iminfo prints out the same.
I can successfuly boot the image with PIBS but I have to use U-Boot.
Here just a part of my build file:
[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}
Thanks for answers
Radoslaw Dyczek
Wensheng Zheng
 

Re: boot with u-boot - bad magic number

Postby Michael Tasche » Fri Feb 24, 2006 11:33 pm

Radoslaw Dyczek schrieb:
Hi Dave!

Thanks for answer.

I tried both: binary and raw.

If I use 'go 300000 (or Entry Point - case binary)' after tftpboot
300000 the system freezes!
If your image is elf, use bootelf 300000.
if I use bootm or iminfo I get "Bad Magic Number"!
If you want to use bootm, you have to convert your elf image with the

u-boot tool mkimage. If your image is greater than 4MB, do not use
bootm, because last time I looked at the u-boot sources, I saw a hard
coded 4MB limitation in the bootm code.

-Michael

It sound like the image format is not recognized by u-boot.

Cheers
Radoslaw

Dave Green schrieb:
Have you tried raw? A raw image is simply a binary image, with a jump
instruction at
the beginning, which will jump to startup_vaddr, which is the actual
QNX entry point.
The other alternative is to download a binary image, but if you do
that, you'll need
to extract startup_vaddr, by observing the output of mkifs -vvvv when
you build the
image, and this address will change, each time you make changes to the
startup code.

So, if your build file has [virtual=ppcbe,binary]

when you build the image:

mkifs -vvvv build image.bin (in this example, [image=0x30000] in the
build file)

"/usr/qnx630/target/qnx6/ppcbe/boot/sys/procnto-400"
30100 100 ---- --- Startup-header
30200 d108 321f4 --- /tmp/DAA210543 <<< the 321f4 is
startup_vaddr
3d208 5c ---- --- Image-header
3d264 6d0 ---- --- Image-directory


so, you'd do the following:

tftpboot 0x30000 image.bin

go 0x321f4

On the other hand, if you do the following:

[virtual=ppcbe,raw]

then you don't need to worry about extracting startup_vaddr each time;
you can
just download the image to the correct address (whatever is specified
by [image=...]
in the build file), and then 'go' to that address.




Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi Dave,

I've tried it with ELF without success :(
Maybe I should use mkimage from u-boot? Maybe u-boot needs something
like own header in front of ELF?

Thanks for every hint!
Radoslaw

Dave Green schrieb:
Does the version of u-boot that you are using support openbios? You
might
try changing the OS image format to 'raw'[virtual=ppcbe/raw], and
then download
and run the image as follows:


u-boot> tftpboot 0x300000 myimage

u-boot> go 0x300000


Radoslaw Dyczek <dyczr@bizerba.com> wrote:
Hi All,
I try to boot my ifs image with u-boot.
After I transferred the image to ram over tftp I try bootm which
fails with: "Bad Magic Number". iminfo prints out the same.
I can successfuly boot the image with PIBS but I have to use U-Boot.
Here just a part of my build file:
[image=0x300000]
[virtual=ppcbe/openbios] .bootstrap = {
startup-440rb -v
...
}
Thanks for answers
Radoslaw Dyczek
Michael Tasche
 


Return to qnx.bsp

Who is online

Users browsing this forum: No registered users and 1 guest