Skip to content

Releases

Tetsu OS v0.2-test.2 (TEST: LPDDR4 and the newer screen)

Choose a tag to compare

@github-actions github-actions released this 18 Nov 23:05
b3d0463

TEST build, for RG35XX SP units with LPDDR4 memory or the newer screen. For everyday use, take
v0.1 instead.

Tetsu OS is developed on one RG35XX SP, which has LPDDR3 memory, and v0.1 only starts on
LPDDR3. This build tries LPDDR4 first and then LPDDR3, so one image should start on both.
The SP was also made with two different screens, and this build detects which one it has.

It works on our unit, which has LPDDR3 and the original screen, but no LPDDR4 unit and no
unit with the newer screen has run it yet
. If you have an RG35XX SP, please try it and tell
us what happened, whether it worked or not. Other models aren't supported yet.

Testing your device has the
steps. It takes about fifteen minutes.

In short

  1. Find your memory type from the stock card:
    Check your memory type.
    It helps, but you can test without it.

  2. Write tetsu-rg35xxsp-v0.2-test.2-sdcard.img.gz to a spare microSD card (at least
    6 GB), for example with balenaEtcher. This erases the card.

  3. Put it in TF1, unplug the cable and power on:

    What you see What it means
    The logo, then the setup It works. Check Settings > SYSTEM > SYSTEM INFO: the MEMORY row shows the memory type
    No picture, and the green light blinks about once a second Neither memory type could be set up
    The green light stays on, but the screen stays dark or garbled The memory works, but the screen setup probably doesn't. bootlog.txt on the card's TETSU-BOOT drive shows which screen was detected, so please attach it
  4. Open a hardware test report.
    X on SYSTEM INFO saves the logs to the card's TETSU-BOOT drive. Attach them, and
    bootlog.txt from the same drive.

It's safe to try. Tetsu OS runs from the card and doesn't touch the device's internal
storage: take the card out, and the stock firmware starts as before.

What's new since v0.1

  • The bootloader detects LPDDR4 or LPDDR3 and sets the memory voltage to match: 1.1 V
    for LPDDR4 and 1.2 V for LPDDR3. LPDDR4 is tried first, so it never gets LPDDR3's
    voltage.
  • The SP's two screens are told apart at each start, by reading the screen's ID. The result
    is in bootlog.txt, as a line starting with panel:.
  • SYSTEM INFO, the logs and bootlog.txt show the memory type and voltage.
  • On LPDDR3 units, it starts about 0.1 to 0.2 s later, from the failed LPDDR4 try.

This build changes the bootloader, which SYSTEM UPDATE doesn't install, so it is only
on a newly written card.

Files

File For
tetsu-rg35xxsp-v0.2-test.2-sdcard.img.gz The card image
SHA256SUMS-rg35xxsp Checking the download: sha256sum -c --ignore-missing SHA256SUMS-rg35xxsp
manifest.txt, manifest.sig, tetsu-rg35xxsp-<build>.img.gz SYSTEM UPDATE (not needed for testing)
tetsu-rg35xxsp-v0.2-test.2-sources.tar.part*, -licences.csv The sources of the GPL and other components, and their licences

Tetsu OS's own code is MIT. The emulator cores keep their own licences: Snes9x, Genesis
Plus GX and PicoDrive may not be used commercially.

Tetsu OS v0.1 (beta)

Choose a tag to compare

@github-actions github-actions released this 18 Nov 18:31
8c8cbaf

Beta. Tetsu OS has been tested on one Anbernic RG35XX SP. The image is built for
units with LPDDR3 memory: check yours
first, as an LPDDR4 unit won't start it (a slowly blinking green light). Units with
another screen panel may show nothing. If yours doesn't start, please open an issue. A
muOS or stock card still starts the device as before.

Install

  1. Download tetsu-rg35xxsp-<version>-sdcard.img.gz.
  2. Write it to a microSD card with balenaEtcher, Raspberry Pi Imager or dd. This erases
    the card.
  3. Put the card in the slot marked TF1 and power on. The first start makes the
    TETSU-DATA partition from the rest of the card and runs the setup.
  4. Add games over USB (Settings > DATA > USB STORAGE) or Wi-Fi (WI-FI TRANSFER).

Devices on this version update themselves later through Settings > SYSTEM > SYSTEM
UPDATE. A new bootloader would need a new card image, and the notes would say so.

Still experimental

  • HDMI output: not yet tried on a real TV or monitor
  • Bluetooth: checked with one controller (Backbone Pro) and one pair of headphones
    (Bose QC35 II)
  • The German translation: not yet reviewed on the device
  • RetroAchievements hardcore mode: refused until the client is registered with
    RetroAchievements
  • USB accessories on the USB-C port don't work (host mode is off)
  • Some SanDisk Ultra cards sometimes stop on a cold start, waiting for the card. Taking
    the card out and putting it back in, or pressing reset, starts it

SSH and the root password

SSH is off. Turning it on in Settings > ADVANCED makes a root password to note down (or
type your own); without one, root can't log in over SSH or the USB serial console.

Files

File For
tetsu-<device>-<version>-sdcard.img.gz New installs
manifest.txt, manifest.sig, tetsu-<device>-<build>.img.gz SYSTEM UPDATE
SHA256SUMS-<device> Checking downloads
tetsu-<device>-<version>-sources.tar.part* The sources of the GPL and other components: cat the parts together into one tar
tetsu-<device>-<version>-licences.csv Every component's licence

Tetsu OS's own code is MIT. The emulator cores keep their own licences: Snes9x, Genesis
Plus GX and PicoDrive may not be used commercially.