Date of this edition: May, 2009
Target OS: QNX® Neutrino® 6.3.2
Host OS: Microsoft Windows XP SP3, 2000 SP4, or NT SP6a; Sun Solaris 7, 8, or 9; QNX® Neutrino® 6.3.0; Linux Red Hat 8, 9, or Enterprise WS 3 or 4
Boards supported: MPL MIP405-3 Rev C SN: 1160 with U-Boot 1.1.4
Note: |
|
Throughout this document, you may see QNX reference numbers (Ref#...) associated with particular issues, changes, etc. When corresponding with QNX Technical Support staff about a given issue, please quote the relevant reference number. You might also find the reference numbers useful for tracking issues as they become fixed. |
This BSP contains:
Note: | Each BSP may contain board-specific information and instructions on building an OS image for that particular board. For details, see the chapter "Working with a BSP" in the Building Embedded Systems manual (in the Documentation Roadmap page under the QNX Neutrino RTOS section). |
Depending on the particular BSP and type of driver, you'll find the files in these locations:
File | Location |
---|---|
"sbin" drivers (serial, flash, block) | $QNX_TARGET\cpu\sbin |
"dll" drivers (network, usb) | $QNX_TARGET\cpu\lib\dll |
File | Location |
---|---|
"sbin" drivers (serial, flash, block) | $QNX_TARGET/cpu/sbin |
"dll" drivers (network, usb) | $QNX_TARGET/cpu/lib/dll |
Workaround: If you need to specify a MAC address to io-pkt-v4, we recommend that you use the same MAC address that the ROM monitor uses. This will ensure that if the host caches the ROM monitor's MAC address, you'll still be able to communicate with the target. Otherwise you might need to delete the target's arp entry on your host (arp -d).
To obtain technical support for the BSP, please contact:
Triadem Solutions AG