Psion Organiser II Re-creation

[amenjet]

Yes, that's possible, but maybe a bit redundant as the display is a full graphic display so the board could be drawn at the full 128x32 pixels.
The new OPL will hopefully have graphics commands, I'm not sure how or if compatibility with the original OPL can be done.

[PaulK]

Andrew,

That sounds brilliant!

Personally, I'm not sure full backward compatibility is needed anyway to be fair - the recreation is a new device, so why not add some additional functionality where you can!

We will all still have our original Psions for an authentic OPL experience if desired, but the spirit of the original can live on in a new machine - would be great to see what people do with graphics commands on your new machine.

This is getting exciting - thanks for your efforts!

Many thanks,
Paul

[amenjet]

If you really want to leave the original organiser and OPL behind and program in C, then the hardware is there. The github repository (https://github.com/blackjetrock/psion-org2-recreate) fits in the original case and runs on a Pico. It should be able to do wifi or bluetooth with a PicoW (that isn't in the code, but should be fairly easy to add, there is code for the WROOM module). It needs a bit of tidying, and addition of SD cards but it's close.
I think OPL will be a good way to go, and I'm hoping to write the 'OS' in OPL, so I need to recreate the translator and runtime, and OPL is a serious, fairly complex language that has a complicated runtime with proper stack frame and so on. I've started it but not fully worked on it as I have some other projects to finish.
Comments and ideas are welcome, they will guide the direction I go in, it was interesting how full backwards compatibility wasn't important to people, for instance.

[Martin]

Hi Andrew and others watching

I thought I would re-read the whole tread to see what the thoughts are.. As I see it it comes down to backward compatibility.

Psion Organiser (1)
Proof of concept, introduction of 'Pocket computer', EPROM storage, programmable, long battery life.

Psion Organiser II CM/XP
More usable, Increased memory, Inclusion of Top Slot interface, double the screen size, built in 'apps' (Calculator, Find, Save, Diary, Alarm etc), improved and 'on board' programming language. Availability of 'plug in top slot devices (Comms Link, Bar code readers, printer interface). Becomes fully costomisable. Larger Datapak, Flash Pack, Ram Pack. Large amount of commercial software available. Desktop 'comms server' and 'developer'. No Backward compatibility to Organiser (1)

Psion Organiser II LZ/LZ64
Again double the screen size, even mode 'apps', increased memory, additional programming 'features' - use these and compatibility is lost!.
Some compatibility with CM/XP - BUT when in CM/XP two line mode gives access to all previous commercial software!

Amemjet Organiser RC
Better screen, 'unlimited' memory, WIFI does away with need for Top Slot, Fully costomisable with inclusion of OPL.

OPL - The inclusion of additional features (increased UDG's, bit mapped screen, WIFI (blue tooth) control) looses backwards compatibility. I'm not sure how you would implement the OPL Comms File transfer and Remote file access functions for WIFI.

Desktop Comms server and developer?

Conclusion

Paul has got a point if a user wants 100% backward compatibility then there are still plenty of Organiser II's available. If I had any of the skills necessary to do so I would keep the foot print of the Organiser II XP as there are plenty of these that need a 'face lift'. I would strive to ensure the maximum battery life or at least include a battery level indicator. Retain (LZ) OPL with better manipulation of the screen (pixel UDG's and Sprites etc). Some form of desktop 'comms server and developer' as loosing backwards compatibility would mean all the software for it would have to come from the few of us that are still interested.

Datapak and Flash support - a one slot read facility would be great so at least it is possible to get 'stuff' off it and then write it to SDCard Gadget in the other slot!

As I said I'm buying into whatever you decide and if need be can contribute to the development costs (PM me)

Sincerely and in good faith
Martin

[amenjet]

Martin, I've created a presentation from your post above, and added the RC1 and RC2 distinction. I've not used the comms server or developer, so some info about what feature people use would be useful. I'm thinking that something along the lines of the integrated development environment of Python, I think it was called Thonny would be interesting. That was one part of Python that I was quite impressed by, apart from the bit where it didn't work.
That would be an OPL development environment, the C code has all of the RP2040/Pico development tools, and it would maybe be possible to use micro python if the problems with libraries ws fixed. I don't think I'd use Python though.

roadmap.pdf

roadmap.odp

[Martin]

Hi Andrew... looks fine

There is a check list (here) (MAKEing Packs Hints & Tips) outlining the stages in the use of Psion's Original Developer. You should be able to take something from that. The 'big deal' is making packs bootable. RC1 should be able to 'boot' these packs. RC2 may need an OPL feature to boot OPL 'name' onto the main menu.

The Comms servers available are the original CL.EXE in DosBOX. For windows then there is Org-Link by Lostgallifreyan or Boris Cornets Psi2Win.

Martin

[PaulK]

Oooh....

I see they've released the Raspberry PICO-2!

Wonder how that will impact Andrew's Recreation?!

Take care all.

Cheers
Paul

[amenjet]

I saw that. There's a Pico 2, but it has the same amount of GPIos as the pinout is compatible. It does have more memory, though, and a few new peripherals, but nothing I can see that makes it an immediate necessary upgrade. So, I think at this stage, I will continue with the Pico 1.
If the Pico 2 is completely compatible then it could be used instead, though.

[amenjet]

I realised I could create a separate line of code for the recreation, specifically code for the hardware that is created using the Pico SDK. So I have, it's here:

https://github.com/blackjetrock/psion-o ... recreate-c

It is very much a work in progress and doesn't do anything useful at the moment, but it's there.
The NewOPL could be folded in to this code if and when it arrives, but you can do anything with this version and it's a lot faster than the emulated ROMs.

[amenjet]

I realised I could create a separate line of code for the recreation, specifically code for the hardware that is created using the Pico SDK. So I have, it's here:

https://github.com/blackjetrock/psion-o ... recreate-c

It is very much a work in progress and doesn't do anything useful at the moment, but it's there.
The NewOPL could be folded in to this code if and when it arrives, but you can do anything with this version and it's a lot faster than the emulated ROMs.

Quick test of the graphics...

https://youtu.be/Fg-st5auV94