VxWorks Software Development Kit (SDK)

Hi Dan
I want to use the wr-cc of "VxWorks SDK for NXP i.MX 8M Quad Evaluation Kit (EVK) " to build ilp32 for AARCH32 and lp64 for AARCH64 separately. Do you know how to configure the project?
Thanks

I believe the i.MX8 SDK is 64-bit only, so I guess what you’re trying to do won’t be possible with this SDK alone.

Dan

I am aware of the issue. Please hold on while IT handles it. Thanks!

got it. thank you Dan.

Hello, do the SDKs have any support for OpenGL?

The VxWorks SDKs published on Wind River Labs do not include graphics support.

Hi Dan,

I’m trying to boot VxWorks on a Raspberry Pi 3A+ using the old 1.6 SDK for Raspberry Pi 3 and I’m not sure what is going on. This is what I see on the serial (115200, 8n1, connected to GPIO14/15):

U-Boot 2024.04-00757-gbeac958153-dirty (Apr 29 2024 - 19:19:47 +0300)

DRAM:  448 MiB
RPI 3 Model A+ (0x9020e1)
Core:  68 devices, 14 uclasses, devicetree: embed
MMC:   mmc@7e202000: 0, mmc@7e300000: 1
Loading Environment from FAT... OK
In:    serial,usbkbd
Out:   serial,vidconsole
Err:   serial,vidconsole
Net:   No ethernet found.

starting USB...
Bus usb@7e980000: USB DWC2
scanning bus usb@7e980000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
9157968 bytes read in 391 ms (22.3 MiB/s)
## Booting kernel from Legacy Image at 08000000 ...
   Image Name:   vxworks
   Image Type:   AArch64 VxWorks Kernel Image (uncompressed)
   Data Size:    9157904 Bytes = 8.7 MiB
   Load Address: 00100000
   Entry Point:  00100000
   Verifying Checksum ... OK
Working FDT set to 0
   Loading Kernel Image to 100000
   !!! WARNING !!! Using legacy DTB
## Starting vxWorks at 0x00100000, device tree at 0x00000000 ...
KԚa@iҗ@SOI
          r9VPV@)JZhKܚVXZҗByHkJqN[XtրXQNYNANY
hPPZ{HCRYp                                   Xa@
XXZ@ZXZBBB@yHYZ[IIR=)o
\XX0@X@(QHVVYj@@BPXX@BNSXPB@ZXZB
                        PVBPP؋Zu        PPPLXZZ
                                               9XXX@@Ba
X@2@@@BB@X@@@@@BPR                                     ڧ8Q=XڣiKQ@@@B0XX@B@B@@oDJ)

Also tried with a different device tree from u-boot:

U-Boot> fatload mmc 0 0x08000000 vx/uvxworks
9157968 bytes read in 391 ms (22.3 MiB/s)
U-Boot> fatload mmc 0 0x09000000 bcm2837-rpi-3-a-plus.dtb
19856 bytes read in 9 ms (2.1 MiB/s)
U-Boot> bootm 0x08000000 - 0x09000000
## Booting kernel from Legacy Image at 08000000 ...
   Image Name:   vxworks
   Image Type:   AArch64 VxWorks Kernel Image (uncompressed)
   Data Size:    9157904 Bytes = 8.7 MiB
   Load Address: 00100000
   Entry Point:  00100000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 09000000
   Booting using the fdt blob at 0x9000000
Working FDT set to 9000000
   Loading Kernel Image to 100000
   !!! WARNING !!! Using legacy DTB
   Using Device Tree in place at 0000000009000000, end 0000000009007d8f
Working FDT set to 9000000
## Starting vxWorks at 0x00100000, device tree at 0x09000000 ...
KԚa@kҗBSOr9VP^H)BRKܚVXZҗByHQkJqNYXtրXQN[NCN[
jPPXqBARYr                                  Za@
)R`KܚVa@kҗB{JSZs@CRYZ:
TXX2@Z@*QHVVQh@BBZ%\JqPLXXZBZZBB
                      PPPЫثX]B@B@PPPB@@2ZZBBB

I know it’s an old board and SDK, but it is what I have available right now. Anything I can do to get it working?

The VxWorks Raspberry Pi 3 BSP only worked on Raspberry Pi 3B (without networking support) and 3B+. I don’t think 3A was ever considered.

Thank you for answering! I saw the notes about the tested boards,but the only major difference between a 3A+ and a 3B+ is the RAM size from what I can tell. It has the same CPU and peripherals…so shouldn’t it work or maybe crash hard (in case it tries to access more than 512MB)? The console output seems to me like it is booting, but not displaying properly for an unknown reason. It also reacts to key presses, but just displays more junk. I’ve made some tests with a modified device tree, but no luck.

I’ll look into switching to another board. Out of curiosity is there any possibility of a BSP for the Raspberry 5 in the future?

Thank you!

There may be some differences in the device tree between Pi3A and Pi3B, but since the device tree is embedded in the VxWorks kernels included in the SDKs, there isn’t an easy way to check that.

The garbled text can indicate an incorrect baud rate, so I’d start by changing the baud rate to check if that makes a difference.

I don’t have a timeline for a Raspberry Pi 5 VxWorks BSP.

Dan

Hi Dan,

For commercial use, where to download the Vxwrok7 SDK?

Please contact your Wind River sales representative for VxWorks licensing information or commercial use of the VxWorks SDKs.

Dan

@dan.milea is there a SDK based on VxWorks 6.6 for Raspberry? I suppose the answer is no… In that case, is there any way to build it? Thanks in advance.

Hi @amigueti ! Unfortunately the answer to your questions is no. Raspberry Pi board support and the VxWorks SDKs are both VxWorks 7 features.

Hi Dan, I am trying to run VxWorks SDK for IA - QEMU (x86-64) - Windows for a simple demo show case but the read me in that file just has this- Refer to the Visual Studio Code Getting Started guide for setup instructions and links to product-specific tutorials to help get you up and running. Which is a dead link, so where should I go to setup this version of Vxworks?

Hi @S_Nath_unh ! Unfortunately that documentation is no longer public. However, the Windows version of the SDK is not that different from the Linux one, so the equivalent Linux README file would be a good starting point.

Please note that the Windows SDK is fairly old, so you may want to evaluate the Linux ones, either on Windows within the Windows Subsystem for Linux (WSL) or on a dedicated Linux machine.

Regards,
Dan