Posts Tagged ‘gen6’

Easy serial debug, now also for Archos gen6 (A5/A7 IMT)

Thursday, July 22nd, 2010

This is a follow-up to my previous posting: Debugging Archos devices just got a lot easier.

It was a bit of work as g_serial has changed a lot inbetween 2.6.22 and 2.6.27. This version only supports one serial device. I’ve decided to bind an cat /proc/kmsg to it, so if you want to bind an getty to it you have to kill the cat first I guess.

I’ve made the initramfs with the slightly modified init script and added modules available. Bitbake recipes should appear in svn in the near future. Need to clean up my tree first. :-(

Thomas, your friendly neighborhood ArchDruid

PS: On an slightly related note. I hope SFR decides soon to open their branded A5 3G+ to an SDE, so that owners of those devices will be able to enjoy this too. They were selling the device for a couple of days for only 50€ free of contract, certainly a very nice offer.

PPS: use with an gen6 kernel only. Like e.g. this one

Debugging Archos devices just got a lot easier.

Monday, July 12th, 2010

UPDATE:

This guide is outdated, please do not use it anymore! There is a new and updated procedure that is easy to follow and integrates g_serial debugging. The files linked to in this guide will be no longer available.


I’ve been talking about this idea for a while now, but today I finally had the right mood to work on it and I think I’ve found a sufficiently flexible solution for now.

I’m loading the kernel modules (musb_hdrc and g_serial) in the initramfs. Fortunately there was enough space left for that.

I’ve created 3 separate serial interfaces using g_serial.

  1. /dev/ttyGS0 – unused (root shell on Archos Android firmware)
  2. /dev/ttyGS1 – unused
  3. /dev/ttyGS2 – kernel messages. this is simply ‘cat /proc/kmsg’

You can now attach terminals or logs to this in your images. Usually by editing /etc/inittab and adding a line like:

s2:235:respawn:/sbin/mingetty --autologin root ttyGS0

If you need to disable this you can just kill the ‘cat’ process and if running stop the getty’s. After doing that you can remove the g_serial and then the musb_hdrc module. You can then e.g. reload musb_hdrc to have it act as a host controller again.

The important changes are in the initramfs. The zImage is only needed if you want the root shell for Android. Get the files here.

Enjoy your easy debugging! No need for serial dongles anymore!

Cheers

Thomas, your friendly neighborhood ArchDruid
PS: As a bonus this zImage will boot Archos 2.0.x firmwares. There will be some problems with transparencies though. We’re going to fix that in the long run though.

PPS: If there is demand I can generate a set for gen6 too.

Proof of Concept:: Win3.1 running on Gen6 w/Angstrom + DosBox

Sunday, May 16th, 2010

After reading the post on a Gen7 booting win3.1, I thought I would give it a shot on a Gen6.

DosBox has serious RAM implications on Gen6 hardware, so I opted to install the windows files from my PC and transfer them over to the Archos 5 IMT.

The Result?

The process was very similar to the post listed below:

I installed DosBox on my PC.  copied the Win3.1 files from the ISO, ran DosBox and mounted the folder where the Win3.1 files reside.  I then created another folder called Windows, and mounted that to a separate drive letter in DosBox.  I then ran the setup, and went through the installation process, installing the OS to the “Windows” directory I created/mounted.

Once finished, I transferred the new “Windows” directory over to my unit,, booted up angstrom and ran DosBox.

I then mounted the “Windows” directory to “C:”, then cd’d into it and ran “win.com”.

Success.  :)

Cheers

~Spz0

A demo Image using the Enlightenment WM

Wednesday, May 12th, 2010

Hello all.

I’ve been wanting to make angstrom more user friendly for some time, so I decided to start working on an e17 Illume build.  There were a bunch things I didn’t like about the current gpe build — the xkbd being too small, midori web browser being too chunky, the lack of overall user friendliness of the UI, amongst other small issues mostly revolving around functionality of Angstrom.

This image that I’ve compiled addresses these issues as well as others such as:

  • A more user friendly interface (Illume)
  • Increased size of buttons and fonts (Scaling)
  • Removal of misc. programs (broken programs and programs incompatible with e17)
  • An increased file system of 1Gb
  • Selection of 3 web browsers – Fennec, Woosh and Dillo (warning: fennec is still a WIP and will crash when loading larger pages due to RAM restrictions on Gen6 devices)
  • OptimSMS2 keyboard layout
  • Quasar Media Player (Mplayer frontend)
  • ePDFviewer
  • Abiword Word Processor
  • Numpty Physics (Neat little physics game)

This image is base on Kevin’s build of the revision 199 of openAOS Ångström overlay. All additional packages have been installed from the regular Ångström package feeds with the exception of Dillo, Woosh, NumptyPhysics and Quasar (which I modified together with some help from Thomas, dm8tbr [thanks m8!!]) and for which sources and bitbake recipe are available here.

Some screenshots (desktop will look different on the downloaded image due to additional software installation):

Main Desktop

Archos gen6 running e17 - main view

Archos gen6 running e17 - main view

Illumes “Top-Shelf” (note: Vkeyboard button is located in the top-right corner “qwerty“)

OptimSMS2 Keyboard (Switch between kbd layouts by hitting “ABC” [above letter"P"])

Archos gen6 running e17 - screen keyboard

Archos gen6 running e17 - OptimSMS2 on-screen keyboard

Quasar UI

Archos gen6 running e17 - running Quasar
Archos gen6 running e17 – running Quasar

OptimSMS keyboard still needs a bit more work, it’s a bit too large right now, but still very usable.  I may get around to finding a way to reduce the size of the container.  Look for that update.  I also kept the “transparent keyboard” active for use, and I have my custom xkbd layout defaulted (mimics OptimSMS2 layout).

There is also a known issue with the Battery Meter being broken.  Hopefully we can fix that soon.  If anyone wants to try, go right ahead.  :)

This image should need minimal adjusting, as we have worked to import all my custom e17′s settings into your home.img, so you should not have to go through the initialization process.  However, if you with to do so, goto “Settings->Settings->Profiles” and select the “Default” profile to run through the initialization process.  I would also suggest increasing the Terminal font size (click the “Look and Feel” icon, goto the “Terminal” tab and increase to the desired font size).  You will have to restart in order for those changes to take effect.

Grab your copy of the E17 Image HERE.**

**updated to beta2 build as described HERE

[ If you wish to run this along side your current build, rename image to "illume.img" and make the appropriate entry in "menu.lst" Otherwise just overwrite your "rootfs.img" and your good to go.]

~Cheers

Spz0.

Just for fun: openAOS boots Maemo/Mer oh and Meego too, ’cause we can!

Friday, May 7th, 2010

This is more of an “oh-look-shiny” thing right now.

I’d like to EMPHASIZE this: Currently we do not support Mer on Archos hardware! This is just an proof of concept!

Gaap asked me on IRC today how to try Maemo/Mer on his A5IT. – Turns out it was very easy.

  1. You take: Mer build for SmartQ5 (Touchbook might work even better I guess)
  2. Throw that into an 500M+ ext3 image.
  3. For good measure throw in some parts of the original Archos SDE images.
  4. Modify menu.lst (the image needs /sbin/init)
  5. profit!

Here are two short videos by Ian58 and spz0:

To get this far you need to go through the first boot assistant. Notice that the screen calibration will be totally off and you need to aim a bit to the side. When you manage to hit an input field the virtual keyboard will show up.

Update: If you like watching paint dry you’ll also like this one: Meego code drop 20100331 repackaged for Archos

Please note, that this is just an proof of concept and nowhere near seriously usable. It just happens to work (a bit). But if someone wants to step up and properly port that or later Meego to Archos hardware. We’re very much open to it. Just contact us for hints and some help!