I am attempting a proof-of-concept to use Pelion Device Management with devices running the QNX operating system.
I started with https://cloud.mbed.com/docs/current/porting/pal-process.html , It references “pal-platform folder in the root of the mbed-cloud-client repository”, but there is no such folder in https://github.com/ARMmbed/mbed-cloud-client. I did find the folder in https://github.com/ARMmbed/mbed-cloud-client-example, so I started by cloning this repo.
Question 1) is this just a typo in the docs?
I then created new files and directories for toolchain, device and OS directories. The pal-platform.py deploy and generate commands appear to work. fullbuild fails with missing “pal.h” file
pal.h is not found in the mbed-client-client-example repo, but it can be found in the mbed-cloud-client repo under the mbed-client-pal directory. This dir tree also contains source for PAL abstraction layers. Using Linux as baseline I stubbed out QNX support under Source/Port/Reference-Imp/OS_Specific/QNX
Question 2) How do I connect my work under mbed-cloud-client/mbed-client-pal (QNX PAL impl) to the work in mbed-cloud-client-example? It seems obvious to me that to build the client I need to pull in PAL impl for QNX, but I cannot find documentation that describes how to do this.
Question 3) How do I build test code for individual RTOS, Networking, etc pieces of PAL for QNX?
Thanks for any assistance you can provide