luxferre/t-deckard
1
0
Fork 0
Code Actions Activity

added tdeckboot

Browse Source
This commit is contained in:
Luxferre
2025-12-22 16:06:01 +02:00
parent c5fe8d741f
commit 122bc06e7f
3 changed files with 28 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -1
View File
@@ -18,7 +18,7 @@ On other generic platforms, most modules which are not T-Deck-specific are set t
## Installation on T-Deck (Plus)
Current installation process doesn't involve any `.mpy` module compilation, so, after installing the prerequisites, you just need to copy the `deck` and `app` directories into the root of the `CIRCUITPY` removable volume.
Current installation process doesn't involve any `.mpy` module compilation, so, after installing the prerequisites, you just need to copy the `deck` and `app` directories (and optionally the `tdeckboot.py` file, see the FAQ) into the root of the `CIRCUITPY` removable volume.
## Components (`deck.*`)
@@ -214,6 +214,8 @@ No, but it provides comparable functionality to the on-device Python REPL. You c
It may at some point, but the entire idea is to give you the foundation to easily create your own custom shells for any special purposes. The project carries the spirit of early personal computing days when the programming language REPL (BASIC, Forth, Lisp etc) **was** your primary operating environment. In this case, the on-device Python REPL is such an environment.
To get a hang of how the shell **might** look like, you can run `from tdeckboot import *`. This will expose all the common methods from the main core modules. See the [tdeckboot.py](./tdeckboot.py) file for details.
### Which platforms is T-DeckARD being tested on?
CircuitPython 10.x on a T-Deck Plus and MicroPython for modern x86_64 Linux. That's it.