Re: Voyager Re-Engineering, was: Re: 15C LE - official statement?


Message #63 Posted by Walter B on 4 Aug 2011, 1:52 a.m.,
in response to message #62 by Paul Dale

Anyway each image is independent and persistent across firmware re-selects and of course power off events. The entire memory content, device state, and NUT virtual cpu context is maintained for each model version.

Oh well, it would have been nice :-(

AFAI understand, that's a set of logically completely independent applications on one HW. That's more than I've expected :-) So I don't understand the :-( above :-?

Sorry, for the late reply.

I believe what Pauli was really asking was whether the runtime context (user stack and register memory) was available between
models such that exchange of data was possible.

That of course exists by default as memory is just one flat
space with individual data context being structured identically.
The task of shuffling data between models is really
an external UI effort as it is unlikely we're going to be
patching the legacy firmware to implement such a feature.

That said, depending on the mechanism for prospective data
sharing, it would still be quite helpful to have annotated
firmware source for all of the Voyager series particularly
in the case such sharing involved tweaking individual RWM
image context unbeknownst to the corresponding firmware.

I have bits and pieces of the 15c firmware documented from
cases where I was chasing KEMU issues. A
more comprehensive and scalable approach would be to modify
a NUT assembler to accept hex binary in addition to instruction
mnemonics so we could start with the binary image,
reconstructing the source incrementally, "reassembling" and
verifying the image as needed after annotation changes.
This assumes some sort of open source like effort to address
entire firmware images (and ideally a nod or minimally some
indication from HP not to contest such an effort). Having
this available is likely useful to HP as well but perhaps not
something at the top of the to-do task list.


I believe what Pauli was really asking was whether the runtime context (user stack and register memory) was available between models such that exchange of data was possible.

This is exactly what I was wishing for. I'd be happy with just the stack and could make do with just X. For some of the Voyagers the location of X and the stack is known already.

- Pauli

Possibly Related Threads...
Thread Author Replies Views Last Post
  HP48GX - looking for Chotkeh Engineering Review Software MANUAL giancarlo 0 475 12-06-2013, 04:28 PM
Last Post: giancarlo
  [OT] engineering student chalenge cyrille de Brébisson 1 465 11-25-2013, 10:06 PM
Last Post: FORTIN Pascal
  HP 50g - displaying result in engineering format Sean Freeman 10 1,142 11-24-2013, 05:44 AM
Last Post: C.Ret
  HP-67/97 Mechanical engineering PAC cover Ignacio Sánchez 0 342 10-30-2013, 04:35 AM
Last Post: Ignacio Sánchez Reig
  Crowdfunding the Prime "engineering" firmware Eelco Rouw 24 2,179 10-28-2013, 01:23 AM
Last Post: Howard Owen
  Voyager keyboard issue John Richards 2 501 09-27-2013, 07:43 PM
Last Post: John Richards
  OT - A lucky find - Busicom Handy-LE LE-120A Cristian Arezzini 2 524 09-26-2013, 04:43 AM
Last Post: Cristian Arezzini
  Low power warning for HP-15C LE and batteries Nick_S 1 474 09-16-2013, 09:34 AM
Last Post: Hans Brueggemann
  Concern about Voyager keyboard test Matt Agajanian 2 552 08-30-2013, 07:56 PM
Last Post: Matt Agajanian
  HP 15C-LE replacement still available? Borja 16 1,642 08-22-2013, 11:16 AM
Last Post: Michael de Estrada

Forum Jump: