1. 34

Pics and videos in the link, (terrible) source code available here.

The source code pack includes all the bike shedding bits, from the ray tracer to the spectrum emulator and beyond.

I’m waiting on the 2020 TTGO Watch, then I’ll look at turning into something less hideous under the hood. In the meantime I’m going to learn more FreeRTOS and LVGL as I really struggled there.

  1.  

  2. 4

    I love it.

    Any chance of replicating the look of the AmigaOS 1.x clock? https://guidebookgallery.org/pics/gui/applications/office/clock/amigaos10-1-1.png

    1. 3

      I did actually look into this. If you look carefully you’ll see a 1.x clock bitmap is the Timer mode icon. I think it’s from 1.3.

      I had ideas while using Bodmer’s TFT_eSPI to reimplement the clock. Initially I wanted to see if I could knock up a 68k emulator and run the code from the original binary on it, but I realised I’d need to pull apart the hunk binary format and reverse engineer it.

      From what I could tell it looks like the Workbench clock binary draws the screen by hand as polygons. I would like to reimplement it or ideally simulate it but I don’t have a 1.3 install to hand with snoopdos and resource on the same box. When I started using LVGL I realised that it (or rather I) isn’t really very good for drawing custom primitives.

      At the moment my plan is to take a break and focus on learning more about FreeRTOS task management and more about LVGL and how it’s put together. Then I’ll look at doing another rewrite but from the ground up instead of using the TTGO library nCov example as the basis.

      1. 2

        AROS is a binary compatible Amiga runtime, and the clock is going to be a standard Intuition app, so you can probably take what you need to run the original clock binary from there (or use their clock tool).

        1. 1

          I’m familiar with AROS as a user, but not so much with the code underneath. Part of the reason I decided not to pursue active emulation was that it would take an awful lot of time to get things to a point where it could run a single clock app, but there’s a whole load of secondary issues from UI to power saving that complicate matters even more.

          ISTR AROS needing an MMU, not sure whether I imagined that or not.

          1. 2

            I think you did :). The platform page for m68k suggests a 68020 with >=6MB fast RAM, and the 68020 didn’t have FPU or MMU.