Watching program flow in a time-sensitive situation

I’m working on some unit test in Java (well, Kotlin) for an Android project. When I set a breakpoint, the failure mode changes because there are timeouts and races going on. This is not an ideal situation, but I’m debugging someone else’s code here. So I found a clever way to log what code is getting called, and from where, by using breakpoint actions. Just put `new RuntimeException().printStackTrace()` in as a breakpoint action! Now your log shows when code got hit, and why it got there, but doesn’t actually stop execution, so it does less intrusive shift to the timeouts and race-conditions.

Receipt Validation on iOS

This has been a pretty major headache: Trying to validate a receipt for an in-app purchase on iOS.

Recomendations:

  1. Use cocoapods OpenSSL-Universal pod to get openssl
  2. Copy Apple’s suggested code, but add the key missing call OpenSSL_add_all_digests() prior to PKCS7_verify()
  3. This last thing is what fixes the mysterious error that reads, “error:2107D06D:PKCS7 routines:PKCS7_BIO_ADD_DIGEST:unknown digest type”

Now, to explore the contents of my ASN1 package!

After installing openvpn I cannot connect to my raspberrypi

So I installed openvpn on my Raspian distro on my Raspberry Pi 2. As soon as I started it up, I lost all connectivity to my Pi.

And I don’t have a display, keyboard, or mouse — all my management has been over the network.

How to recover?

I tried a bunch of things, but here’s what worked, in brief.

  • Power off PI and put SD card in my Mac.
  • Copy the SD card to an image file using `dd`
    • dd bs=32768 if=/dev/disk0 of=if=raspberrypi.img

Now we edit the image. If you have a way to open ext4 filesystems already, just remove the files (see rm step below). Here’s how I did it:

  • Install Veertu emulator (VMWare or VirtualBox would work too) with the latest Finnix Recovery Distro.
  • Create the Finnix VM in Veertu and add a 4GB Hard Disk. Boot it up once so it creates the disk image.
  • Move raspberrypi.img on top of the recovery image, e.g.
    • mv raspberrypi.img ~/VM\ Library/Finnix\ Rescue\ 2/hd1.img
  • Boot Finnix again
  • Mount the image
  • mkdir -p /mnt && mount -t ext4 /dev/sda2 /mnt
  • Remove the openvpn startup scripts
    • rm /etc/rc*/*openvpn
  • Unmount
    • umount /mnt
  • Power off Finnix
    • shutdown -h now
  • Copy the image back onto the SD card:
    • dd bs=32768 if="~/VM\ Library/Finnix\ Rescue\ 2/hd1.img" of=/dev/disk0

Put the SD card in your Raspberry Pi and reboot!

Update: The reason RPi doesn’t boot with open vpn is because ifplugd tries to HOT plug it.  To fix this, explicitly list the real network interfaces in `/etc/default/ifplugd`:

  • Replace
  • INTERFACES="auto"
    HOTPLUG_INTERFACES="all"
  • with
  • HOTPLUG_INTERFACES="eth0 wlan0"

(Do that instead of the rm step above to prevent openvpn from killing the wifi.)

Linea

I’m so excited about Linea, new sketching app for the iPad from Iconfactory. Already we’re seeing some amazing drawings and sketches from users! Creating new software and releasing it into the wild is exciting and thrilling. We’re already hard at work at a dot release, so please give it a try and let us know how you like it.

Now running nginx and secure

So I think I’ve finished migrating my blog to the new server. It’s on Ubuntu 16.04 now, instead of 12, and running on PHP7 instead of PHP5, and on mariadb instead of mysql, and on Nginx instead of Apache.

Lots of little problems came up.

For one thing, the old database was configured so that the character set was latin1 instead of utf8. But wordpress was putting utf8 bytes into it. Which worked fine until I went to migrate the data. Because now-a-days mysqldump delivers data in utf8 encoding by default, so in order to get the bytes out unmolested, I had to specify to dump as latin1. Then, it’s necessary to edit the dumped .sql file and change the latin1 in there to utf8. Quite a headscratcher. If you see accented characters showing up as TWO weird characters, this is probably what happened to you.


ssh user@hostname.tld 'echo XXXXXpasswordXXXXX | mysqldump --default-character-set=latin1 -u root -p database' > data.sql

Next, a shout out to Lets Encrypt which is providing the SSL certificates for my domains. Configuration was incredibly easy.

I’m still running on Linode, which is working reliably — as it has done for the past many years! They no longer let me create an instance of the size I used to use, so my new instance is slightly smaller… when all is said and done I might save a little money!

I’m also trying an experiment where I track changes to my Linux configuration in `/etc` using GIT. Unfortunately, lots of files change in `/etc` for reasons that aren’t meaningful configuration changes… so it will probably be of dubious value.

Now on to the rest of my domains…

FeelieFaces

Have you tried out the new iOS Messages Stickers yet? I bet you’ve found some that are your favorites: silly emoji or some of your favorite Disney characters? My favorite pack so far is FeelieFaces (http://feeliefaces.com) by Sydikos! It’s over two dozen animated faces that show the whole range of human emotion. There are sad face FeelieFaces and happy faces, too! The best one, in my opinion, is the Pirate face who says “Arrrggh!”:

Arrrggh!

SevSeg Arduino and Easy Driver Stepper Motor

This is a continuation of my previous post. When we left off, I was trying to figure out which pins on the Sparkfun SevSeg display I could repurpose for my own purposes as digital out pins.

I did some research on the ATMega chip, and it is pretty clear that most of the pins on the top row of the SevSeg could be used for other purposes. Having identified which (Arduino) pins were connected to the display, I was able to figure out which pins were connected to the top row of solder points by using a simple programs that displayed a number on the LCD while simultaneously toggling that pins state to high and low. I had some trial and error — for example my multimeter takes about 4 seconds to register a change in voltage and my initial script was changing the voltages faster than that… at first it seemed like nothing was happening! But finally I figured out the pin numbers for the solder points. Only after I did all that did I look in the header file provided by the Sparkfun “board” for the SevSeg and see that they’d provided convenient macros for those points! All in all I found 6 available digital I/O pins.

I decided to connect five pins to the Easy Driver — Enable, Step, Dir, MS1 and MS2. I left MS3 disconnected. This will allow me to control the direction of rotation, turn off power to the motor, and use half, quarter and one-eight stepping modes for slow speeds.

That left one pin for a button. I verified that I could make inputs work by simply connecting one output pin to one input pin by sliding a resistor between the two solder points. When I programmatically set one of them to output HIGH while putting the other into INPUT_PULLUP, I verified that I could read a state change.

Next I soldered connections between the buttons and the EasyDriver and the SevSeg. I’m also using the EasyDriver as a power supply for the SevSeg.

I found some example code for how to drive the stepper motor by sending alternating HIGH and LOW pulses to the STEP pin, each with some delay. This worked perfectly, on the first try. However, when I tried adding the digital display to show how many rotations are left, I ran into a problem. The SevSeg.cpp uses delays internally to rapidly illuminate each digit in succession. I also needed carefully timed delays between each STEP I send to the stepper. Arduino doesn’t have any threading support. I was facing having to build some kind of scheduler to allow these two tasks to do small bits of work offset by time delays. Ugh.

But then I discovered the clever pt.h “threads” library by Adam Dunkels. This imposes some pretty strict limitations on your “C” code — e.g. locals are not persistent across WAITs. But the solution to that was the (normally frowned upon) practice of using static/globals for everything! The original SevSeg library was built around a C++ object, which I had to refactor to be a static “C” function — easily done once I made all its member fields public (another no-no, normally!).

The end result: I can control both the motor and the display simultaneously without one (significantly) interfering with the other.

And here is a demo of the finished project:

Using Sparkfun 7-Segment Display as an Arduino : Part 1

Today I opened my new Sparkfun 7-Segment display and tried my hand at using it as a general purpose Arduino controller. My ultimate plan is to use it to drive a stepper motor and to respond to the input of a push button. However, this item interested me because it has 4 7-segment LED displays attached to it, which means my project could provide some minimum visual feedback.

First, I opened the package and soldered 6 header pins onto the end — put them inside where the package is silk screened with a little white line. I plugged in a FTDI connector and plugged that into my Mac. It displayed a zero on the first of the LED displays.

Next I installed the Arduino IDE and the FTDI driver for my Mac. The instructions for FTDI driver installer said to run a command `sudo kextunload –b com.apple.driver.AppleUSBFTDI` but that just gave me an error message (“Can’t create –b. Can’t create com.apple.driver.AppleUSBFTDI.”) so I don’t know if it did anything.

Next I tried running some sample SevSeg.cpp files but had trouble.

I realized I needed to program this device using a definition provided by Sparkfun. I followed the instructions in this repo’s readme file to install those definitions: https://github.com/sparkfun/Arduino_Boards and then selected “Sparkfun Serial 7-Segment Display” from the Arduino IDE Tools -> Board menu.

I found the SevSeg project and copied the files (SevSeg.cpp and SevSeg.h) next to my Arduino project file (SayHello.ino). Word of warning: This library just emits a blank character for letters that don’t have any mapping into LCD (e.g. K, V, W, M…) I guess it’s cool that it even tries to draw any letters at all…

Finally I had to figure out the pin order for this particular display. The SevSeg project requires about 18 integer parameters when it is initialized… and I had trouble mapping pinouts (for example from this spec for the display: http://dlnmh9ip6v2uc.cloudfront.net/datasheets/Components/LED/Serial-7-Segment-Display-v31.pdf) to the parameters. One of the things I’m immediately finding myself annoyed with in Arduino is the lack of transparency around what pins are called…. apparently each board renames the ATMega pins (which already have names like PB0 or PC4) to a new number. Finally I was able to solve this by looking at the firmware for the Sevseg display and copying the key values from there:

int digit1 = 16; // DIG1 = A2/16 (PC2)
int digit2 = 17; // DIG2 = A3/17 (PC3)
int digit3 = 3; // DIG3 = D3 (PD3)
int digit4 = 4; // DIG4 = D4 (PD4)

//Declare what pins are connected to the segments
int segA = 8; // A = D8 (PB0)
int segB = 14; // B = A0 (PC0)
int segC = 6; // C = D6 (PD6), shares a pin with colon cathode
int segD = A1; // D = A1 (PC1)
int segE = 23; // E = PB7 (not a standard Arduino pin: Must add PB7 as digital pin 23 to pins_arduino.h)
int segF = 7; // F = D7 (PD6), shares a pin with apostrophe cathode
int segG = 5; // G = D5 (PD5)
int segDP= 22; //DP = PB6 (not a standard Arduino pin: Must add PB6 as digital pin 22 to pins_arduino.h)

int digitColon = 2; // COL-A = D2 (PD2) (anode of colon)
int segmentColon = 6; // COL-C = D6 (PD6) (cathode of colon), shares a pin with C
int digitApostrophe = 9; // APOS-A = D9 (PB1) (anode of apostrophe)
int segmentApostrophe = 7; // APOS-C = D7 (PD7) (cathode of apostrophe), shares a pin with F

int numberOfDigits = 4; //Do you have a 2 or 4 digit display?

int displayType = COMMON_ANODE; //SparkFun 10mm height displays are common anode

//Initialize the SevSeg library with all the pins needed for this type of display
myDisplay.Begin(displayType, numberOfDigits,
digit1, digit2, digit3, digit4,
digitColon, digitApostrophe,
segA, segB, segC, segD, segE, segF, segG,
segDP,
segmentColon, segmentApostrophe);

My next objective is to see if I can repurpose the pins on the top of the display to control a stepper motor and read a button. Those are silk screened on the display as A7, A6, GND, VCC, SD0, SCK, RST, SD1, SS (with a bar), and RX. I haven’t yet figured out what those pins are called in arduino-speak, nor what their ATMega names are either. Stay tuned…