Springboards
Visor Springboards
One of the key reasons I bought a Handspring Visor, was the expandability via the Springboard slot. There are modems – wired and wireless; MP3 players; voice recorders; memory modules; backup modules; pager modules; cell-phone modules… the list goes on. And new modules are being announced regularly.
I have a couple modules myself, naturally I have taken them apart to see how they work and what, if anything, can be done to or with them as far as modifications. So far, the answer has been, not much. Though I have at least got to see the insides, and I’ll share that with you.
The Modules – Reviewed and Dissected
- Innogear’s InnoPak/2V
- Handspring’s Backup Module
- Handspring’s Flash Module
- Handspring’s Tiger Woods PGA Golf Module
- Taking Modules Apart
Some Basic Information
The Springboard specifications were set out by Handspring as they developed their PDA. Though it is a ‘proprietary’ solution, they seem to have been successful in getting a lot of other companies interested in making peripherals and accessories for their platform, and have also licensed the Springboard slot to a few companies who will use it as part of their own products.
The connector itself is actually identical to the 68-pin connector of a PCMCIA device — mechanically identical, but electronically, some of the pin assignments are different. The slot is ‘keyed’ so that PCMCIA cards cannot be inserted.
Innogear’s InnoPak/2V
The InnoPak/2V from Innogear contains 2MB of Flash memory, combined with a vibrating silent-alert. It contains three applications preinstalled:
File Mover (For moving data and apps between the Visor and Springboard memory — essentially the same app as in the 8MB Flash Module.)
IP Test (To test the function of the vibrating motor)
IP Conf (Toggles between audible or vibrating alert mode).
When the InnoPak/2V is plugged into the Visor, a logo is briefly flashed, and the 3 applications automatically appear in your Launcher. To toggle the silent alarm, you can either run the IP Conf application, or you can simply tap the screen in the very lower right corner of the Find box, which is a shortcut to the IP Conf program.
The vibrating alert is powered by your Visor, so there are no extra batteries to worry about. The size of the InnoPak/2V is identical to that of the backup module; it fits flush with the back of the Visor and does not protrude at all.
I have tested the vibrating alert on my desk, and with the Visor in the cradle, and I don’t think there is any worry of this not being noticed. If anything, I almost think it is a little too strong. The first time it went off, I thought it was going to shake apart! While the Visor is in the cradle, when the alarm goes off the cradle takes a little ‘walk’ around. It may not be so useful in a purse or briefcase, but in a pocket or on a belt, you will not miss this.
In the IP Conf application, you can set how long you want it to vibrate for, you can set it from 3, 5, 10, 15, or 30 seconds. There is also a little Speaker Icon on the IP Conf screen, which tells you if you are currently set to audible or silent alert (a line appears through the speaker to indicate it is silent). At the risk of being picky, this Icon only shows the state of things when IP Conf is first run. The Icon won’t change while IP Conf is running, so it won’t reflect the change of state if you have just done it. You would have to close then reopen IP Conf to see the changed Icon. This probably won’t be a problem to most, but it did confuse me at the very beginning.
A single 2-sided page of instructions was included, one side explained the use of the IP Test and IP Conf programs, insertion and removal of the module, etc. The other side explained use of the File Mover application. For information on the File Mover app, please see below. I found that all three applications were intuitive enough that I didn’t really need the instructions — though without them I wouldn’t have found the shortcut tap for IP Conf.
I’ve used the InnoPak/2V for several days now, and I have not noticed any ill-affects that the motor has on the batteries of the Visor. I’ve had all of my alarms set for vibrating, configured it for 5-second duration vibrating. In Datebook+, I have set it to alarm three times in a row, which means that each alarm results in 15 seconds of vibration. I’ve made sure to have 4 or 5 alarm events each day. It has run pretty smoothly on the whole. I’ve tested it with the regular Datebook and the Datebook+ alarms, both worked fine. It should work fine with all alarm events.
Although there is no need to install any software from disk or CD, a CD was included in the package. It contained hundreds and hundreds of shareware and freeware files from PalmGear HQ, and a nice interface for browsing and searching the archives. I was pleasantly surprised by this ‘bonus’.
The only thing about the operation which I think could be improved, is that if you have set it for vibrating alerts, then remove the InnoPak/2V, it reverts to audible alarms. In itself, this is not a problem, in fact this is how it is supposed to work and is preferable. However, when you reinsert the module, it does not switch back to vibrating by itself, you have to remember to manually enable the silent alarms again. I guess it saves a few bytes or so of memory in your Preferences file, but I have so far never remembered to enable the silent alert when putting the module back in. It’s always later on, (after the first beeping alarm) that I remember to do that. If you never (or seldom) remove the InnoPak/2V, then this may not be an issue for you. But I use the Handspring Backup module every night, so it’s something I’d prefer to see ‘fixed’.
The only real problem I have encountered, is that once in a while when I insert the InnoPak/2V, the motor starts up on it’s own, and won’t stop. Turning the Visor off won’t even stop it. To stop it, I have to run the IP Test application, and click the ‘Stop’ button. I have tried to figure out what causes this, by trying inserting it with the Visor on, with the Visor off, removing the module while it was set to Silent alarms, etc., without success. It is possible that when the module is initialized after insertion, that the signal to make the motor go sometimes ends up ‘on’ during the reset (See below). However, this does not happen too frequently. Maybe one insertion in ten or fifteen. As the three applications are on the Flash memory chip, Innogear can release an upgrade or bug-fix to the software as required.
All in all, I think this Springboard was worth the $44.95 (US), considering you get not only the silent vibrating alert, but the 2MB Flash memory as well.
I am looking forward to the release of Innogear’s ‘SixPak Combo’ module, their website claims it will include: a land-line modem, a cellular modem, a voice-recorder, a memory upgrade, a vibrating alert, and a flashing LED alert; all within the same size package as the Innopak/2V. If it’s reasonably priced, then I’ll be picking one up, and you will find the review and inside pics here!
InnoPak/2V’s Insides
* R1 was originally a 0 Ohm chip resistor. I felt like the motor was running too fast; I didn’t like how strongly it was shaking the Visor, so I have replaced it with a regular 10 ohm 1/4 watt resistor. I should point out that if you solder and de-solder things to the teeny solder-pads they make for surface mount components, you will eventually cook the solder pads right off the circuit board, and then have to get rather creative as to how to save your Springboard. R1 connects the positive lead of the motor, to VCC (springboard pins 17 & 51). The motor runs at the 3v supplied by the Visor, Q1 (just below & right of the motor) is an NPN transistor, which controls the motor’s connection to ground.
** U3 is a Programmable Logic Device. It is CMOS programmable, and electronically erasable. It is in control of the motor. A signal from pin 16 goes through R5 (470 ohms) to Q1. I have confirmed that this device acts as the motor controller. CS1 (chip select 1) goes to this IC, while CS0 goes to the memory chip. From what I can tell, when CS1 and WE (write enable) both go low, the motor is triggered (though this is only a guess, from poking around at the control lines while the card is in the Visor). It is possible that the problem I’ve encountered, with the motor starting up during module insertion, is due to the initialization of the module inadvertently dropping these two signals low.
R2 (0 ohm jumper), R3 (empty), and R4 (empty) are jumpers for the memory chip. By tracing the circuits, I have confirmed that R2 and R4 control address line A20: R2 sends A20 to pin 10 of the memory chip, and R4 sends A20 to pin 15 of the memory chip. R3, when in place, sends address pin A22 to pin 10 of the memory chip. I don’t know too much about these chips, but here’s what I have deduced: As it stands, A20 is tied to pin 10 (R2 in place, R3 & R4 empty) for the 2MB flash chip. If you remove R2, and jumper R4 and R3, this reconfigures the card to use a different flash chip (perhaps an 8MB one?). Again, this is just my guessing. I need to learn more about flash chips before I can be more certain.
*** I added this LED. It’s rated for 3 volts, in a T1 package. It lights when the motor is triggered. It’s presence does not affect the strength of the motor at all.
Other than my LED, and changing the value of R1 to control the strength of the motor, there aren’t really any mod opportunities. U3 might have some possibilities, the spec sheets for that part were interesting, and it is possibly being under-utilized as simply an addressable motor-controller.
Software-wise, if I can figure out exactly what software function activates and deactivates the motor, then maybe the vibrating action could be incorporated into home-made programs.
Handspring’s Backup Module
This module is made by Handspring. I love it. I’ve got about 2MB of stuff on my Visor, and it takes about a minute or two, to fully back it up. It takes about that long to do a full restore as well. In my opinion, if you own a Visor you should own one of these modules. If your Visor is lost or stolen, get a new one and do a restore, and it’s like nothing happened. Likewise, if you take your Visor apart on a regular basis, this is a huge time-saver. No reinstalling applications through hot-sync, no concerns about data files that maybe aren’t backed up during a sync or have no conduit… about the only thing that isn’t saved on this module, is the time and date. It makes a ‘mirror’ of Visor’s RAM. For a thorough review, please refer to the Gadgeteer’s web reviews.
About the only negative thing I can say about this module, is that from time to time when I try to back up my Visor, I get a message that the Backup Failed. Since this message appears in exactly the same place and font as the Backup Complete message, and there is no beep or warning or message box, if you are not looking closely you might not notice this message. And if you later on needed the backup, you would not be a happy camper. This has not happened too often, maybe one time in ten, and there is never an explanation as to why the Backup Failed. I think though that when the Backup Fails, there should be a little more fanfare or a beep or some kind of attention-getting message, so you will know to try it again.
Aside from that one complaint, I’m all for this module. After the price of your Visor, this will be the best $39.95 (US) that you can spend.
Backup Module’s Insides
As you can see, there are a minimum of components here. U2 is a 64KB memory chip which contains the Backup program. The standard Info screen lists 12k free of 63K, with the Backup application taking 52K.
I am not familiar enough with the part number on this chip (MR1MX16HDSB001) to know if this ROM is erasable or not. I have a feeling though that the MR stands for masked ROM, which means that any upgrades will be software patches that go into the Visor’s memory instead of the module’s.
The 8MB Flash chip does not appear to be directly available to the Visor at all. The OS reports Card 1 is a Backup Module v256, with a Romsize of 65276 and Free RAM of 0.
I’m not too sure what the missing U1 is supposed to be for. I initially thought it might be for a different ‘footprint’ of flash chip, but now I am not so sure. By tracing the pins to the module connector, I’ve found out that it’s not a U1 vs U3 choice, but a U1 vs U2 decision. Chip-select 0 is shared by U1 and U2, while Chip-select 1 makes it’s way to U3, by way of the IC package U4. Perhaps before going to the Masked ROM chip at U2, Handspring may have initially prototyped this module with a Flash chip at U1 to facilitate debugging. If that’s the case, then perhaps by soldering an appropriate Flash chip at U1, and desoldering U2’s VCC and CS pins (23 & 12 respectively), you could get both Backup functionality and have some Flash memory to play with. Though this is a long shot, and you’d need to copy the Backup app out of ROM before you disabled it. Bottom line is, though, I wouldn’t even think of trying to do ‘mods’ with this module. The ability to back up your entire Visor’s contents with one tap, and restore it all with one tap, is way too important and cool, than anything I could think of.
Handspring’s 8MB Flash Module
This module is also made by Handspring. It is basically for those who have so many applications that they’ve run out of space on their Visor. It can also be used in lieu of the Backup Module to save data as well as applications, but you have to move them over one by one, rather than a one-touch backup. The module comes with only one application pre-loaded on it, called File Mover. This application is very straight-forward, and easy to use. When the module is inserted, File Mover automatically appears in your Visor’s Launcher. You can then use it to move, copy, or delete Applications and Data to and from the module / Visor memory. The File Mover app is stored within the same Flash memory, but in a protected area so the user can’t delete, move, or copy it. However, it can be updated if newer versions come out.
In terms of ease-of-use, this module ranks very well. Like Handspring’s Backup module, this is what Plug and Play is all about. Insert the module, and it works. The File Mover app, and any applications you have stored on it, automatically appear in the Launcher and can be run like any other application. Remove the module, and the applications on it automatically disappear from your Launcher.
If you have large applications that use a lot of memory, you can move them to the Flash module and free up Visor memory. You can also move large data files to the module, but because of the nature of Flash memory, the Visor cannot edit data files while they are on the module. The Visor views this memory as ROM rather than RAM, and if an application tries to edit a data file which is on the Flash module, you will get a fatal error message. The File Mover application warns you when you attempt to move a data file to the module; it suggests you Copy rather than Move the file. However, it will allow you to move the file if you insist.
For data files which are not edited (or at least, not edited in normal use), you should be able to get by with the data file on the module. I tested this by moving a couple large Doc files onto the Flash module, then running TealDoc by TealPoint. TealDoc recognized the Doc files as though they were still in the Visor memory, indeed they were still in the appropriate category within TealDoc. I was able to load them and view them without difficulty. I also tried this with a game program called ZIP - a game engine for those old text-based games like Zork that we played before computers had graphics. The engine is a .prc file, and the games are .pdb files. I moved a couple game files onto the module, and then confirmed that I was able to run them.
In my opinion, the ability to put large Doc files or other non-editable data files on the Flash module makes this module worthwhile. I’m sure that there are people out there who have used up their Visor’s 8MB of RAM with huge applications, and are looking for the extra 8MB so they can put another 200 applications into their Visor… but I think it much more likely that someone might want to fill the module up with, say, a few dozen e-books and a Doc reader for instance.
To be honest, I did not need to buy this module, I’ve still got 5.5 MB free in my Visor. Another feature of this module, that Handspring mentions on their website, is that it may be used for prototyping new Springboard applications. Handspring’s SDK’s are freely available, and with their available software, you can completely erase the module (including the File Mover app) and then fill it with your own programs. As such, you can use this module to design and test your own custom Springboard applications.
At $80 US, I think this module is a little bit pricey for what it does. However, what it does, it does very well. I would rate this as another ‘winner’ for Handspring. If you’re just looking to backup your Visor, go for the Backup module, at half the price. If you’re looking for a way to carry around an extra 8 MB of apps and data, and/or backup a handful of individual files, then this is a good buy for you.
8MB Flash Module’s Insides
I was surprised to find this module used four 2MB Flash chips instead of just one 8MB flash chip. I’m sure there is a good reason for this, and I’d love to know what it is. With one 8MB chip, this module could well have looked like the Golf module below. Instead, the module has to include address decoding, to let the Visor access the four chips as though they were one. The smaller IC (labeled Decoder Chip) performs this function. It monitors the upper address bits, and depending on which bits are active, it directs the Chip Select signal to the appropriate memory chip. This module only uses Chip Select 0; CS1 is not even connected to anything.
What could you do with this module? Well the first thing that comes to mind, is doubling the size. If you were very, very desperate for a 16MB Flash module, you could get 4 more of those memory chips (Toshiba TC58FVB160FT-10), plus one more of those decoder chips (74AC139), piggy-back all the new chips onto the existing ones, except leaving the chip-select lines of the memory chips unconnected, and leaving the corresponding chip-select pins of the decoder chip unconnected, then using bits of wire, solder the chip-select lines of the new memory chips to the corresponding pins of the decoder chip, then solder the chip-select input of the decoder chip to the unused CS1 of the Springboard connector. Then reformat the module, and it ought to read as 16MB. Of course, this ought only be done by someone who knows exactly what they are doing with these delicate memory-chip components, and so far, that rules me out. Plus, I just don’t need a 16MB module. I don’t even need the 8MB module.
Tiger Woods PGA Golf Game
Ok, I’m not a golfer, I’m not a computer-golfer, and I don’t even watch golf on television. I bought this module because I wanted a Springboard to rip open and mess with, and it was the cheapest one available. (Once I found out how easy they were to open, I proceeded to open the other two as well of course.)
I don’t really want to ‘review’ the game itself in much depth, because of my disinterest in the sport, but I will give a brief overview.
When you insert the module, it automatically runs the game. You can click the applications button to exit of course, and if you do, then the game icon appears in your launcher. The start-up screens of the game take a while to come and go, and I find it a bit annoying to have to see 6 screens of advertising and legalese every time I insert (or just run) the game. It takes 10 or 12 seconds for all of this to flash by, each and every time this game is run.
You can play a couple different kinds of games, from a quick round, to a full tournament against up to 3 other human or computer players. There are three courses to choose from. The interfaces are pretty straight-forward, though it comes with a fairly comprehensive manual as well.
The game also installs two very small files on your Visor, TIGRsave and TIGRxtra. They are just 1K each, and keep track of your name and score I believe (though I am not sure). If you delete them after removing the Springboard, they will reappear when you reinsert it.
I’ve played the game 3 or 4 times, it’s Ok, but as I have indicated, it is not really my sport. A golfer though might find it more useful.
The bottom line for me was, I ought to have saved my $29.95 (US). The game does nothing for me, and there was nothing inside of interest (see below). However, if you like computer golf games you may enjoy this module.
Tiger Woods Golf Game Insides
As far as circuit boards go, this has to be the most boring one I have ever laid eyes on.
As you can see, there is just one memory chip and one capacitor. The memory’s part number is MR1MX16HDBTW02. The OS reports it as Card 1: Tiger Woods V1.1 v257, with a Romsize of 511740 and Free Ram of 0. The standard Info screen reports Free Memory 64K of 498K and a single file, Tiger at 435K.
Basically, it’s a single 512K ROM chip wired to the address and data lines to the Visor. Not too much that’s doable here as far as modifications, I’m afraid. Though if I do want to try building my own Springboard at some point, I can remove the ROM chip, and use this board as the basis for some prototyping. It will give me access to the IO lines and power and interrupts and so on.
So you want to pull apart a Springboard?
As usual, when opening up these things, you kiss your warranty goodbye. Further, when prying it open, if you are careless or using the wrong tool (say, an axe) you could damage the module inside. Though for the ones I have displayed above, I must say there is not much you can break on them. Your worst case would be scratching the board and cutting traces, or cracking the board and breaking traces. Either way, you toast the board. I am not liable or responsible in any way for damage you do to your Springboard or Visor if you try prying them apart or messing around with their insides.
Of the ones I have worked on so far, they have either been glued or they have been ‘welded’. All of them have been the smallest kind, not the larger modem, MP3, or GPS style Springboards. Just the ones that fit flush with the Visor. Those larger ones will likely require a different method. In the cases I have done, the plastic top has been fixed to the plastic bottom in a ‘permanent’ fashion, while the circuit board itself is not fixed at all, but held in place by friction and by a tongue-and-groove fitting at the 68-pin connector.
Using either a very small slot screwdriver, or (be careful!!!) a small hobby knife (like the OLFA Touch-knife), probe along the visible seam, to find a weak spot. Once you have found it, press the knife / screwdriver blade inwards, get a bit in, and then twist gently, to try to pry the thing open. If you are lucky, the glue / weld will start to give, and you can insert your tool a little further, and repeat. Start following the seam all the way around, go one direction then the other, till you have opened all three sides. The module will then simply come apart.
If you are not so lucky, the glue or weld will be stronger than the plastic, and you will end up with unsightly marks along the seam where you have tried prying it open. If these marks protrude, you can shave them off with a hobby knife, but they’re tough to get rid of. One of my module cases ended up this way, and I even lost a corner of the plastic where the plastic tore rather than the glue releasing. (That’s now the golf module of course.)
Whether using a screwdriver or a hobby knife, do be careful not to go too far into the module with it. As mentioned above, you could scratch the circuit board, or possibly even ‘bump’ a small component. Those chip resistors and chip capacitors can be brittle and can crack or break if hit right. Or a weak solder-joint could give way and set the tiny part free.
Putting them back together, is pretty easy. Just set the circuit board in it’s place, stick the top on, and you’re done. Ok, it won’t stay put together, unless you use some glue. It’s a bit of a quandary now, if you use glue you’ll have to go through all this again next time you want in. If you use nothing, then the modules will keep falling apart. I opted to leave them all apart. When you put them together and put them into the Visor, they cannot fall apart as the rails of the Visor holds the module firmly in place. Just don’t loose any bits and pieces if you leave them strewn about your desk. And you share your place with a mischievous cat.
Doll Cards?
Here’s a little curiosity that you may not have noticed. Handspring’s 8MB Flash Module’s circuit board is labeled as a ‘Ken Board’, and the Tiger Woods module’s board is labled as a ‘Barbie ROM Card’. Further, the OS identifies the InnoPak/2V card as ‘IG_Barbie_1′. I guess naming conventions have to come from somewhere, but I wonder what inspired then Handspring folk to go with Ken and Barbie.
What NOT to do to your Springboard module:
This is the Tiger Woods golf module, after I desoldered and removed the ROM chip. I did a terrible job with it, I damaged 4 or 5 traces on the board. This is what you can expect, when trying to remove a surface-mount IC with 40+ pins, with a $10 soldering pencil and an X-acto knife. Needless to say, this module is now destroyed, as far as playing golf. However, it may see life again as a home-brew board doing something interesting.