#ReverseEngineering / #embedded folx, is it possible that a boot ROM is mapped near the end of the address space such that some of its contents wrap around?
See: https://github.com/NationalSecurityAgency/ghidra/issues/7917
Context: I'm trying to figure out the memory map for the #PocketViewer .
Here I go a bit more computer-science-ish
To Stack or not to Stack, Queue is the Question
How ual reimagines data structures with perspectives: one container, many possibilities.
https://github.com/ha1tch/ual/blob/main/blog/stacks/tostack-or-not_queue-is-the-question.md
In traditional computer science, stacks, queues, priority queues, and other sequential containers are taught as distinct data structures. The ual programming language takes a fundamentally different approach through its stack perspectives model, which unifies these seemingly disparate structures under a single container abstraction.
UPDATE: ual 1.5 proposal
Defer Stack Mechanism
https://github.com/ha1tch/ual/blob/main/spec/ual-1.5-PROPOSAL-defer.md
This document proposes a Go-inspired defer mechanism for ual implemented through a dedicated @defer stack and offering a convenient defer_op syntactic sugar. This feature aims to simplify resource management and enhance error handling robustness.
From Forth to ual
https://github.com/ha1tch/ual/blob/main/doc/philo/ual-philosophy-04-forth.md
This is a new addition from the perspective of the philosophy of programming languages.
Some of you may be interested in this particular addition, feel free to ignore the rest in the series if you are exclusively focused on the Forth-like aspects of ual,
UPDATE: The philosophy of ual.
If you're more the kind of person who would like to understand better from a humanistic point of view what values are encoded in the language, this is for you. It's not a big proclamation, and it's nothing like Larry Wall's exegesis, but I needed to try to understand myself at least in this way that works for me. Hope it works for some of you too.
https://github.com/ha1tch/ual/tree/main/doc/philo
UPDATED: Three new primers added to documentation explaining ual for different programming backgrounds.
Who-Who... Are You?
Mainstream Programmer
Embedded Systems Programmer
Retro or Minimalist Programmer
The README now links to the primers as well from the quicklinks section.
Of course, dear Spidey, that with great power comes great responsibility, creating too many stacks can be overkill for some resource-constrained systems. But this is becoming less of a problem with new multi-core MCUs running at hundreds of Mhz, and with several megabytes of RAM.
What #ual says is: if your machine is not very powerful, we may be able to make it less painful to program highly optimised code for it. If your target machine is powerful, we may help to speed up your development cycles, and you may construct more nuanced, sophisticated, and reliable software with less effort.
New #ual programmers can start coding following most ideas they would assume to work using Lua, and progressively adopt the ual-specific stacked mode when it makes sense. For example, in resource-constrained systems where an algorithm using a Forth-like stack can be more efficient for certain tasks.
The > operator indicates a line that operates on the stack system, using a vocabulary for the most part similar to Forth's.
The @stackname > expression allows the programmer to select on which stack the operations are executed. The system comes with a data stack (@dstack) and a return stack (@rstack) built-in, but you can instantiate new ones, since stacks are first class objects in ual.
Take for example this implementation of Dijkstra's shortest path algorithm, uses its own separate stack to perform its computation.
https://github.com/ha1tch/ual/blob/main/examples/dijkstra.ual
Hope you like it!
This is something I pondered quite a lot about, and it looks almost Rust-like, which I believe offers a better way to handle errors at least for the typical use cases that ual aims for.
Let me know what you think!
Other ideas in the works:
Adding the zxa assembler as one additional backend, to produce Z80 binaries.
https://github.com/ha1tch/zxa
in the future this could allow ual programs to target the ZX Spectrum and the RC2014.
Adding a uxntal backend to produce uxn roms.
Introducing the concept of transmutation
ual is a new programming language for small systems, it borrows from Lua, Forth, and Go/TinyGo.
https://github.com/ha1tch/ual
It's not a scripting language, it compiles to TinyGo, and Go, therefore binaries are produced for the same targets of those compilers. In the case of TinyGo using an optimised LLVM-based backend (esp32, risc-v, wasm, various mcus), and for mainstream server/desktop computing architectures via the Go compiler's own backend (x86-64, arm64, etc.) and OSes (Linux, Mac, Windows).
((Work in progrees))
Not ready to use yet, but I thought I'd RFC before I complete the first implementation, whilst there's still time.
Hope you find it interesting!
Spec:
https://github.com/ha1tch/ual/tree/main/spec
Examples:
https://github.com/ha1tch/ual/tree/main/examples
Let me know what you think!
My latest blog post: Simplify VCD
https://mikecoats.com/simplify-vcd/
Simplify VCD is a tool designed to make working with Value Change Dump (VCD) files more efficient and faster. This tool enables users to clip sections of VCD files, trim irrelevant data, and reduce the resolution to a more manageable timescale, significantly improving processing speed and usability.
Thanks to Mastodon, I have my first external contributor!
An optimized JPEG decoder for embedded devices, JPEGDEC, has been listed by @fast_code_r_us
This library brings efficient image processing to resource-constrained systems.
My latest blog post: VanSpoof - Prototype 2 - Echo Firmware
https://mikecoats.com/van-spoof-prototype-2-firmware-1/
In part 1 and part 2 of building my first VanSpoof prototype, I managed to flash the microcontroller on the PCB with a blinky demo. This time round, let's see about sending and receiving some serial data.
Mein Uhren-Projekt auf embedded graphics umgestellt und 1kloc gelöscht.
Let's gooooo. Dann wird das vielleicht ja doch in absehbarer Zeit fertig.
Fehlt dann nur noch das case. Und der Pico-W damit ich da auch ne echte Uhrzeit drauf bekomme.
#fluConf2025 will feature a track on hardware-hacking and permacomputing. We want to feature articles and presentations that explore matters related to how devices interact with the physical world, how to repair and adapt those devices for different use-cases, and the challenges associated with maintaining any technology over long periods of time.
We welcome proposals that address:
* open chip design, fabrication, and supply chains
* open-source schematics, 3d printing, and all other maker-oriented skills
* off-grid power supply solutions
* advocacy for the right-to-repair and against DRM
* mobile operating systems and gaming hardware
* radio, mesh networks, routing, and all things networking
* creative or useful applications of embedded systems
* peripherals, device drivers, and storage media
* old or unusual processor architectures, or systems featuring specialized co-processors
Apply up until midnight of January 19th, 2025 (anywhere on Earth)
DIY enthusiasts, rejoice! Our Sige7(RK3588) now has 3D blueprints for you to craft custom enclosures. Let your creativity shine! #SBC #embedded #AI #hardware #raspberrypi #opensource #LINUX
Download now and start crafting!
https://drive.google.com/drive/folders/1jMrzK29BGL-MvSF8JiTV1ekhT6T5UK_O
Introducing the #RK3506 chip! Featuring triple Cortex-A7 cores, ultra-low power consumption (200mW), 720P video decoding, and AMP multi-system support. Perfect for #IoT, industrial gateways, and more.
Share your innovative ideas for this chip!
#linux #AI #embedded #maker #hardware #opensource #homelab
Merry Christmas from ArmSoM! For our first festive gift to you, enjoy a special treat when you purchase our Sige7 (RK3588) or Sige5 (RK3576) from Dec 18 to Dec 25th. 
Get a free purple casing with your order! Thank you for your support!
#sbc #embedded #linux #opensource #AI #rockchip #raspberrypi #homelab #nas
