#epoc16 — Public Fediverse posts

THE JOYS OF SERIAL COMMUNICATION!

#psion3 #sibo #epoc16 #mclink #rs232

THE JOYS OF SERIAL COMMUNICATION!

#psion3 #sibo #epoc16 #mclink #rs232

THE JOYS OF SERIAL COMMUNICATION!

#psion3 #sibo #epoc16 #mclink #rs232

THE JOYS OF SERIAL COMMUNICATION!

#psion3 #sibo #epoc16 #mclink #rs232

THE JOYS OF SERIAL COMMUNICATION!

#psion3 #sibo #epoc16 #mclink #rs232

PS:

Changing "main()" to "int main()" will already cause the compiler to barf.

#psion3 #sibo #epoc16 #smallc

PS:

Changing "main()" to "int main()" will already cause the compiler to barf.

#psion3 #sibo #epoc16 #smallc

PS:

Changing "main()" to "int main()" will already cause the compiler to barf.

#psion3 #sibo #epoc16 #smallc

PS:

Changing "main()" to "int main()" will already cause the compiler to barf.

#psion3 #sibo #epoc16 #smallc

PS:

Changing "main()" to "int main()" will already cause the compiler to barf.

#psion3 #sibo #epoc16 #smallc

Here is the code in the file "HELLO.C". I'm afraid it is rather non-standard.

/* Take a look at win.c for full details about
using #link and #run etc..
*/

#link "-om:\img\hello.img hello.o stdio.o"
#run "m:\img\hello.img"

#include <stdio.h>

main()
{
printf("Hello world\n\r");
fgetc(stdin);
exit(0);
}

#smallc #psion3 #sibo #epoc16

Here is the code in the file "HELLO.C". I'm afraid it is rather non-standard.

/* Take a look at win.c for full details about
using #link and #run etc..
*/

#link "-om:\img\hello.img hello.o stdio.o"
#run "m:\img\hello.img"

#include <stdio.h>

main()
{
printf("Hello world\n\r");
fgetc(stdin);
exit(0);
}

#smallc #psion3 #sibo #epoc16

Here is the code in the file "HELLO.C". I'm afraid it is rather non-standard.

/* Take a look at win.c for full details about
using #link and #run etc..
*/

#link "-om:\img\hello.img hello.o stdio.o"
#run "m:\img\hello.img"

#include <stdio.h>

main()
{
printf("Hello world\n\r");
fgetc(stdin);
exit(0);
}

#smallc #psion3 #sibo #epoc16

Here is the code in the file "HELLO.C". I'm afraid it is rather non-standard.

/* Take a look at win.c for full details about
using #link and #run etc..
*/

#link "-om:\img\hello.img hello.o stdio.o"
#run "m:\img\hello.img"

#include <stdio.h>

main()
{
printf("Hello world\n\r");
fgetc(stdin);
exit(0);
}

#smallc #psion3 #sibo #epoc16

Here is the code in the file "HELLO.C". I'm afraid it is rather non-standard.

/* Take a look at win.c for full details about
using #link and #run etc..
*/

#link "-om:\img\hello.img hello.o stdio.o"
#run "m:\img\hello.img"

#include <stdio.h>

main()
{
printf("Hello world\n\r");
fgetc(stdin);
exit(0);
}

#smallc #psion3 #sibo #epoc16

Here are my efforts to document compiling C-Code with Small C to an IMG-File on the Psion 3c itself.
Steps:
1. Scrolling through the C-Code
2. Compiling with <Psion>+T
3. Switching to the IMG-Files launcher
4. Running the IMG-File itself and terminating with <ESC>

I apologise for the lousy quality of the the video.

#retrocomputing #epoc16 #sibo #psion3 #smallc

/cc @thelastpsion

Here are my efforts to document compiling C-Code with Small C to an IMG-File on the Psion 3c itself.
Steps:
1. Scrolling through the C-Code
2. Compiling with <Psion>+T
3. Switching to the IMG-Files launcher
4. Running the IMG-File itself and terminating with <ESC>

I apologise for the lousy quality of the the video.

#retrocomputing #epoc16 #sibo #psion3 #smallc

/cc @thelastpsion

Here are my efforts to document compiling C-Code with Small C to an IMG-File on the Psion 3c itself.
Steps:
1. Scrolling through the C-Code
2. Compiling with <Psion>+T
3. Switching to the IMG-Files launcher
4. Running the IMG-File itself and terminating with <ESC>

I apologise for the lousy quality of the the video.

#retrocomputing #epoc16 #sibo #psion3 #smallc

/cc @thelastpsion

Here are my efforts to document compiling C-Code with Small C to an IMG-File on the Psion 3c itself.
Steps:
1. Scrolling through the C-Code
2. Compiling with <Psion>+T
3. Switching to the IMG-Files launcher
4. Running the IMG-File itself and terminating with <ESC>

I apologise for the lousy quality of the the video.

#retrocomputing #epoc16 #sibo #psion3 #smallc

/cc @thelastpsion

Here are my efforts to document compiling C-Code with Small C to an IMG-File on the Psion 3c itself.
Steps:
1. Scrolling through the C-Code
2. Compiling with <Psion>+T
3. Switching to the IMG-Files launcher
4. Running the IMG-File itself and terminating with <ESC>

I apologise for the lousy quality of the the video.

#retrocomputing #epoc16 #sibo #psion3 #smallc

/cc @thelastpsion

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Time for another poll:

#psion #psion3 #psion5 #epoc16 #epoc32

Time for another poll:

#psion #psion3 #psion5 #epoc16 #epoc32

Time for another poll:

#psion #psion3 #psion5 #epoc16 #epoc32

Time for another poll:

#psion #psion3 #psion5 #epoc16 #epoc32

Time for another poll:

#psion #psion3 #psion5 #epoc16 #epoc32

Some #Psion news! #plptools, the open source suite of programs for transferring files to and from #EPOC16 and #EPOC32 devices, has some additional maintainers: @captfab, @jbmorley ... and me!

We're looking into how we can take the project into the future. We do have some ideas, but we're taking a considered approach to future development.

plptools currently runs on Linux and macOS (and possibly FreeBSD, NetBSD, Solaris, AIX and HP-UX, although these haven't been tested in a while). I've started work on porting it to #HaikuOS.

The repo has been moved to a new GitHub organisation, which you can find here. https://github.com/plptools/plptools

#retrocomputing

Some #Psion news! #plptools, the open source suite of programs for transferring files to and from #EPOC16 and #EPOC32 devices, has some additional maintainers: @captfab, @jbmorley ... and me!

We're looking into how we can take the project into the future. We do have some ideas, but we're taking a considered approach to future development.

plptools currently runs on Linux and macOS (and possibly FreeBSD, NetBSD, Solaris, AIX and HP-UX, although these haven't been tested in a while). I've started work on porting it to #HaikuOS.

The repo has been moved to a new GitHub organisation, which you can find here. https://github.com/plptools/plptools

#retrocomputing

Some #Psion news! #plptools, the open source suite of programs for transferring files to and from #EPOC16 and #EPOC32 devices, has some additional maintainers: @captfab, @jbmorley ... and me!

We're looking into how we can take the project into the future. We do have some ideas, but we're taking a considered approach to future development.

plptools currently runs on Linux and macOS (and possibly FreeBSD, NetBSD, Solaris, AIX and HP-UX, although these haven't been tested in a while). I've started work on porting it to #HaikuOS.

The repo has been moved to a new GitHub organisation, which you can find here. https://github.com/plptools/plptools

#retrocomputing

Some #Psion news! #plptools, the open source suite of programs for transferring files to and from #EPOC16 and #EPOC32 devices, has some additional maintainers: @captfab, @jbmorley ... and me!

We're looking into how we can take the project into the future. We do have some ideas, but we're taking a considered approach to future development.

plptools currently runs on Linux and macOS (and possibly FreeBSD, NetBSD, Solaris, AIX and HP-UX, although these haven't been tested in a while). I've started work on porting it to #HaikuOS.

The repo has been moved to a new GitHub organisation, which you can find here. https://github.com/plptools/plptools

#retrocomputing

Some #Psion news! #plptools, the open source suite of programs for transferring files to and from #EPOC16 and #EPOC32 devices, has some additional maintainers: @captfab, @jbmorley ... and me!

We're looking into how we can take the project into the future. We do have some ideas, but we're taking a considered approach to future development.

plptools currently runs on Linux and macOS (and possibly FreeBSD, NetBSD, Solaris, AIX and HP-UX, although these haven't been tested in a while). I've started work on porting it to #HaikuOS.

The repo has been moved to a new GitHub organisation, which you can find here. https://github.com/plptools/plptools

#retrocomputing

HIVEMIND: Does anyone have a copy of the TopSpeed Pascal 3.10 compiler?

I've discovered something. I can't unsee it. So now I have to follow it through.

The [TopSpeed] Pascal compiler could also be used to develop software for the Psion series 3 in a roundabout way if used with the PSION s3 SDK, as the environment allowed you to develop Pascal code with C code, headers and libraries you could get functional s3 apps by linking the Pascal code with the required C headers/libs and then compiling everything with the PSION SDK, in rare cases needing a little bit of glue C code.

Source: http://www.edm2.com/index.php/TopSpeed_Pascal

Does anyone have a copy of TopSpeed Pascal? I need to try writing Pascal software for #EPOC16. The documentation would be really handy, too.

#retrocomputing #compilers #retrodev #compiler #askfedi #psion #pascal

HIVEMIND: Does anyone have a copy of the TopSpeed Pascal 3.10 compiler?

I've discovered something. I can't unsee it. So now I have to follow it through.

The [TopSpeed] Pascal compiler could also be used to develop software for the Psion series 3 in a roundabout way if used with the PSION s3 SDK, as the environment allowed you to develop Pascal code with C code, headers and libraries you could get functional s3 apps by linking the Pascal code with the required C headers/libs and then compiling everything with the PSION SDK, in rare cases needing a little bit of glue C code.

Source: http://www.edm2.com/index.php/TopSpeed_Pascal

Does anyone have a copy of TopSpeed Pascal? I need to try writing Pascal software for #EPOC16. The documentation would be really handy, too.

#retrocomputing #compilers #retrodev #compiler #askfedi #psion #pascal

HIVEMIND: Does anyone have a copy of the TopSpeed Pascal 3.10 compiler?

I've discovered something. I can't unsee it. So now I have to follow it through.

The [TopSpeed] Pascal compiler could also be used to develop software for the Psion series 3 in a roundabout way if used with the PSION s3 SDK, as the environment allowed you to develop Pascal code with C code, headers and libraries you could get functional s3 apps by linking the Pascal code with the required C headers/libs and then compiling everything with the PSION SDK, in rare cases needing a little bit of glue C code.

Source: http://www.edm2.com/index.php/TopSpeed_Pascal

Does anyone have a copy of TopSpeed Pascal? I need to try writing Pascal software for #EPOC16. The documentation would be really handy, too.

#retrocomputing #compilers #retrodev #compiler #askfedi #psion #pascal

HIVEMIND: Does anyone have a copy of the TopSpeed Pascal 3.10 compiler?

I've discovered something. I can't unsee it. So now I have to follow it through.

The [TopSpeed] Pascal compiler could also be used to develop software for the Psion series 3 in a roundabout way if used with the PSION s3 SDK, as the environment allowed you to develop Pascal code with C code, headers and libraries you could get functional s3 apps by linking the Pascal code with the required C headers/libs and then compiling everything with the PSION SDK, in rare cases needing a little bit of glue C code.

Source: http://www.edm2.com/index.php/TopSpeed_Pascal

Does anyone have a copy of TopSpeed Pascal? I need to try writing Pascal software for #EPOC16. The documentation would be really handy, too.

#retrocomputing #compilers #retrodev #compiler #askfedi #psion #pascal

HIVEMIND: Does anyone have a copy of the TopSpeed Pascal 3.10 compiler?

I've discovered something. I can't unsee it. So now I have to follow it through.

The [TopSpeed] Pascal compiler could also be used to develop software for the Psion series 3 in a roundabout way if used with the PSION s3 SDK, as the environment allowed you to develop Pascal code with C code, headers and libraries you could get functional s3 apps by linking the Pascal code with the required C headers/libs and then compiling everything with the PSION SDK, in rare cases needing a little bit of glue C code.

Source: http://www.edm2.com/index.php/TopSpeed_Pascal

Does anyone have a copy of TopSpeed Pascal? I need to try writing Pascal software for #EPOC16. The documentation would be really handy, too.

#retrocomputing #compilers #retrodev #compiler #askfedi #psion #pascal

If anyone fancies following in my footsteps with #EPOC16 hackery, I've released my updates to #EDisAsm as 0.0.6. First update in a couple of years!

https://github.com/thelastpsion/edisasm/releases/tag/0.0.6

#Psion #retrocomputing

If anyone fancies following in my footsteps with #EPOC16 hackery, I've released my updates to #EDisAsm as 0.0.6. First update in a couple of years!

https://github.com/thelastpsion/edisasm/releases/tag/0.0.6

#Psion #retrocomputing

If anyone fancies following in my footsteps with #EPOC16 hackery, I've released my updates to #EDisAsm as 0.0.6. First update in a couple of years!

https://github.com/thelastpsion/edisasm/releases/tag/0.0.6

#Psion #retrocomputing

If anyone fancies following in my footsteps with #EPOC16 hackery, I've released my updates to #EDisAsm as 0.0.6. First update in a couple of years!

https://github.com/thelastpsion/edisasm/releases/tag/0.0.6

#Psion #retrocomputing

If anyone fancies following in my footsteps with #EPOC16 hackery, I've released my updates to #EDisAsm as 0.0.6. First update in a couple of years!

https://github.com/thelastpsion/edisasm/releases/tag/0.0.6

#Psion #retrocomputing

I originally thought that it was just a hardware thing - solder on another chip, job done. After all, the pads were on the board, so why wouldn't #Psion have made #EPOC16 work with 4MB RAM?

But maybe a 4MB 3mx just wasn't a priority for Psion any more. #EPOC32 and the Series 5 were in full swing by the time the 3mx was released. The two Psions were drifting apart, too - Psion's hardware business ended up refocusing on Windows CE machines.

Psion had the ramdrive working with 2MB machines since the 3a2. The code probably hadn't been touched in ages, and it might have been too much hassle to update for the returns they thought they might get.

This is all speculation, of course. But it would make sense.

#retrocomputing

I originally thought that it was just a hardware thing - solder on another chip, job done. After all, the pads were on the board, so why wouldn't #Psion have made #EPOC16 work with 4MB RAM?

But maybe a 4MB 3mx just wasn't a priority for Psion any more. #EPOC32 and the Series 5 were in full swing by the time the 3mx was released. The two Psions were drifting apart, too - Psion's hardware business ended up refocusing on Windows CE machines.

Psion had the ramdrive working with 2MB machines since the 3a2. The code probably hadn't been touched in ages, and it might have been too much hassle to update for the returns they thought they might get.

This is all speculation, of course. But it would make sense.

#retrocomputing

I originally thought that it was just a hardware thing - solder on another chip, job done. After all, the pads were on the board, so why wouldn't #Psion have made #EPOC16 work with 4MB RAM?

But maybe a 4MB 3mx just wasn't a priority for Psion any more. #EPOC32 and the Series 5 were in full swing by the time the 3mx was released. The two Psions were drifting apart, too - Psion's hardware business ended up refocusing on Windows CE machines.

Psion had the ramdrive working with 2MB machines since the 3a2. The code probably hadn't been touched in ages, and it might have been too much hassle to update for the returns they thought they might get.

This is all speculation, of course. But it would make sense.

#retrocomputing

I originally thought that it was just a hardware thing - solder on another chip, job done. After all, the pads were on the board, so why wouldn't #Psion have made #EPOC16 work with 4MB RAM?

But maybe a 4MB 3mx just wasn't a priority for Psion any more. #EPOC32 and the Series 5 were in full swing by the time the 3mx was released. The two Psions were drifting apart, too - Psion's hardware business ended up refocusing on Windows CE machines.

Psion had the ramdrive working with 2MB machines since the 3a2. The code probably hadn't been touched in ages, and it might have been too much hassle to update for the returns they thought they might get.

This is all speculation, of course. But it would make sense.

#retrocomputing

I originally thought that it was just a hardware thing - solder on another chip, job done. After all, the pads were on the board, so why wouldn't #Psion have made #EPOC16 work with 4MB RAM?

But maybe a 4MB 3mx just wasn't a priority for Psion any more. #EPOC32 and the Series 5 were in full swing by the time the 3mx was released. The two Psions were drifting apart, too - Psion's hardware business ended up refocusing on Windows CE machines.

Psion had the ramdrive working with 2MB machines since the 3a2. The code probably hadn't been touched in ages, and it might have been too much hassle to update for the returns they thought they might get.

This is all speculation, of course. But it would make sense.

#retrocomputing