porting a BSP from VxWorks 5.5 to 6.2. - VxWorks

This is a discussion on porting a BSP from VxWorks 5.5 to 6.2. - VxWorks ; I'm evaluating to port my BSP from VxWorks 5.5 (with Tormado 2.2.1) to VxWorks6.2 (with WorkBench 2.4) Looking at Windriver web site seems that it's easy to move a BSP for 5.5 to 6.2. The only task to do it's ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: porting a BSP from VxWorks 5.5 to 6.2.

  1. porting a BSP from VxWorks 5.5 to 6.2.

    I'm evaluating to port my BSP from VxWorks 5.5 (with Tormado 2.2.1) to
    VxWorks6.2 (with WorkBench 2.4)

    Looking at Windriver web site seems that it's easy to move a BSP for
    5.5 to 6.2.

    The only task to do it's to recompile all.

    it's true ?..

    Please note that I want to move from 5.5 to 6.2 without change the HW!!

  2. Re: porting a BSP from VxWorks 5.5 to 6.2.

    no u must change some code in config.h

  3. Re: porting a BSP from VxWorks 5.5 to 6.2.

    ok! so it's a minimal change.

    Thanks

  4. Re: porting a BSP from VxWorks 5.5 to 6.2.

    Hi,

    Wind River have a migration guide which is available from their support
    pages. It seems that the main points are to:

    1. Add memory protection using the MMU if the BSP does not already do
    so. This is required for the RTPs.

    2. Update the BSP to use the architecture independant cache library
    APIs.

    3. Create a memory space for persistent memory after USER_RESERVED_MEM

    Compared to writing a BSP is should be straightforward!

    Hope this helps

    Ed

    Ed Liversidge
    Harmonic Software Systems Ltd

+ Reply to Thread
« Doesn't vxWorks support bool type? | Missing `fcntl' »