braino: What is mean by that is the original firmware as in not hacked yet. There is a file that is run on the miniSD called z2script.sh if it finds it at bootup. The debian, side-track, z2sid, ubuntu, etc distributions don't check for this.
Zipitwireless does encourage hacking, and they have disclosed quite a bit of information about the hardware.
After a full charge the battery on mine lasted about 45 minutes. Also, with the clamshell closed, I can squeeze it and hear a lot of buttons being pushed under the lid.
martin: the battery life seems a bit short. I would leave it plugged in over night and see what kind of battery life you have in the morning.
I get quite a bit more time from mine running ubuntu than I did with the older rootnexus debian install because it has power management to turn down that anoyingly bright screen, and to turn off all keyboard and screen when it is closed. The stock firmware has power management too, so you should be seing quite a bit more life than 45 minutes.
The squeze thing is normal. It apears the soft keys double as bumpers:^)
There is not a standard hacked image, but there are several only a couple of different common kernel flash images and several rootfs images. I like mozzwalds ubuntu, because of the stickey shift and alt keys as well as power management, and most of all, that is the one people have gotten USB to work on. I can send you an image of what I have, but I haven't gotten USB to work yet, so no externl prop connection yet. PM me if you want it. Anybody else is welcome also, but I don't want to put the links here in the forum because they will be temporary.
For $10 each I could not resist, so I just ordered three Z2A units. Might as well get some spares, it's obviously a fire-sale price so I'm sure they'll be gone quickly.
My intended application is just as an always-on internet connection for some data acquisition hardware that has only a (3.3V level) serial output. The Z2A would grab data via its (hacked-in) serial port and then send it on to a remote web server, via 802.11b through my home wifi. That way I avoid the power drain of having my main PC on all the time to do this menial task. I think that soldering on the serial Rx,Tx,Gnd wires is all the modifications I need to the Z2A hardware, correct? Then load in a fresh Linux kernel and write some hopefully simple script for transferring serial data to wifi.
Question: anyone know if there is any problem with leaving the unit on with external power supply connected all the time? Would it be better (or possible) to run with the internal battery removed?
I've had my two Z2A's for a little more than a week. I have not yet flashed a new Linux Kernel -- instead, I am using one of the several versions of the Improved Z2 Shell (IZ2S) that runs from the Mini-SD card directory on the stock firmware.
I just finished a new version of the WiFi script setup-wifi.sh, which configures the wireless for use. My version now caches all the "configured" network information, so you only have to enter it once (ESSID, passcode and encryption type) for any given ESSID, and it allows you to select which network to connect to (or enter the data for a new network).
As far as the serial mod goes, it only includes TX and RX lines, but no DTR/DSR or RTS/CTS line, so it cannot be used to upload programs to the Propeller board(s) with auto-reset. However, if you do flash the appropriate new Linux kernel, you can use the device in USB 1.1 host mode, so it should be able to talk to any of the USB compatible boards or the PropPlug.
"The PXA27x processor provides 121 highly-multiplexed general-purpose I/O (GPIO) pins..." (Section 23.1, p. 1043)
BUT... in Table 461 (p. 1047...1051) I see that pins 2 and 5-8 are not GPIO, they show footnote [5] which says " 5. This signal is dedicated to the function shown and is not available as a GPIO."
I notice a short battery time at first, the unit showed full charge, but ran down quickly. This happened a couple times the first day, but I left it charging overnight and is seems OK now, although I did not record times.
Have you tried multiple cards? I have not seen that problem yet on 5 zipits that I have unboxxed here.
As for battery life, it helps to have an os that turns off the leds when not in use, and turn them down when in use to keep you from seeing spots and warming up your fingers. Have you noticed that when the LEDs are on high, the keyboard is noticably warm?
I use z2sid and ubunto which have some commands like "backlight-medium" and "backlight-low".
I have been looking for a single GPIO for reset too. Unfortunately, I have not located one yet. Perhaps I may have to steal one used for another purpose. I suspect that not all unused GPIOs will be accessible - its a BGA chip and perhaps not all pins are connected. Unfortunately, little time to continue this.
I have not yet flashed a new Linux Kernel -- instead, I am using one of the several versions of the Improved Z2 Shell (IZ2S) that runs from the Mini-SD card directory on the stock firmware.
This is a good suggestion. Its handy to be abl to return to the stock firmware by removing the sd card when I have to check that I didn't trash something. I'm using the most recent one,
This one looks like is can save network information.
It worked fine on the 1G and 2G cards, but did not initially boot from the 4G card. But it detected the card, and played mp3 files. Out of the blue, after last power cycle it booted from the sd.
Small progress. Mozzwald's ubuntu, U-boot and a cheap mini USB cable soldered to the main board internally. When booting up, the kernel recognizes any FT232 chip connected. It shows up as /dev/ttyUSBx. But the Zipit must be plugged into the charger to get 5v.
Here is a pic of my proposed serial mod. It is a 4pin socket arranged in the PropPlug format. See the lower right of the ZipIt2 pcb for the socket (not wired). I propose to glue it to the pcb with superglue. Pins from left to right GND, -Reset, TXD, RXD. (Note I have not yet verified a close ground point - the reset switch should have a ground connection and I think that is the top left, but with my meter on the high seas and me on dry land, I have not verified it.)
By using a pin socket with long pins we can then extend the socket out to connect to a prop pcb or use a cable with pins one end and a socket the other to connect to a prop pcb. Just need to find that elusive GPIO pin for resetting the prop.
It will also work with a cable to a true PropPlug (i.e. FTDI chip to USB) to connect the ZipIt to a pc.
Professor, the version you are using is version 2.04 -- I have version 2.05 Beta, but I think I may go back to 2.04, as the beta image does not have as many programs: for example, 2.04 has the nano editor, but 2.05 does not.
Surprisingly, I've been able to compile Catalina, install Homespun, compile spin programs and upload to a Prop on this little thing, all via SSH. No hacking, no patches. Apart from me not really knowing what I was doing it was pretty smooth. Really amazing considering it's cost.
Small progress. Mozzwald's ubuntu, U-boot and a cheap mini USB cable soldered to the main board internally. When booting up, the kernel recognizes any FT232 chip connected. It shows up as /dev/ttyUSBx. But the Zipit must be plugged into the charger to get 5v.
I just cut the end off a mini USB cable and soldered it to the expansion port (pins 13&14 counting from right to left) inside the Zipit. I'm using the ASC's on board FT232 chip to do everything else. I should have said that, sorry. However, it shouldn't be any different for a Prop-Plug/Clip or any other Prop platform that has USB. The limitation is you have to be plugged into the charger to get 5v.
The general steps I used:
Flashed U-Boot to the Zipit
Used the Debian live CD to partition, format and write to an SD card the "ubuntu for uboot" root file system. Everything from here on was done on the Zipit.
Booted the Zipit with that SD card and used apt-get for about 3 hours to update everything and install some other apps I like to have. (Heater's suggestion to open your wifi long enough to do that worked great here)
Once WPA was set up on the Zipit and the wifi closed down again I used SSH from my PC for the remainder.
The FT232 drivers are built into the kernel, so no installation or configuration necessary there. It appears as /dev/ttyUSB0 during boot.
Unpacked the catalina source into /usr/local/lib/catalina and used build_all in the source/catalina dir.
Catalina compiled and installed with no errors. (I had to 'apt-get install mono' to run Homespun.)
To load a prop you use 'payload -p 17 -t 1000 yourfile'. The -t timeout needs to be 700(ms) or greater on the Zipit otherwise I get "no response" errors.
All this information and software is from mozzwald.com.
There's about 8,000 more steps I took that were wrong or unnecessary of course, and I may have left out a detail or two. I'm willing to help anyone who wants to try it. You really must be proficient with Linux to attempt this. Knowing things like permissions and how to use sudu, resolving dependencies, etc.
The only debian install that is u-boot compatible AFAIK, is z2sidX for uboot here: http://mozzwald.com/node/92. U-boot is needed in order to do usb.
Unfortunately, when I tried it wouldn't boot up all the way...it got hung on the usb stuff.
I am waiting for another release, as they are coming pretty often now.
I might be interested, assuming I can work out how to get a USB-capable system. I have not tried the U-boot kernel yet. Is a USB system any more difficult or flakey to run as compared with what I've got now, which is 2.6.29 kernel and z2sid userland ? I just followed the instructions at http://hostwork.com/users/matt/zipitz2/
Just out of curiosity, could you attach a USB hub and get several FT232 devices hanging off it at once?
If you really wanted to run from internal battery, you could make a 3V -> 5V boost converter circuit. Maybe better to just use external +5V though, either wallwart or larger battery + regulator.
Martin: I don't see the point in an FTDI chip and reset circuit in the connector housing. Provided we can find a spare GPIO pin we can just use the serial and gpio pin for reset to download to the prop. I look at every link I find, so I will look at JBeale's links, to see if I can find a suitable GPIO pin.
A more useful pcb in the connector would be a miniUSB connector.
Comments
Zipitwireless does encourage hacking, and they have disclosed quite a bit of information about the hardware.
I get quite a bit more time from mine running ubuntu than I did with the older rootnexus debian install because it has power management to turn down that anoyingly bright screen, and to turn off all keyboard and screen when it is closed. The stock firmware has power management too, so you should be seing quite a bit more life than 45 minutes.
The squeze thing is normal. It apears the soft keys double as bumpers:^)
Is there a standard "hacked" image? Most of the links talk about setting up a linux PC to get started, I'd like to just get an image and flash it.
Once it is hacked to linux, what is the current popular software for accessing the prop?
My intended application is just as an always-on internet connection for some data acquisition hardware that has only a (3.3V level) serial output. The Z2A would grab data via its (hacked-in) serial port and then send it on to a remote web server, via 802.11b through my home wifi. That way I avoid the power drain of having my main PC on all the time to do this menial task. I think that soldering on the serial Rx,Tx,Gnd wires is all the modifications I need to the Z2A hardware, correct? Then load in a fresh Linux kernel and write some hopefully simple script for transferring serial data to wifi.
Question: anyone know if there is any problem with leaving the unit on with external power supply connected all the time? Would it be better (or possible) to run with the internal battery removed?
I just finished a new version of the WiFi script setup-wifi.sh, which configures the wireless for use. My version now caches all the "configured" network information, so you only have to enter it once (ESSID, passcode and encryption type) for any given ESSID, and it allows you to select which network to connect to (or enter the data for a new network).
As far as the serial mod goes, it only includes TX and RX lines, but no DTR/DSR or RTS/CTS line, so it cannot be used to upload programs to the Propeller board(s) with auto-reset. However, if you do flash the appropriate new Linux kernel, you can use the device in USB 1.1 host mode, so it should be able to talk to any of the USB compatible boards or the PropPlug.
http://sourceforge.net/apps/mediawiki/openzipit/index.php?title=GPIO_List_WIP
Although I think Marvell is cheating a bit on the numbering of GPIO pins. Reading the manual
http://www.marvell.com/products/processors/applications/pxa_family/pxa_27x_dev_man.pdf
"The PXA27x processor provides 121 highly-multiplexed general-purpose I/O (GPIO) pins..." (Section 23.1, p. 1043)
BUT... in Table 461 (p. 1047...1051) I see that pins 2 and 5-8 are not GPIO, they show footnote [5] which says " 5. This signal is dedicated to the function shown and is not available as a GPIO."
When the card is inserted, it clicks, pops back out about halfway, and does not appear to make contact. This is observed on two units.
EDIT - Turns out to have been operator error. If you observe the conditions above, it means the card is upside down. Doh!
As for battery life, it helps to have an os that turns off the leds when not in use, and turn them down when in use to keep you from seeing spots and warming up your fingers. Have you noticed that when the LEDs are on high, the keyboard is noticably warm?
I use z2sid and ubunto which have some commands like "backlight-medium" and "backlight-low".
http://rayhaque.blogspot.com/2010/02/version-204-iz2s-release.html
This one looks like is can save network information.
It worked fine on the 1G and 2G cards, but did not initially boot from the 4G card. But it detected the card, and played mp3 files. Out of the blue, after last power cycle it booted from the sd.
Attachment not found.Attachment not found.Attachment not found.
By using a pin socket with long pins we can then extend the socket out to connect to a prop pcb or use a cable with pins one end and a socket the other to connect to a prop pcb. Just need to find that elusive GPIO pin for resetting the prop.
It will also work with a cable to a true PropPlug (i.e. FTDI chip to USB) to connect the ZipIt to a pc.
IZ2Se 2.05Beta here
Fantastic! Is there something you are not telling us?
To download from Zipit to Prop one needs a serial TX and Rx and another line to reset the Prop. I thought we were still missing that last detail.
Otherwise, there are 2 leds - maybe we can reuse one of these until we find a pin - GPIO#10 apparently drives the Red Led 0=on.? Or use the USBIO pin?
That is great! Why didn't you try for the external connection?
Can you give a close up of where you soldered in?
I just cut the end off a mini USB cable and soldered it to the expansion port (pins 13&14 counting from right to left) inside the Zipit. I'm using the ASC's on board FT232 chip to do everything else. I should have said that, sorry. However, it shouldn't be any different for a Prop-Plug/Clip or any other Prop platform that has USB. The limitation is you have to be plugged into the charger to get 5v.
The general steps I used:
To load a prop you use 'payload -p 17 -t 1000 yourfile'. The -t timeout needs to be 700(ms) or greater on the Zipit otherwise I get "no response" errors.
All this information and software is from mozzwald.com.
There's about 8,000 more steps I took that were wrong or unnecessary of course, and I may have left out a detail or two. I'm willing to help anyone who wants to try it. You really must be proficient with Linux to attempt this. Knowing things like permissions and how to use sudu, resolving dependencies, etc.
Attachment not found.
External connection would have been better. If one doesn't mind paying as much or more for the plug than the Zipit.
Attachment not found.Attachment not found.Attachment not found.Attachment not found.
Thank you. That's brilliant. I hope it works with the Debian I am using on my Zipit. Time to dig out the soldering iron...
Unfortunately, when I tried it wouldn't boot up all the way...it got hung on the usb stuff.
I am waiting for another release, as they are coming pretty often now.
http://www.youtube.com/watch?v=AhOK6CJOk4E
http://sourceforge.net/apps/mediawiki/openzipit/index.php?title=GPIO_List_WIP
[01:43] <fanoush> the "Function" column means what is the meaning of the pin set by bootloader
[01:44] <fanoush> it can be changed into different function (0,1,2) anytime by software
so the CIF function can be turned off and basic GPIO turned on
[01:45] <fanoush> so without using camera there are like 12 free GPIOSs on the expansion port
above from http://www.mozzwald.com/irclog/readlog.php?date=2011-1-12&chan=zipit
Zipit expansion port connectors
Hirose ST60X-36S CONN PLUG 36POS R/A CRADLE SMD WITH SHIELD
Hirose ST40X-36S-CV(80) CONN PLUG 36POS SOLDER WITH SHIELD
from Hirose connector catalog: http://www.hirose.co.jp/cataloge_hp/e24100015.pdf
http://parts.digikey.com/1/parts/328595-conn-plug-36pos-solder-pcb-st40x-36s-cv-80.html
Just out of curiosity, could you attach a USB hub and get several FT232 devices hanging off it at once?
If you really wanted to run from internal battery, you could make a 3V -> 5V boost converter circuit. Maybe better to just use external +5V though, either wallwart or larger battery + regulator.
A more useful pcb in the connector would be a miniUSB connector.