Datapack tool for Psion Organisers
** This is a work in progress **
This is a fork of blackjetrock's datapak tool at: https://github.com/blackjetrock/psion-org-datapack-tool
It's an attempt to tidy and develop the code.
Currently builds oled_test.c which allows a test of the oled and menu operation. SD card functionality will come next.
Blackjetrock's previous code status:
The code builds and can read datapack data. It can also write datapack data. issues: the OLED and buttons work and there are read and write and info options that work on the OLED. A lot of funtionality is over USB serial.
- There are errors on the fab1 PCB. these are listed in the errata. hand mods are needed to get the PCB to work.
- Flash packs can't be written.
- Read pak to file doesn't seem to give a valid opk file, not sure why
- Detection of all the diffferent pack addressing schemes and sizes isn't there, really.
- Could do with a detection routine.
- The code is untidy...
- The OLED and serial functions aren't very coherent.
Libraries required:
official raspberry pi picosdk at https://github.com/raspberrypi/pico-sdk
blackjetrock's SD card library at https://github.com/blackjetrock/ajm-no-OS-FatFS-SD-SPI-RPi-Pico
with the pico hardware setup (GPIOs) in file: ajm-no-OS-FatFS-SD-SPI-RPi-Pico/FatFs_SPI/sd_driver/hw_config.c
This library is a fork of: https://github.com/carlk3/no-OS-FatFS-SD-SPI-RPi-Pico and is explained further there.
The firmware directory has the files required for building the code but CMakeLists.txt is configured for a particular file system structure. This will have to be altered to match the location where your SDK and FAT FS SD card libraries are located.
First fix errors in CMakeLists.txt (should only be directories, the location of the pico SDK and FAT FS library)
You can set the environment variable PICO_SDK_PATH using export, but it is also set in CMakeLists.txt
export PICO_SDK_PATH="[where the Pico SDK is]"
create a 'build' directory in the 'firmware' directory:
mkdir build
cd build
cmake ..
Then, still in build directory:
make
Then program with either a picoprobe or as a UF2 file.
There is a script in the firmware directory
flash_code.sh
that will use openocd and a picprobe toprogram the code onto a Pico. Run this script from the build directory
../flash_code.sh
Openocd needs to be set up as detailed in the Pico documentation. Some directories may need to be altered to match your structure.
There is also a script
../set_debug_openocd.sh
(also run from the build directory) that will set up gdb for a session. Run this from the build directory as well. It is set up to use the TUI (Text User Interface) with the -tui command line option, but that can be removed for a standard gdb CLI experience.
There is an interface on the OLED display that uses the buttons.
Left button: Up Middle Button: Down Right Button: Action/Execute
There is a menu system to access all the functions.
There is also an interface that runs over the USB serial connectin from the Pico on the PCB to a host PC. I use minicom on Linux but any terminal emulator should work, e.g. the one in the Arduino SDK.
The SD card holds .opk images in a directory called 'PAK' that is located in the root directory of the SD card. The SD card is checked at power on and a message appears on the OLED display indicating whether the check was OK or not.