Thanks Again, which u-boot version are you referring, because I am using 2013.04 version and in this there is no directory named board/BuR/KWB. can you please send the Boot Arguments which you used to boot the vxworks and which method are you using to boot vxworks?
On Mon, Sep 8, 2014 at 10:16 PM, Hannes Petermaier <han...@petermaier.org> wrote: > Hi Ashish, > > okay - i am using vxworks 6.9.3.3, and there is is a issue around the > interrupt vectors. In later versions 6.9.4 upwards windriver takes care > about this and sets up the interruptvectors. > U-Boot does sets them to some address within u-boot code, but vxWorks > expects that the interrupt vector are at the place where they are after > poweron-reset. > > In my case (using AM3352 from TI) i've set the interrupt vectors back to > original state (have a look to my KWB-Board, board/BuR/kwb/board.c). > > BTW: i am using a stripped image which i directly start with "go > <address>", but that shouldn't matter. > > best regards, > Hannes > > > > On 2014-09-09 03:56, Ashish Khetan wrote: > >> Hi Hannes >> Thanks for your reply. I am using VxWorks 6.7 and the image is not >> stripped. The loadaddress is also same within kernel configuration. I am >> using bootvx command to boot VxWorks. Do I need to update boot >> parameters? >> On Sep 8, 2014 4:11 PM, "Hannes Petermaier" < >> hannes.peterma...@br-automation.com> wrote: >> >> Hi Ashish, >>> >>> i had a problem booting vxworks in the past around interrupt vectors. >>> Which version of vxworks you are using ? do you use a stripped image ? >>> is the loadaddress the same within kernel configuration ? >>> >>> best regards, >>> hannes >>> >>> From: Ashish Khetan <curieux.khe...@gmail.com> >>>> To: u-boot@lists.denx.de >>>> Date: 04.09.2014 14:13 >>>> Subject: [U-Boot] VxWorks Booting using U-boot as Bootloader >>>> Sent by: u-boot-boun...@lists.denx.de >>>> >>>> Hi, >>>> I was trying to boot vxworks using u-boot bootloader for learning >>>> >>> purpose >>> >>>> on MPC8640DHPCN board. Previously I successfully ported QNX os along >>>> >>> with >>> >>>> linux on same board using u-boot. while booting using bootvx command its >>>> not booting and stucking after showing the following message: >>>> >>>> tftp 01000000 vxWorks >>>> Speed: 1000, full duplex >>>> Using eTSEC1 device >>>> TFTP from server 192.168.10.2; our IP address is 192.168.10.4 >>>> Filename 'vxWorks'. >>>> Load address: 0x1000000 >>>> Loading: >>>> >>> * ################################################################# >>> >>>> ################################################################# >>>> ################################# >>>> 12.3 MiB/s >>>> done >>>> Bytes transferred = 2392432 (248170 hex) >>>> BOSSv2.0=> bootvx 0010 1000000 >>>> ## Ethernet MAC address not copied to NV RAM >>>> ## Using bootline (@ 0x4200): root=/dev/nfs rw >>>> nfsroot=192.168.10.2:/opt/eldk-5.3/powerpc/rootfs-basic >>>> ip=192.168.10.4:192.168.10.2:192.168.10.1:255.255.255.0:Boss:eth0:off >>>> panic=1 console=ttyS0,115200 >>>> ## Starting vxWorks at 0x00100000 ... >>>> >>>> >>>> please somebody provide me some link or any pointer to help me get more >>>> understanding about booting multiple os using uboot. >>>> _______________________________________________ >>>> U-Boot mailing list >>>> U-Boot@lists.denx.de >>>> http://lists.denx.de/mailman/listinfo/u-boot >>>> >>> >>> >> >
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
