You don’t have to build ‘Uboot image’ using that tool. If you generate QNX
boot image in ELF multiboot-compatible format (this is supported starting
from 6.3 I think) Uboot can load it directly by “bootelf” command.
One neat feature that you can use is that Uboot has ‘autoboot’ command
that can include a sequence of commands. It also tries to verify an image
before jumping and skips the jump if it is invalid. Together these
features allow for something like this:
autoboot=“bootelf; tftp; bootm primary write xxxxxxx; reset”
(not sure about the bootm - it might have been some other command, it’s
been few years…).
Which means ‘try to boot, if that fails try to TFTP and reflash the boot
image, then reset’.
This allows fail-safe boot using network, which is nice during development
when you can mess up your board. If you want to deploy a new image all you
have to do is to put in onto your TFTP server and invalidate the image
signature on the board (this can be done by interrupting the autoboot with
ESC and using command like “erase 2:2”). The target will pick it up and
reflash itself on next boot…
“Jan Raddatz” <> email@example.com> > wrote in message
news:e698cg$g11$> firstname.lastname@example.org> …
thanks a lot for your quick answer. It sounds similar to Pierre’s answer
and I will try to get it running at Uni now.
Thanks again and have a great day !
“Dave Green” <> email@example.com> > schrieb im Newsbeitrag
news:e695om$e6e$> firstname.lastname@example.org> …
Jan Raddatz <> email@example.com> > wrote:
actually I am trying to port QNX onto the DNP9200 Board and I ran into
We managed to create a complete QNX Image with our own Startup Programm
written as described in the QNX documentation.
Since UBoot does a lot of hardware initialization we have not written
own IPL programm and want to use UBoot.
For testing the image we want to start it via UBoot and executing the
startup by jumping to our startup code entry point.
The question is:
Is that possible and if so how do we find out the adress of the entry
of our startup code?
Booting QNX from U-Boot is possible, and quite common. There are various
of specifying the start address for U-Boot to jump to, depending on what
of image you generated.
Here are some examples - assume DRAM starts at 0xA0000000.
In your build file, if you have:
when you generate the image, you will obtain an offset where the QNX
mkifs -vvvv build image.bin
Offset Size Entry Ramoff Target=Host
a0020000 100 ---- — Startup-header
a0020100 c008 a00224e0 — /tmp/DAA065960
this is the address for U-Boot to jump to (startup_vaddr)
So, at the U-Boot prompt, you would download and run the image as
U-Boot=>tftpboot 0xA0020000 /xfer/image
The problem with this method is, if you change the startup code at all,
entry address may change, and it’s tiresome to obtain the address each
and manually enter it. A better method is to configure your build file
A ‘raw’ format image is the same as a binary, except it has a jump
right at the beginning, which jumps to startup_vaddr. So, each time you
image, you can enter:
U-Boot=>tftpboot 0xA0020000 /xfer/image.raw
Actually we are try to use the offset value that is printed when
the QNX image.
At the moment UBoot says: Starting Kernel…
And thats all…
Thanks a lot in advance!
David Green (> firstname.lastname@example.org> )
QNX Software Systems Ltd.