| forum.getinpulse.com http://www.getinpulse.com/hack/forum/ |
|
| SDK version 1.1.1 posted http://www.getinpulse.com/hack/forum/viewtopic.php?f=6&t=177 |
Page 1 of 1 |
| Author: | Ryan [ Tue Mar 29, 2011 9:02 pm ] |
| Post subject: | SDK version 1.1.1 posted |
Pulse SDK Version 1.1.1 (Mar 29, 2011) - fixed bug with alarm putting watch to sleep - fixed compileandload for -n - added makefile for local compiling (see http://www.getinPulse.com/guide/local for instructions) |
|
| Author: | hudson [ Tue Apr 05, 2011 7:05 pm ] |
| Post subject: | Re: SDK version 1.1.1 posted |
Ryan wrote: - added makefile for local compiling (see linux getting started guide for instructions) Hurrah! I was able to use the summon-arm-toolchain to build arm-none-eabi-gcc (after unsuccessfully fighting with the raw sources from the FSF). I haven't been able to successfully load anything that uses resources other than the stock firmware (with -n), although non-resource using programs (like my cavern.c) load just fine after a local build. Any chance of getting the sources to the libraries? The two things I would specifically like to do are take advantage of the code in spiflash.o in libkernel.a to allow storage of non-image resources in the flash (I can probably figure out how to use spiflash_read() works through the calls in get_resource_metadata(), but that takes time away from writing more useful programs), and to remove the Bluetooth stack (since I always seem to need to drop back to the fail-safe loader, and the library seems like it would save around 14 KB when I remove bt.o from libkernel.a and relink my executable). Is the first 4 KB reserved for some sort of permanent resident boot loader? It looks like several of the routines make indirect calls through a jump table at 0x20, which doesn't seem to be present in the compiled binary. |
|
| Author: | Eric [ Wed Apr 06, 2011 6:12 pm ] |
| Post subject: | Re: SDK version 1.1.1 posted |
Correct, the first 4kB hold our bootloader, but since the LPC only allows chunks of 4kB to be overwritten, we decided to include a few other functions to fill up that space. Good call on eliminating the BT stack. It's easy to fall back to the fail-safe firmware. That would free up a ton of space for cool games and watchface apps... |
|
| Author: | dang [ Thu Apr 07, 2011 11:50 am ] |
| Post subject: | Re: SDK version 1.1.1 posted |
I noticed that the new notification app includes a charging icon when the watch is charging, that changes when it's full. That icon is not present in the version of the notification app included with the SDK. How do I get that information (the charging status of the watch)? Could the source version of the notification app be updated to the latest source? I've been basing my app on that, and it'd be nice to include charging status. |
|
| Author: | Eric [ Fri Apr 08, 2011 12:25 am ] |
| Post subject: | Re: SDK version 1.1.1 posted |
@dang, we haven't exposed charging status in the SDK because...it just doesn't work that well yet. Sorry about that! We'll fix it (ie make it actually work, right now it ONLY displays when charge is full/not-full) and then get it out to you guys. |
|
| Author: | mtuzzolo [ Thu Apr 14, 2011 7:02 am ] |
| Post subject: | Re: SDK version 1.1.1 posted |
Hey Hudson, Thanks for the tip on using the summon-arm-toolchain. Did you have any issues with openocd? Seems that the new package doesn't have a configure script (odd): x openocd-master/.git/hooks/pre-commit.sample x openocd-master/.git/hooks/pre-rebase.sample x openocd-master/.git/hooks/prepare-commit-msg.sample x openocd-master/.git/hooks/update.sample ****************************************************************** * Configuring openocd-master ****************************************************************** ./summon-arm-toolchain: line 426: ../openocd-master/configure: No such file or directory I'm going to try and pull the openocd code from http://openocd.sourceforge.net/ and see if I can get it to work using that. -Matt |
|
| Page 1 of 1 | All times are UTC - 8 hours |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|