I am porting a signal processing API to Palm OS. This software runs on a number of embedded systems including some with the same ARM processors powering PalmOne's devices. For speed, it is necessary to compile directly for ARM. The API does not contain any UI code. I have started off using Palm OS Developer Suite.
PalmSource touts Cobalt as the OS of choice for software developers, but there do not appear to be any actual devices available to run Cobalt. Is this true or am I missing something? It appears that Cobalt would let me almost directly compile my code, but without any devices available, I will have to go the Garnet / PNO route. Garnet / PNO programming appears to be almost equivalent to programming a dual processor system (always difficult) with the unfortunate choice of processors with different endianness (even more difficult). I would like to put all of my code in the PNO with a thin layer to give a 68K interface to it, but it is unclear where the line is drawn between Protein development for Cobalt and using the Protein tools to build a PNO. My questions are: - Can I link the PNO to the Cobalt posix libraries? - Can I access/store local files from the PNO? - Is this 64K size limit issue a problem for code or heap or both? Other issues I have run across: - Limited stack size. - Byte swapping. - Integer alignment and structure packing. Are there other issues I should be aware of? Would I be better off switching to the Code Warrior tools? Thank you very much for your help. -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
