[U-Boot-Users] How do I boot VxWorks (6.3) image with u-boot1.1.3 :: mkimage entry point and address ?

[Chaffin, Michael]

> To: u-boot-users at lists.sourceforge.net
> Subject: Re: [U-Boot-Users] How do I boot VxWorks (6.3) image 
> with u-boot1.1.3 :: mkimage entry point and address ?
> 
> Chaffin, Michael wrote:
> 
> > I have a working system, PowerPC embedded in Xilinx Virtex II Pro, 
> > that does boot into Linux using u-boot 1.1.3; but I need to load a 
> > VxWorks
> > (6.3) image and boot from that. I have read thedocumentation, but I 
> > don't know what my entry point for mkimage to use, sysInit( )? What 
> > should my load address be?
> 
> You have to pass as address the entry point of the vxworks kernel.
> On my PPC405 board I had no problem with the following steps 
> I have in my config.h a
>     RAM_LOW_ADRS       = 00010000 ;

I quick check and I have the same value for 'RAM_LOW_ADRS'; a quick
search of the executable vxworks with objdump turns up 
  $ objdump -x ./vxWorks | grep -A 2 -B 2 _sysInit
  0006242c g     F .text  0000022c soaccept
  0008b4f0 g     F .text  00000078 tyDevTerminate
  00010000 g       .text  00000000 _sysInit
  00025050 g     F .text  00000014 islower
  00091ac8 g     F .text  00000020 dllCount

So sysInit( ) is at 0x00010000

> I did no call mkImage for my vxWorks (5.5.1), but copied it 
> directly into the ram at an address which does not conflict 
> with my RAM_LOW_ADRS e.g. loadb 0x00200000 then I call bootm 
> 0x00010000 ;

Ok ... Here we go with executing the program with /no/ mkimage..

=> loadb 0x00200000
## Ready for binary (kermit) download to 0x00200000 at 115200 bps...
## Total Size      = 0x000e09b6 = 919990 Bytes
## Start Addr      = 0x00200000
=>
=>
=>
=>
=> bootm 0x00200000
## Booting image at 00200000 ...
   Image Name:   vxWorks3.msc
   Image Type:   PowerPC VxWorks Kernel Image (uncompressed)
   Data Size:    919926 Bytes = 898.4 kB
   Load Address: 00000000
   Entry Point:  00100000
   Verifying Checksum ... OK
OK
<Same Result>

> On the Yosemite PPC440EP evaluation board, my vxWorks (6.3) 
> hangs too. I had not yet a chance to figure out why, but I 
> think there might be some differences into how the HW is 
> mapped into the memory space. 
> 
> Best regards

Thanks for the help, I think I will try Stefan Roese's suggestion of
'bootvx'; maybe it will help you with your Yosemite board?
 
> Niklaus Giger