WP43 News

This area is for discussion about these families of custom high-end Scientific Calculator applications for SwissMicros devices.
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

Looks like the matrix division problem Pierre found is solved with 0.20.9. :D
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
User avatar
PierreMengisen
Posts: 305
Joined: Wed Nov 29, 2017 1:38 pm
Location: Neuchâtel CH

Re: 43S News

Post by PierreMengisen »

Everything is fine so far, good job!
Just a question: why use small caps on p 157 of RefMan for ADM, ... ..., #DEC ?

76 This configuration encompasses all user assignments as well as the current values of
ADM, DENMAX, ISM, REALDF, and #DEC; ...

other remark : I think you should indicate how to delete HIDE nn by ordering HIDE 00

and other typo problem : p 164 the first RANGE should not be bold
[result exceeding (−10𝑹𝑨𝑵𝑮𝑬 , 10𝑅𝐴𝑁𝐺𝐸 )]
Pierre
[TI59 with PC100C; TI-84 Plus CE-T; HP41CV with HP IL loop & 2*82161A DCD & 82162 TP; HP15C; HP28S; DM41; DM41L; DM42; DM41X]
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

Merci!
PierreMengisen wrote:
Mon Sep 27, 2021 3:56 pm
Just a question: why use small caps on p 157 of RefMan for ADM, ... ..., #DEC ?
All predefined variables and system flags are printed this way in the manuals (cf. p. 9).
PierreMengisen wrote:
Mon Sep 27, 2021 3:56 pm
other remark : I think you should indicate how to delete HIDE nn by ordering HIDE 00
Merci. Done.
PierreMengisen wrote:
Mon Sep 27, 2021 3:56 pm
and other typo problem : p 164 the first RANGE should not be bold
[result exceeding (−10𝑹𝑨𝑵𝑮𝑬 , 10𝑅𝐴𝑁𝐺𝐸 )]
Merci. Corrected.
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
User avatar
PierreMengisen
Posts: 305
Joined: Wed Nov 29, 2017 1:38 pm
Location: Neuchâtel CH

Re: 43S News

Post by PierreMengisen »

LocR seems to be activated but causes a crash.
Pierre
[TI59 with PC100C; TI-84 Plus CE-T; HP41CV with HP IL loop & 2*82161A DCD & 82162 TP; HP15C; HP28S; DM41; DM41L; DM42; DM41X]
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

PierreMengisen wrote:
Mon Sep 27, 2021 9:38 pm
LocR seems to be activated but causes a crash.
LocR makes sense in programs only. Programming is not functional yet. Please don't use LocR.

Nevertheless: merci and 22 more points for you! 8-)

EDIT: Will not happen with next release anymore. Promised.
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

90.1% of all specified commands/operations are implemented now. If project time were just proportional to the amount of commands to deal with, it would take another year to finish this project. Of course, it will go the faster the more people collaborate actively...

It's a hobbyist's project. Our team has still space for growth, so applications of C programmers are welcome. Development systems are Linux and Windows. Looking forward to your applications...
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
User avatar
Jaymos
Posts: 1635
Joined: Sun Nov 04, 2018 7:03 pm
Location: Cape Town

Re: 43S News

Post by Jaymos »

Walter wrote:
Thu Sep 30, 2021 6:31 pm
Development systems are Linux and Windows
and of course MacOS…
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
User avatar
Walter
Posts: 3070
Joined: Tue May 02, 2017 11:13 am
Location: On a mission close to DRS, Germany

Re: 43S News

Post by Walter »

Oooh, progress is a snail! At least in coding...

Thanks to Mihail, the Solver is implemented. Thanks to Jaco, a major refinement in statistical data storage is close to be finished. But our other SW guys are occupied by tasks beyond this project...
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
invariant
Posts: 13
Joined: Fri Apr 02, 2021 8:01 am

Re: 43S News

Post by invariant »

I have been spending some time understanding the wp43s codebase. I'm making good progress, but one thing that's stumping me is understanding the design rationale for storing certain things in QSPI.

I do understand the TO_QSPI macro is forcing things into the .qspi section which will then end up into the separate qspi flash file. I do understand the CRC compensation routine trying to keep a constant CRC. But I did not manage to find a rationale for using QSPI in the first place.

My hypothesis so far is that QSPI is being used because of fear of running out of internal flash. There is 704K of internal flash and current WP43S is about 672K already. It is perhaps even attempted to keep constants and things that are unlikely to change into QSPI such that in the future, routine updates are unlikely to require an update of the QSPI.

Is this correct, or am I missing something?
User avatar
Jaymos
Posts: 1635
Joined: Sun Nov 04, 2018 7:03 pm
Location: Cape Town

Re: 43S News

Post by Jaymos »

invariant wrote:
Wed Oct 27, 2021 11:39 pm
I have been spending some time understanding the wp43s codebase. I'm making good progress, but one thing that's stumping me is understanding the design rationale for storing certain things in QSPI.

I do understand the TO_QSPI macro is forcing things into the .qspi section which will then end up into the separate qspi flash file. I do understand the CRC compensation routine trying to keep a constant CRC. But I did not manage to find a rationale for using QSPI in the first place.

My hypothesis so far is that QSPI is being used because of fear of running out of internal flash. There is 704K of internal flash and current WP43S is about 672K already. It is perhaps even attempted to keep constants and things that are unlikely to change into QSPI such that in the future, routine updates are unlikely to require an update of the QSPI.

Is this correct, or am I missing something?
It is as you say, we are running out of pgm storage space.
read the thread on the closed gitlab issues page on this topic when Benjamin figured out that system, before we went over to use that. Maybe just search for qspi on the issues page.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Post Reply