Posted Thu 13-Sep-2012
The board design for the SNES wireless controller project is proceeding nicely. I recently finished the main controller schematic, after running into multiple difficulties about how exactly to implement its electronics. Next up: laying out the circuit board. This presented its own set of challenges, which eventually led to me developing a powerful tool for simplifying the layout of complicated circuit boards.more...
Posted Wed 12-Sep-2012
One of the problems we faced when designing the schematic for the wireless SNES controller, is whether to leave the original PCB in, or fabricate a complete replacement. Implementing the controller on a smaller circuit board would make it cheaper to manufacure: most PCB prototyping companies bill by the square inch. However, using a smaller board would result in an extremely cramped layout, and might require physical modification of the plastic supports on the inside of the circuit board. Instead, we decided to replace the entire PCB. As we had already decided this project was for fun, money was no object. Also, the larger amount of space on the bigger board makes it easer to route the circuit. Unfortunately, there is one more downside to the full PCB approach: the replacement PCB must fit exactly into the space left by the older board. This led to another issue: the PCB will only fit in a single brand of SNES Controller.more...
Posted Mon 8-Aug-2011
Suppose you have an old joystick that you want to use to control your
latest micro-controller project. These joysticks use a DB-15 connector
with a readily available
pinout. A Game
Port style joystick consists of digital buttons, and analog axes. In
this post, I will go over how to optimally interface the axes of these
types of joysticks with your microcontroller.
Inside of the joystick, mounted at right angles are potentiometers, one for each axis:
Posted Mon 16-May-2011
Recently I took a class on Embedded Systems at Portand State University, and was required to program a bare metal ARM development board. This is a continuation of my notes on how to program the board. You can read the first part here.
In order for this development environment to work, we need to implement the syscalls that newlib will use for the C standard library. Most of the required syscalls are necessary in order to access abstractions that wont make sense on the development board. For example, with a concept of a process, there is no need for the fork() system call. In fact, the only system call we really need to implement is sbrk().more...
Posted Mon 16-May-2011
I recently took a class on Embedded systems design at PSU. In this class, we covered designing memory systems, serial busses, as well as sensors, transducers, and outputs. The labs for this class used an ARM development board based on the (then Intel) PXA270 microprocessor. Students were supposed to develop software in ARM assembly to demonstrate what was learned in class.
I decided to implement my solutions in C to provide more of a challenge. In order to do this, I needed to set up a development environment to cross-compile C code for the PXA270.more...