More old tech, more blog posts. This time about a Thinkpad 220. No, not the X220, the 220. A 1993 vintage, Japan only, ultra compact Thinkpad! There is not much online about these so let’s fix that!
I saw one of these laptops for sale, untested, on Marktplaats. A Dutch Ebay so to say. It was looking a little rough but the fact that this laptop popped up at all was amazing, and luckily my offer got accepted. So a few days later I was greeted with a dirty laptop. No adapter or anything, just a laptop.
Luckily, powering this laptop is oddly easy. It just takes some AAs
Oh yes. Just stuff some AAs in it. I like it! Now, just alkaline AAs work, sadly there is no support for rechargables.
And it just works. Huh. Well there are a few errors related to an empty cmos battery, which is not surprising at all. So, it just needs a clean! Which means a full disassembly. Which there is zero info about online.
Guess why I am typing this blog :)
First, some history
This Thinkpad was launched in 1993, and it was made by IBM and Ricoh, just like the more known PC 110. That laptop is is even smaller but has a cramped keyboard and made a few years later. Like the PC 110, this was only sold in Japan. They really like their small computers over there!
Specs wise, you’d get an Intel 386, 2 to 6MB RAM and an 80MB HDD. This all in a 1KG package, less then even most modern laptops! The screen is 640*480 monochrome and has some backlight.
The 220 initially was a 10th year anniversary addition for the IBM 5550 and apparently IBM made 5550 of them and they where popular enough they ended up selling 20.000! These where sold for around 200.00 yen in 1993, which is around 230.00 yen today, as the inflation in Japan is quite low. That’s still around 1500 USD today!
A peek underneath
After removing the battery pack, the bottom comes off with a few screws. And there is a few fun things under here. First of all, upgradable memory! There is 2MB on the motherboard, but the optional module can extend it up to 6MB. On my machine it’s maxed out. And there is a power supply module kinda just plugged in there. Let’s remove those two things for now.
After removing the big ribbon cable, the HDD can be seen but cannot be accessed from the bottom. It’s screwed in from, it appears like, the top. So let’s soldier on and disassemble it more.
After all screws are removed from the bottom side. the top plastic can carefully be popped off. 2 more screws and the keyboard can be removed. And after all this, finally, the HDD can be removed! Now, for a full disassemble, a few more parts need to come out.
And there we go. There is a small PCB on the bottom for all the miscellaneous parts, trackball, speaker, leds and all that. This also contains a small rechargeable li-ion, which is very dead by now. It’s used for suspend to ram but the machine works fine without. I decided to remove it before it can leak. A small gotcha is in the floppy connector, it has 2 screws. I missed those at first and could not get the motherboard out!
Time for a clean
With everything apart, cleaning this machine is pretty easy! I tend to clean mostly with a degreaser, warm water and patience. The plastic on older Thinkpads can get sticky sometimes, but this one seems fine so far luckily!
After that, it’s just reassembling, carefully, and there we go, a nice and clean machine!
Perhaps this will help someone in the future, as these laptops seem quite rare and hard to find info about. And as always, welcome yo buy me a coffee!
First things first: This is the first post of the year, halfway in the year. A move got in the way but a few fun things are in the pipeline :) With that out of the way, let’s take a peek in how small computing could be in the early 1990s. Nowadays small form factor computers are everywhere. Intel’s NUC from the early 2010’s, Apple launched the Mac Mini in the mid 2000s, and plenty more examples exist. Most big brands make tiny computers for office use that just take up 1L of space. But back in the late 80s and early 90s, this was not that common. One of the earlier tiny computers was the Sun SPARCstation IPC, and a little later the Sun SPARCstation IPX. At roughly 26x26x13cm it’s not small by modern standards, but back in the day it sure was tiny!
It’s not the smallest but at least the IPX has the power supply internally!
The Sun SPARCstation IPX in this photo was send to me by a friend to repair, as it didn’t output anything on a monitor. So let’s have a peek inside, see how to repair it and take a look at what kind of maintenance a computer from 1991 needs!
I always liked the idea of Litex, a framework to easily build a SoC for an FPGA, but never really made time to try it out. So let’s change that and write down how it went! I am using a Sipeed Tang Nano 9K FPGA board, which is a fairly cheap bit of kit, but most of this blog should apply to any supported FPGA.
Now, there was a little bit of a learning curve. Litex is written in Python, or a little more specific, it uses Migen, a python based tool that generated Verilog. I never coded much Python, let alone Migen. I wanted to learn a couple of things to say I know the basics of Litex
Understand a minimal SoC example
Customize a SoC with some peripherals already in Lite
Code custom firmware and run it on the created SoC
Have a way of working that’s somewhat pleasant to use
Before I get to all of that, let’s first install Litex and build an example!
Building the example SoC
If running a modern Linux, this is fairly straightforward, and following their guide works on Debian 12. To be able to build some examples, the standard or full config is needed, and a RISC-V toolchain needs to be installed. Luckily the quick start guide nicely explains all that and how to do so.
Now to the Gowin toolchain. It’s not open source, but free at least, but you need to apply for a free license. It can be downloaded here after registering. An open source toolchain is being developed but at the time of writing not complete enough to use with Litex.
The gw_sh binary from Gowin has to be added to the path, so a line in the likes of this in .bashrc should do:
PATH="$PATH:/path/to/gowin/IDE/bin"
After installation, navigate to the “litex/litex-boards/litex_boards/targets” folder and run:
./sipeed_tang_nano_9k.py --build --flash
This will take a good bit of time, but it should compile, synthesize, PnR and then flash the fpga. The LEDs will blink in a nice pattern and when a serial port is opened at 115200 baud to the board, the following should greet you:
Pfff, that was a bit of work to get going, something to put in a docker perhaps…. :)
Now I can build the example, but I have no clue what it all does. Luckily a minimal example is included, let’s just take a peek at that. I took a moment to remove all that I could from the sipeed 9K example to more match the simple.py example and ended up with this:
import os
from migen import *
from litex.gen import *
from litex_boards.platforms import sipeed_tang_nano_9k
from litex.build.io import CRG
from litex.soc.integration.soc_core import *
from litex.soc.integration.soc import SoCRegion
from litex.soc.integration.builder import *
kB = 1024
mB = 1024*kB
# BaseSoC ------------------------------------------------------------------------------------------
class BaseSoC(SoCCore):
def __init__(self, **kwargs):
platform = sipeed_tang_nano_9k.Platform()
sys_clk_freq = int(1e9/platform.default_clk_period)
# CRG --------------------------------------------------------------------------------------
self.crg = CRG(platform.request(platform.default_clk_name))
# SoCCore ----------------------------------------------------------------------------------
kwargs["integrated_rom_size"] = 64*kB
kwargs["integrated_sram_size"] = 8*kB
SoCCore.__init__(self, platform, sys_clk_freq, ident="Tiny LiteX SoC on Tang Nano 9K", **kwargs)
# Build --------------------------------------------------------------------------------------------
def main():
from litex.build.parser import LiteXArgumentParser
parser = LiteXArgumentParser(platform=sipeed_tang_nano_9K_platform.Platform, description="Tiny LiteX SoC on Tang Nano 9K.")
parser.add_target_argument("--flash", action="store_true", help="Flash Bitstream.")
args = parser.parse_args()
soc = BaseSoC( **parser.soc_argdict)
builder = Builder(soc, **parser.builder_argdict)
if args.build:
builder.build(**parser.toolchain_argdict)
if args.load:
prog = soc.platform.create_programmer("openfpgaloader")
prog.load_bitstream(builder.get_bitstream_filename(mode="sram"))
if args.flash:
prog = soc.platform.create_programmer("openfpgaloader")
prog.flash(0, builder.get_bitstream_filename(mode="flash", ext=".fs"))
prog.flash(0, builder.get_bios_filename(), external=True)
if __name__ == "__main__":
main()
Wow, that’s around 50 lines, not too bad. But it turns out, a lot of magic happens in Litex to keep this small. Let’s try to break it down a bit!
But what does it all do?
First, some imports and defines,
from litex_boards.platforms import sipeed_tang_nano_9k
imports the platform file, this file contains all the IOs and peripherals, it also includes some information about the programmer to use and the clock speed of the on board oscillator. For a custom board, a file like this has to be created from scratch.
The rest of the imports pull in migen, the HDL language used in Litex, and some basic builders to build the SoC.
import os
from migen import *
from litex.gen import *
from litex_boards.platforms import sipeed_tang_nano_9k
from litex.build.io import CRG
from litex.soc.integration.soc_core import *
from litex.soc.integration.soc import SoCRegion
from litex.soc.integration.builder import *
kB = 1024
mB = 1024*kB
Now time to jump to the bottom of the code and take a look at the main function:
First of all, the LitexArgumentParser is imported and instantiated. This is a super handy feature in Litex that makes it easy to custimize a SoC with command line arguments. Run
./sipeed_tang_nano_9k.py --help
to get all the options, here is just a few of them for example:
Yes, selecting a different CPU is just a command line argument away, awesome!
Then the BaseSoc function is called, which is used to customize our SoC. We’ll look at that in a bit. Then the Litex Builder is called with our SoC as argument to generate the final SoC.
At last, the –load and –flash argument are handled. They both call the OpenFPGALoader tool to either load a bitstream in RAM or flash it in SPI flash on the FPGA board. The OpenFPGALoader tool is installed with the Litex_setup script.
The BaseSoC class creates the SoC to be fed into the Litex Builder in a bit. A basic SoC in Litex contains a Vexriscv CPU, wishbone bus, some RAM, ROM, a timer and a UART peripheral. But that’s the basics, it can be customized here. For now I specify the system clock frequency and generate a CRG. CRG means Clock Reset Generator and should contain any clocks and resets. For now there is just a single clock but let’s look into that more later on.
I also specify the rom and ram size, but this could even be removed if the defaults are fine. All this information is fed into the SoCCore.__init__ function that returns our SoC.
And there we go, a minimal SoC, awesome. It can also be viewed in full in Github.
Now let’s slowly add some new functions to it!
Adding a clock reset generator
The CRG currently is very limited compared to the one in the example. There isn’t even a reset button! Let’s change that and introduce a PLL and a Reset.
Compared to before, the CRG now uses one of the user buttons as a reset input. A PLL is generated that for now has the same input frequency as output frequency, but this can be changed by passing a parameter with a requested system clock frequency, neat! The reset pin resets the PLL, which in term resets the CPU. A full diff compared to the previous SoC can be seen here.
Finally, peripheral time!
There are quite a few peripherals already available in Litex, timers, uart, I2C, SPI and more. Sadly the documentation can be a little lacking, but after some digging around I got most of them to work. So let’s add a few things in the sipeed_tang_nano_9k.py file!
To add some peripherals, first they need to be imported:
from litex.soc.cores.timer import *
from litex.soc.cores.gpio import *
from litex.soc.cores.bitbang import I2CMaster
from litex.soc.cores.spi import SPIMaster
from litex.soc.cores import uart
There, that takes care of the most common ones. Instantiating is luckily pretty easy too!
Two more timers, some LEDs, I2C, UART and a GPIO input, just in a few lines. That is a TON easier then doing this in VHDL or Verilog. Now the platform file needs to be expanded a bit too so Litex knows what to place on what IOs:
Perfect! But there is a small tiny issue still. Well two actually. But the first one that is bothering me is that editing this all in the litex-boards repo is not really, ideal.
Time to make a separate folder for all of this, heck, a docker would be even nicer.
Containerize it all
When talking with a friend about running this all on a macbook, and the gowin IDE being not available for Mac OS he whipped up a small docker container for setting it up, just enter a license file location and good to go! I made a few small changes to it, mostly to set the workdir and add vim. So checkout that repo and give it a go!
With this, it should be possible to run Litex with the Gowin tooling reliable on any computer, regardless of OS and distro. Ok, that is one issue taken care of, now to separate it all. I finally settled on a folder with the following structure:
platform contains the platform file and software the C source code for the program on the SoC, which can be found on my Github.
When starting the docker container, I bind the folder to docker as such:
The license file depends on mac address, so be sure to set your mac address in the docker to match the one for your license. Best would be to use a mac address generator and check that nothing in your network uses the generated mac address so there is no chance of any collisions or other network shenanigans.
After starting the container I end up in the correct folder immediately and I’m a single
./sipeed_tang_nano_9k.py --build
away from building!
Alright, the software folder is already showing up in there, but how did I get that far is another story.
Software woes
To start with, I looked at the demo application in Litex, and compiled that. It can be “uploaded” by integrating it in the internal rom of an SoC, but that means rebuilding the entire SoC on every software change. That’s quite hassle if you want to quickly reiterate on code.
Luckily, Litex also has a nice program called litex_term, which can be used to upload binaries and to have a terminal connected to the SoC. The default bios in Litex can accept a binary on boot, and run it, a little like the bootloader in an Arduino. Using it is pretty simple, run
litex_term /dev/TTYhere --kernel=yourapp.bin
and to upload the binary again after a change, just reset the board!
Now, this means there must be some RAM on your SoC that can be changed and is not used for the bios code. Can’t have your new code loaded in the RAM of the bios application of course. On some FPGA’s there is enough space to have 2 big blocks of RAM, but I opted to use the internal HyperRAM of the FPGA. This is also what the example uses and that seems to work quite well. The code to add this to the SoC is as follows:
# HyperRAM ---------------------------------------------------------------------------------
if not self.integrated_main_ram_size:
# TODO: Use second 32Mbit PSRAM chip.
dq = platform.request("IO_psram_dq")
rwds = platform.request("IO_psram_rwds")
reset_n = platform.request("O_psram_reset_n")
cs_n = platform.request("O_psram_cs_n")
ck = platform.request("O_psram_ck")
ck_n = platform.request("O_psram_ck_n")
class HyperRAMPads:
def __init__(self, n):
self.clk = Signal()
self.rst_n = reset_n[n]
self.dq = dq[8*n:8*(n+1)]
self.cs_n = cs_n[n]
self.rwds = rwds[n]
# FIXME: Issue with upstream HyperRAM core, so the old one is checked in in the repo for now
hyperram_pads = HyperRAMPads(0)
self.comb += ck[0].eq(hyperram_pads.clk)
self.comb += ck_n[0].eq(~hyperram_pads.clk)
self.hyperram = HyperRAM(hyperram_pads)
self.bus.add_slave("main_ram", slave=self.hyperram.bus, region=SoCRegion(origin=self.mem_map["main_ram"], size=4*mB))
self.add_constant("CONFIG_MAIN_RAM_INIT") # This disables the memory test on the hyperram and saves some boottime
Now that is one hurdle, but I want to be able to compile my own code, separate from the litex repo’s, but while using their pre-made drivers and such. After some experimentation, I ended up with the following makefile. The magic bits are the build and include dirs at the top:
BUILD_DIR=../../build/sipeed_tang_nano_9k
SOC_DIR=/usr/local/share/litex/litex/litex/litex/soc/
include $(BUILD_DIR)/software/include/generated/variables.mak
include $(SOC_DIR)/software/common.mak
Oddly enough, in the readme for the demo, Litex uses a small python script to compile. I decided to just stick with a makefile as that is also what the python file seems to call. My code is very much based on the demo application, first stripped and then with new code for the new peripherals added.
Peripheral drivers
After generating an SoC with some IOs, I2C and more, I want to use those peripherals! Most of them are quite simple to use, but there is not really any documentation on how to do so. The best course of action is to look at the migen code and let Litex generate a document with all the registers. The can by done by adding the “–soc-csv” option. For example:
will output a file soc.csv with all the registers inside. –soc-json and –soc-svd are also possible for JSON and SVD files.
Some C include files are also generated on a build, especially csr.h in the build/sipeed_tang_nano_9k/software/include/generated/ is very useful, and for small peripherals using the functions in here is perfectly viable.
As an example, for reading the gpio pins, the “gpio_in_read” function works as expected.
For some, there are drivers available in Litex. I2C for example has a driver that works really well and can handle more then one I2C peripheral being generated, awesome!
One thing that was not clear however was using interrupts, so let’s take a dive into that real quick!
Interrupt woes
Enabling interrupts is pretty easy on the Litex/FPGA side of things. In general the irq.add function will take care of all that! For example:
I removed some #defines for clarity, but it will only handle the uart interrupt for the default uart! So either I need to change this file in Litex, or not use the Litex libraries. Ooooor make a small change and a PR. What I did is change the above code to the following:
// Weak function that can be overriden in own software for any IRQ that is not the uart.
// Return true (not zero) if an IRQ was handled, or 0 if not.
unsigned int __attribute__((weak)) isr_handler(int irqs);
// Override by default with return 0
unsigned int isr_handler(int irqs)
{
return 0;
}
...
void isr(void)
{
__attribute__((unused)) unsigned int irqs;
irqs = irq_pending() & irq_getmask();
if(irqs & (1 << UART_INTERRUPT))
uart_isr();
else
if(!isr_handler(irqs))
printf("Unhandled irq!\n");
}
So a simple __weak__ function is defined at the top, a weak function means that if the exact same function exists anywhere else, it will override the weak function. If it doesn’t exist it will call the weak function.
This means that if an interrupt happens that is not the uart interrupt, it will call the isr_handler(). If you implement it in your own code, awesome, it goes there and runs that. Otherwise no harm done, it will call the one in here.
In this case, if the interrupt that happens is the GPIO_INTERRUPT, I will handle it and return 1, otherwise 0 and the isr can throw a nice warning :) This is currently on a branch as a PR and not merged, so for now make sure to use that branch!
In the style of the original demo, I created a program with that reads the serial port and can execute a few commands to test I2C, gpio, timer interupts and so on. The full code can be found here. Now there is just one small thing left I’d like to figure out. Making my own peripheral!
Creating a custom peripheral
To get a bit of a feeling for making a peripheral, I decided to make a simple pwm peripheral. Something simple that just generates a PWM signal at a given frequency and duty cycle. Internally it should have a counter and when the counter is below or above a certain value toggle an IO pin to control the PWM duty cycle.
It should have a few registers:
An enable register, to enable/disable the PWM peripheral
A divider register, to be able to make lower frequency PWM signals
A maximum count register, it should count to this value and then reset it’s internal counter
A duty cycle register, if the counter is below this value, the IO pin should be low, otherwise it should be high.
That all sounds pretty doable, and while Migen reads quite different then Verilog or VHDL, it does make for some compact code because of all the Litex goodies.
For starters, making a register and connecting it to a CPU is very easy:
from migen import *
from litex.soc.interconnect.csr import *
from litex.gen import *
class PwmModule(LiteXModule):
def __init__(self, pad, clock_domain="sys"):
self.divider = CSRStorage(size=16, reset=0, description="Clock divider")
Just a few lines, and a simple peripheral is made! It just is a single 16 bits register but hey, that’s pretty amazing! No need to worry about CPU busses or anything. The CSRStorage is not the fastest method but for a peripheral like PWM it’s plenty.
So let’s quickly make that complete peripheral shall we!
A few more registers, and some internal counters for dividing the clock signal and the PWM counter. A complete and usable peripheral in a little over 30 lines, awesome!
And to use this peripheral in the SoC, just a single line is needed:
self.pwm0 = PwmModule(platform.request("pwm0"))
On the software side, just a few registers need to be set:
And with that all settled, the complete code for the SoC can be found here.
Conclusion
That was fun! From nothing to an FPGA SoC with some custom peripherals going on, awesome. And that in quite a small number of lines of code. I’m pretty amazed by what Litex can do!
Of course, it’s not perfect, and currently the at times lacking documentation is a bit of a bummer. Hopefully this blog at least helps a little. I am considering to look at creating some more advances peripherals, that HDMI port is alluring! I also want to at some time look at mixing Verilog/VHDL and Migen, which should be very possible. For now I think that this blog is long enough already.
If you enjoyed this blog, please consider buying me a coffee!
A long while back I picked up an old Tektronix logic analyzer. It was in decent shape but threw an error on the self test. To be more specific, the triggering board was faulty. But that means it was almost free and how can I say no to a repair job! Especially to some weird fun Tektronix box with a CRT touchscreen.
So let’s have a look inside and see what the issue might be.
Ok ok ok, this is not a Nixie, it’s a Panaplex watch, but that sounds so much less fun. They work like nixies, but they are flat and often 7 segment displays, somewhat common in alarm clocks and tech gear.I got a few of them from a friend and compared to nixies, they are rather small and flat. So why not make a wristwatch with them!
Like nixies, panaplex displays require a high voltage to operate, around 200V. Which, on a wristwatch is a little challenging. I also wanted this to be a somewhat usable watch, unlike some of the nixie watches that, while cool, look quite cumbersome to wear due to their size.
This display is the ZM1570, which according to the datasheet, is similar to the ZM1550 but a little radioactive, fun!
So let’s look at what it takes to make a watch with these and how small all the circuitry can be.
Yes I bought more 1980s computers. This time an HP9000/310. This is a computer launched in 1985 meant to control measuring equipment via HPIB, the interface later renamed to GBIP and still in use today. Now, a computer from the 80s meant to control EE equipment is not something I could not buy right?
The computer was stored working, but a little dirty. I first checked if the power supply was operating in spec and if there was any visible damage from things like leaking capacitors or batteries. That all seemed OK, so let’s turn it on!
And indeed, it still works! Now let’s take a good look at it, give it a clean and see if I can make it do something fun.
A while back I got a Siemens luggable computer from a friend. It’s a computer from the mid 1980s and it was not working anymore. The latest state was “smoke came out when I turned it on” so it needed some repairs. This is not a personal computer, but instead a computer made to program and debug Siemens Simatic S5 PLCs.
This was kind of perfect as I wanted to try out something new. I wanted to try making a video thingy/blog and see how that goes. So I guess this would be Just Another Electronics Video Blog? Don’t worry, it won’t replace the written blog, but I think that some topics are a little nicer on video and some are nicer written.
It took a few years, but it’s finally possible to order an affordable Linux capable RISCV CPU. The Lichee RV is a small System On Module (SOM) with the Allwinner D1 System on Chip (SoC). This SoC contains a 1Ghz RISCV64GCV single core CPU. The SOM comes with 512MB of RAM, although some 1GB versions have popped up, and costs less then 30 euro’s delivered. The CPU on the Allwinner D1 is also open source, which is pretty neat. Sipeed makes a ton of interesting boards, like the FPGA boards I recently covered. They didn’t sponsor this post, I just think they make cool stuff!
There is also a small dock that it can be mounted on that has HDMI, USB, Wifi and more broken out. But I wanted to have a few different interfaces. I like having good old Ethernet and I also wanted a headphone jack. So how hard can it be to design a dock with those interfaces and get Linux to co-operate? Let’s find out!
When the Raspberry pi launched in 2012, it sold out immediately and became an instant hit overnight. The combination of a powerful enough Linux board, capable of Full HD video and an unbelievably low price of $25 was unheard of back in the day. And after 10 years, well over 40 million of them have been sold.
Of course, this was not the first Single Board Computer (SBC) that could run Linux. When I saw an add pop up on the local version of Ebay with some Atmel Linux boards from 2007 I was curious. When I saw it was an AVR32 CPU, something that Atmel discontinued quite a while ago, I gotten even more curious and picked them up. It even came with a CD with the original board support package (BSP)
So let’s have a look at this SBC, the AVR32 CPU, how to use them in 2022 and what they can still do.
The Atmel NGW100 SBC
The NGW100 was a SBC from Atmel, which was $100 or $50 with student discount from what I could find. The AVR32 CPU ran at 140Mhz and was paired to 32MB of SDRAM. A big difference from the 700Mhz CPU and 256/512MB RAM of the first Raspberry pi! For storage, it has 8MB parallel flash and 8MB SPI flash. The latter can only be used for data storage. Of course there is an SD-card slot but it cannot boot from that directly. A bootloader like u-boot has to be located on the 8MB parallel flash which could then boot from SD-card.
Now of course, this board has not 1 but 2 network ports! That makes up for the lack of video out right? And yes, there used to be OpenWRT support for this board, though I doubt it makes for a good router nowadays.
I gotten yet another odd piece of electronic test equipment. This time something that seems to be an early storage oscilloscope. It looked very interesting as it has more buttons then I have seen on a scope yet, so I had to pick it up (I swear I don’t have a problem :) )
I couldn’t find much information online about it. No user manuals, let alone a service manual. I did find a little bit of information calling it a universal waveform analyzer. So let’s see what it is, how to use it and what’s inside. Warning, this blog post is a bit picture heavy!
