Posts Tagged ‘hack’

MeeGo HX on A5IT – looking for help

Monday, July 12th, 2010

I was anxiously waiting for the handset experience to surface. After all I had quickly gotten the MeeGo core image to work on my A5IT (see previous posting Maemo and Meego on A5IT – proof of concept).

Once it was out I managed to get my hands on a kickstart file referencing the correct repositories and set up mic2 (which is a serious pain in the back).

Sadly the resulting image (I had added our kernel modules and some slight modifications) didn’t get the Xorg server up.

After some investigations and tests I added the SGX modules from the 2.0.x Archos firmware but still Xorg fails.

I am now looking for people that also want to try get this working. I suspect some libraries need to be replaced or even recompiled. To make things easier I’ve hacked up an USB-console into the image. So when you attach it to your PC it will show up as a serial device and you can directly use a terminal software to access the root console bound to it.

So if you want to help drop me a line on IRC (see chat link top right corner).

Cheers

Thomas

PS: Due to hardware differences this will work on gen7 only. Gen6 is missing the SGX GPU core.

openAOS brings you: ArchDruid – Android 2.0 for gen7!

Tuesday, May 11th, 2010

We are proud to be the first ones to have a public preview of Android 2.0 (eclair) on 7th generation Archos devices (Archos5IT).

Mind you, this is not an Archos build and none of the multimedia functionality would work right now. It just shows that even with the current 2.6.27.10 Linux kernel the device is able to boot an Android 2.0 user-space and bring up the UI. I’ll repeat this. If Archos releases an Android 2.0 firmware it will be very much different!

empty home screen

home screen

Given the ease with which I was able to modify an existing build of Android 2.0 to run on my device and get rid of most of the error messages – I have to say I have no idea why nobody else has done this yet. But this is kind of symptomatic for the Archos “community”. The loudest to cry out and demand but no one is even able to get their behind up and try it themselves. It took me less than an hour to have the GUI up and running.

locked screen

locked screen

One major downside at the moment is that the touchscreen driver is not cooperating. If someone wants to help and try to make it work – please contact me.

I/InputDevice.ReadPointercalFile: (  956): t.x1=796.0 t.y1=0.0 t.z1=-95501.0t.x2=0.0 t.y2=508.0 t.z2=-116804.0t.s=3830.0  
I/KeyInputQueue(  956): Device added: id=0x10002, name=ADS784x Touchscreen, classes=14                                    
I/KeyInputQueue(  956):   X: unknown values                                                                               
I/KeyInputQueue(  956):   Y: unknown values                                                                               
I/KeyInputQueue(  956):   Pressure: unknown values                                                                        
I/KeyInputQueue(  956):   Size: unknown values                                                                            

If all you want to ask is “Can haz newist Image!?” – shove it, don’t even bother, if there will be updated images you’ll find the information about it on this blog.

Meanwhile you have something nice to look at:

boot animation

boot animation

and you can brag how you were among the “fr!st evar!” to boot Android 2.0 outside of Archos R&D on an Archos5IT.

Disclaimer: If this image makes your Archos bite your dog or eat your cat or otherwise damages the device or causes the Doomsday Machine to activate. – Tough luck, no cookies.
That said nothing bad has happened to my unit yet, but you never know.

That all said, if you still want to try or god forbid even want to help: here’s a bzip’ed image for you. Use something like this for the menu:

Android_2.0|/dev/sda1|/archdruid_0_0_1.img|/init

Ah and the original build is from here (qdroid).

That’d be all for today folks. Check back for a video soon.

Thomas, your friendly openAOS Archdruid

Serial console on gen6 and gen7 using the Archos DVR Station

Wednesday, April 21st, 2010

The serial console is an extremely powerful tool while working on embedded systems on an low level. Rewriting the init process to enable the openAOS Boot-Menu would have been virtually impossible without this.
So, due to some requests for information on how to access the serial console on Archos generation 6 and 7 devices I put together this posting. Thanks also to those who contributed the Pictures to make this post possible!
What will you need?

  • A soldering iron with a fine tip (capable of soldering SMD parts)
  • Some thin, insulated wire
  • A level converter 1,8V ⇄ RS232 (this is very important, more on that later)
  • An Archos DVR station for gen6/7

Once you have everything prepared on a clean surface:

  1. First open the DVR-station. The screws on the back are not important, the ones hidden below the pads on the bottom are.
  2. You should now see something like this:
    Overview of the DVR-station PCB, click for larger version

    Overview of the DVR-station PCB. Click image for larger version

    Notice how some parts are highlighted in red. Those are convenient spots to grab the serial TX, RX signals and an nearby ground pad.

  3. To have an interference free serial interface you will have to sacrifice the IR receiver and transmitter. Or to fit a switch; though this goes beyond the scope of this guide so that design and implementation are left to the discretion of the interested reader.The following picture shows the two resistors that need to be removed while hilighting the appropriate solder pad to attach an wire. To the Right you also can see an easily accessible large ground pad which needs no further preparation.
    Closeup of the DVR-station PCB, with resistors, click for larger version

    Closeup of the DVR-station PCB, with resistors still in place. Click image for larger version

  4. After unsoldering the resistors you can proceed to soldering on the three wires.

    Closeup of the DVR-station PCB, with wires, click for larger version

    Closeup of the DVR-station PCB, with wires soldered on and resistors removed. Click image for larger version

    Notice how the TX and RX wire are soldered to the lower of the two pads where once the SMD resistor was located.

  5. Apply some tape so there is no mechanical stress on the solder joints
  6. Find a way to route the wires outside the case
  7. Please notice that TX and RX is respective to each device, this means you need to wire: TX → RX and RX → TX!
  8. Attach your 1,8V ⇄ RS232 converter to the three wires!I will emphasize this once again:
    This converter is a MUST! If you connect your Device directly to an RS-232 port you are going to cause irreversible damage to it!

    Alternatively you could use one of these USB converters. I heard that you can get away without modifying VCCIO for 1,8V and just leaving it at the 3,3V default.

  9. Congratulations! You can now directly debug your Archos running an custom kernel!

Some further notes on this topic:

  • This does not work with the original Archos firmware!
  • Advanced users can connect an USB-to-serial converter chip that is capable of 1,8V directly to the port. This is not something you can buy off the shelf. Regular converters use RS232 levels → irreversible damage!
  • If you are connecting an cheap USB-to-serial converter to the level converter use a “moderate” baud rate! Cheap converters usually contain an prolific-2303 chip. It works ok for 115k2 but won’t work reliable at 1M. I can recommend FTDI converters, they work just fine at 1M.
  • A similar modification should be possible using the HDMI-Dock as I’ve been told it has two docking connectors (TX is on the left, RX on the right).

I will add some more notes here later on.

And once again. NEVER connect RS232 directly to the bare wires! You have been warned.