• Why the onboard flash disk is not visible on VxWorks?

    From IoClaudio@21:1/5 to All on Thu Feb 15 14:58:12 2018
    I have a board that has a flash sata disk (in which now is installed a Fedora distribution).
    Now I have to install VxWorks in this Flash disk.

    I can load, using the Ethernet, both the Boot Rom and a custom VxWorks Kernel. The problem is that after loading the Boot Rom, it seems that a drive "ata0" exists:
    [VxWorks Boot]:
    Instantiating /ata0:1 as rawFs, device = 0x20001
    Instantiating /ata0:2 as rawFs, device = 0x30001
    Instantiating /ata0:3 as rawFs, device = 0x40001

    But, after loading the VxWorks kernel, the command "devs" does not show the "/ata0" disk.

    How is it possible?

    Thank you

    cld

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Vikash Jain@21:1/5 to IoClaudio on Sat Feb 17 04:58:27 2018
    On Friday, 16 February 2018 04:28:15 UTC+5:30, IoClaudio wrote:
    I have a board that has a flash sata disk (in which now is installed a Fedora distribution).
    Now I have to install VxWorks in this Flash disk.

    I can load, using the Ethernet, both the Boot Rom and a custom VxWorks Kernel.
    The problem is that after loading the Boot Rom, it seems that a drive "ata0" exists:
    [VxWorks Boot]:
    Instantiating /ata0:1 as rawFs, device = 0x20001
    Instantiating /ata0:2 as rawFs, device = 0x30001
    Instantiating /ata0:3 as rawFs, device = 0x40001

    But, after loading the VxWorks kernel, the command "devs" does not show the "/ata0" disk.

    How is it possible?

    Thank you

    cld

    If I understand correctly, bootloader you are able to see disk (ata0), but when you load complete OS image (vxworks), disk is not visible. Which OS version you are using. You should again check for vxWorks kernel setting (on 6.x VSB/VIP components), as
    both bootloader and OS setting might differ.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From IoClaudio@21:1/5 to All on Sat Feb 17 08:53:42 2018
    If I understand correctly, bootloader you are able to see disk (ata0), but when you load complete OS image (vxworks), disk is not visible. Which OS version you are using. You should again check for vxWorks kernel setting (on 6.x VSB/VIP components), as
    both bootloader and OS setting might differ.

    Thank you Vikash Jain for your answer.

    Yes, I can see the flash disk from the Bios and from the bootloader (using the devs command).
    [VxWorks Boot]: devs
    drv name
    0 /null
    1 /tyCo/0
    1 /tyCo/1
    5 hostname:
    3 /ata0:1
    3 /ata0:2
    3 /ata0:3

    While in the kernel the output is:
    -> devs
    drv name
    0 /null
    1 /tyCo/0
    1 /tyCo/1
    1 /tyCo/2
    1 /tyCo/3
    1 /tyCo/4
    8 hostname:
    9 /vio
    10 /tgtsvr
    value = 25 = 0x19

    The boot from that device works well. Now there is a Fedora distribution installed on it. I have to replace it with a VxWorks kernel.
    I'm using VxWorks 6.9.
    Yes I've compared the settings of the bootloader and of the kernel and added to the kernel the ones that could have solved the problem but nothing changes.
    I'll check better these differences.

    cld

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Vikash Jain@21:1/5 to IoClaudio on Wed Feb 21 01:00:53 2018
    On Friday, 16 February 2018 04:28:15 UTC+5:30, IoClaudio wrote:
    I have a board that has a flash sata disk (in which now is installed a Fedora distribution).
    Now I have to install VxWorks in this Flash disk.

    I can load, using the Ethernet, both the Boot Rom and a custom VxWorks Kernel.
    The problem is that after loading the Boot Rom, it seems that a drive "ata0" exists:
    [VxWorks Boot]:
    Instantiating /ata0:1 as rawFs, device = 0x20001
    Instantiating /ata0:2 as rawFs, device = 0x30001
    Instantiating /ata0:3 as rawFs, device = 0x40001

    But, after loading the VxWorks kernel, the command "devs" does not show the "/ata0" disk.

    How is it possible?

    Thank you

    cld

    See if you have below defined in your VIP settings:
    INCLUDE_ATA
    INCLUDE_DATACOLLECTOR_SHOW
    INCLUDE_ATA_SHOW

    Which BSP you are using, can you send details.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)