All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot - vxWorks booting problems
Date: Wed, 26 Feb 2003 13:19:39 +0100	[thread overview]
Message-ID: <3E5CB0DB.C65CAE82@staubli.com> (raw)
In-Reply-To: BAY2-F179al8UUGrh7i00042931@hotmail.com

Den Denov wrote:

> Hi all!
>
> I begin use U-Boot at my custom board  based on TQM823L module.
> It works fine.
> But I have problem with vxWorks image to boot it.
>
> Briefly. I compile vxWorks ram-based ELF image, make .bdx file from it and
> download BDX throught BDM using visionClick\visionICE.
> When I says "GO 100000" it works fine!
> After it I make binary image (using ElfToBin utility), make image from it
> using MKIMAGE utility from U_Boot, upload it to my target using u-boot
> serial interface, copy to flash - all ok.
>
> When I says "bootm 40040000". Image start to load ok, but after message
> "Starting vxWorks at 0x100000" target crashed.
>
> I try to make
> cp.b 40040040 (where actually image w\o header placed) 100000 $filesize
> its copied OK
> But "go 100000" cause crash again.
>
> I try set brakepoint at address 0x100000 and make step-by-step tracing. And
> wondering - code at 100000 after copy from flash looks different then I
> simple download BDX file through BDM before!
>
> I think something wrong with vxWorks binary image after ElfToBin.
>
> Please give me advices and suggestions about possible resolving my problem!
>
> Den.
>

Hi Den,
have you tried to make an image directly from the elf file (using mkimage).
I use u-boot to boot a QNX OS which is also contained in an elf image, and I
use mkimage on the elf file, then I use bootm on this image and it works fine.

Hoping this helps.

Best regards

      reply	other threads:[~2003-02-26 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 11:42 [U-Boot-Users] U-boot - vxWorks booting problems Den Denov
2003-02-26 12:19 ` Pierre AUBERT [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E5CB0DB.C65CAE82@staubli.com \
    --to=p.aubert@staubli.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.