Re: Richard Nelson's pictures of the 4 HP 15c versions Message #12 Posted by uhmgawa on 22 Feb 2012, 11:32 a.m., in response to message #10 by Alexander Oestert
Quote:
Could the experts elaborate on the question if it would be possible to port the DM-15CC's firmware to the HP 15C LE hardware as it seems to be bug free? Or the code that go15c for Android is based on which also has no apparent bugs.
Several folks have asked for a KEMU port to the sam7 voyager.
KEMU sidesteps all of the known problems with the current sam7
15c le firmware and additionally supports full NUT/voyager
emulation including system/keypad self test, synthetic
programming via y^x rotate-22, command line interface, multiple
voyager family models, even the NUT ptr==13 CPU errata.
It is fairly configurable and currently is optimized for size:
bundled with a 15c firmware image it is
well under 32K on an AVR core SoC and I'd expect substantially
less for an ARM footprint. Even with all voyager images of
(11c/12c/15c/16c), graphic support, and assorted bells & whistles
as demonstrated in the
Graphic Voyager Prototype,
image size is under 64KB.
Requiring support for only the sam7 voyager's segment display,
image size reduces
further and usage would be essentially the same the
KINOMI/KEMU voyager. The point here being over half of the sam7's
128KB flash would be available for further optimization,
functional customization, or user persistent storage.
The hold up thus far has been over logistics rather than
technical issues, concerning how a prospective user deals
with obtaining voyager firmware. The images I've been using
have been captured from voyagers I own rather than elsewhere.
Ideally I'll be able to reach some understanding with HP to allow
bundling these images with a KEMU release but we're not there
yet. The alternative of finding images elsewhere is certainly
possible and that may be a fall-back if bundling isn't an
option. But it is unwelcome end user clunkiness best avoided.
|