I’ve got a X68000 ACE HD and have been restoring it. The original power supply was dead and I was reparing it. However, even I fix the original power supply, it is for Japanese 100VAC and I am not comfortable using it with American 120VAC. So, I have been working on making a 120VAC power supply unit using ATX power supply along with the PSU repair project. There are many people who have created PSUs for X68000 using ATX power supply.

summary My X68000 ACE HD’s power supply is not working. Recapping was not enough to fix it. Repalced a Zener diode, a transistor, and a voltage regulator to fix. My friend gave me an X68000 ACE HD telling me that it doesn’t power on. X68000 is a 30 year old computer and the capacitor leakage is a very common problem. The X68000 ACE HD seems to have the capacitor leakage in its power supply.

I often need to test batterys voltage before throwing them away. I am using a multimeter to test, but it is cumbersome. I thought it is not too difficult to make battery voltage measurement tool using a microcontroller, so I did it as a little electronics project. Microcontroller I used - M5stack Core I used M5stack Core. It is an ESP32-based microcontroller and it is handy that it comes with a LCD screen.

I wanted to learn about RISCV this holiday break. You can use QEMU to emulate a RISC-V machine environment and you can run Fedora Linux on it. However, it was not straightforward. There are several tutorials online, but things seem to have changed and most of these didn’t successfully boot Linux for me. It took several days, but I finally managed to boot it. Here’s how I did it. My goal My goal was to log on to a Linux environment and issue ls command.

The goal of the project is to drive an MC8250 ACIA chip and send out “Hello World!” message over a serial connection. I have a Serial I/O card of RC2014 project. Its circuit diagram looks like this: The part that surrounded by the red line is the part we’re interested in. MC68B50 is a faster version of the 6850 chip, and its behavior is practically identical to the original MC6850 in this project.

I have not been a fan of Android File Transfer. I remember there are a few sshd for Android. Someone mentioned about SSHelper. While it doesn’t seem to have source code on Github, it is a GPLed open source software by Paul Lutus. It provides ssh access to your android. pc$ ssh 192.168.10.227 -p 2222. Sshd is running on port 2222. User doesn’t matter. You can log in with password by default.

I tried to open a Mac app called Sweet Home 3D.app and it failed. I tried from the command line: $ cd "/Applications/Sweet Home 3D.app/Contents/MacOS" $ ./SweetHome3D dyld: lazy symbol binding failed: Symbol not found: _CGContextSetAllowsAcceleration Referenced from: /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Libraries/libawt.jnilib Expected in: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices dyld: Symbol not found: _CGContextSetAllowsAcceleration Referenced from: /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Libraries/libawt.jnilib Expected in: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices Abort trap: 6 Solution: Install Java for macOS 2017-001. I did this before, but I had to do it again.

I realized that I had to type Control-P twice when I connected to a docker container and was using a command line. I’ve created a docker config file under root home directory: // ~root/.docker/config.json - don't type this { "detachKeys": "ctrl-@" } I am not using control-@. This solved the problem.

setup-environment script OEROOT=sources/poky if [ -e sources/oe-core ]; then OEROOT=sources/oe-core fi ... cd $OEROOT . ./oe-init-build-env $CWD/$1 > /dev/null # if conf/local.conf not generated, no need to go further if [ ! -e conf/local.conf ]; then clean_up && return 1 fi However, this seems not working as intended. Instead, I see the following message on console: Your configuration files at build have not been touched.

I used docker for building Yocto linux images and it used up the space. # docker info ... Data Space Used: 107.4 GB Data Space Total: 107.4 GB Data Space Available: 0 B ... The thin pool (?) is 100GB (107.4GB) and it is full. I found this dicussion on github. You need to increase the pool allowed for your containers. To do this , you will need to remove your var/lib/docker which will destroy all your containers and images.