▼
Posts: 16
Threads: 4
Joined: Apr 2009
Thanks to those who made possible the project wp34s. I would have contributed myself with something if my knowledge on computing would have been a little above zero :-) but it's not the case. However I have had for years a couple of ideas in my head related to the display and I'd like to mention them now, so you can give your opinion about it.
As everyone knows, the last series made by Hewlett Packard when till independent, the Pioneer, did not include a RPN model with segment lcd screen. That is to say, the RPN models in that serie used matrix screens. In other words, the RPN version of the HP20S was never produced. I noticed it when I was a kid and I bought my first Pioneer.
And this wasnt natural. In fact all the previous spice models had segment(obviously) led displays. So it would have been a logical step to make a simple RPN calculator with segment display, for example the lcd version of the HP34C.
I have problems to work with matrix displays. I love segment displays, which are clear and sharp, and I like simple calculators. I think it would be a good idea, based on the wp34s, to make a RPN model with Segment display by avoiding the use of the matrix section on the screen of the hp30b.
It would cover a niche and the project would be almost straight forward! By this I mean that the layouts are already there: the HP20s and HP34C keyboards. And the manual doesnt need to be written; it was written decades ago: the HP34C manual.
What's your opinion?
jose poyan
▼
Posts: 1,248
Threads: 33
Joined: Aug 2007
But of course the Voyagers were segment and RPN. But I like Pioneers better myself as well.
▼
Posts: 16
Threads: 4
Joined: Apr 2009
I know. I was refering to the models with vertical format only.
▼
Posts: 3,283
Threads: 104
Joined: Jul 2005
You might want to repurpose the new 10bii+. It comes with a plain segmented LCD, has the Pioneer keyboard layout, so what would you want more?
Personally, I stick to wp34s. When the firmware is stable, I'll almost certainly will sacrifice a 30b for the purpose.
▼
Posts: 1,248
Threads: 33
Joined: Aug 2007
I thought I read Tim saying it could not be repurposed. But I can't find the post.
▼
Posts: 3,283
Threads: 104
Joined: Jul 2005
Of course it can. The programming connector is the same. There is no JTAG connector for debugging and HP has yet to release technical information but this is not a principal problem.
▼
Posts: 1,278
Threads: 44
Joined: Jul 2007
I don't think there will be any release of anything. The only difference between them (20/30b, 10bII+, 12c) is the screen. Just a LCD table is all you need different.
Personally, I am quite excited there is the ability to build using GCC. We always wanted to get around to that but just didn't have the time.
TW
▼
Posts: 3,283
Threads: 104
Joined: Jul 2005
ATMEL provides the necessary startup files for GCC. I've recently switched to CodeSourcery G++ Lite, the free command line only compiler from them. I have yet to test if this realy works. The code is more compact then with the Yagarto or netX tool chains.
The LCD mapping for the new 12C and 10bii+ units (together with the necessary timing infos, i. e. what to write to the SLCDC controller registers) would be fine.
EDIT: The keyboard arrangement is sufficiently different from the 20b/30b to warrant same explanation, too.
Edited: 29 Apr 2011, 2:03 p.m.
▼
Posts: 2,309
Threads: 116
Joined: Jun 2005
When I've needed to determine a keyboard mapping, I've just used a simple C program to scan the GPIO pins one at a time, drive that pin alternately high and low, and read the other pins to see if any correspond. When a match is found, send the ID of the output and input GPIO pins out the serial port. Then I just press each key in turn and see what comes out.
Similarly for the display, I just sequentially toggle each bit in the LCD bitmap, with a delay (or a wait for a keypress or serial receive), and manually record what segments correspond.
▼
Posts: 3,283
Threads: 104
Joined: Jul 2005
That's a workable idea. The choices are limited as only the WAKEUP pins can be used the way HP designed the software.
For the display, you need to know some details about its physics to be able to configure the number of segments and commons and the corresponding frequencies correctly. Without a JTAG connector, you cannot peek into the settings of the original firmware.
▼
Posts: 2,309
Threads: 116
Joined: Jun 2005
It's not that hard to work out LCD settings by trial and error. There aren't really all that many parameters to adjust, and you don't have to get them all correct to see that you're making progress.
You can use SAM-BA commands over the serial port to write the registers, if you don't want to write a program to do it. See page 175 of the datasheet for the SAM-BA commands. (Prior pages describe how to get into SAM-BA boot mode.)
▼
Posts: 107
Threads: 16
Joined: Jul 2007
Quote:
It's not that hard to work out LCD settings by trial and error. There aren't really all that many parameters to adjust, and you don't have to get them all correct to see that you're making progress.
Exactly. Besides, there's not much variation in hardware between the units.
|