|Hands on the 20b SDK|
Message #1 Posted by Marcus von Cube, Germany on 9 Feb 2011, 10:06 a.m.
I'm willing to help bring forward the 20b/30b repurposing efforts and am taking the first few steps in this direction.
Firstly, my cable has arrived and works fine. (I have a spare, which I can offer to someone here in Germany for free.) After downloading SAM-BA from atmel.com, I was able to erase the flash of my 20b and reprogram it with the image provided in the SDK. The little machine is up and running its original software again. So technically, I'm able to put any software on it.
The following step was getting the sample application in the simulator to compile and run. My old MSC compiler does not support the long long data type (it's there but differently named). Some changes to the sources helped me out. One function is missing from the MFC libraries coming with my compiler. I've got the software running but without support for multiple skins.
To overcome these problems, I decided to upgrade to Visual Studio C++ Express which you can download from Microsoft for free. You'll need some spare space on your hard disk though. The install has just finished. I'll report back, if the SDK example application will compile with this version.
The next step would be to compile WP-34s for the simulator. If I can get this to work, a big step is taken towards a "real" port. On SourceFourge.net I can only find the documentation for download. What do I need to get to the sources? I guess an SVN client is necessary.
I had asked IAR for a price quote for the full development environment from them. In short, I'm not willing to pay over 2000 € for a hobbyist project. I'll be getting the kickstart edition to play around with the SDK but I plan to make GCC an alternative. OK, no debugging in the foreseeable future...
EDIT: The IAR compiler was able to create a working flash image of the number guessing game. I did some code changes to get rid of any compiler warnings and I had to change the project settings: The kickstart version does not allow assembly listings being generated from C/C++ code and the library options were set to "none" which lead to linker errors (missing symbols.)
Edited: 9 Feb 2011, 12:45 p.m. after one or more responses were posted