—————–

$ ssh ubuntu@10.0.1.10
ubuntu@10.0.1.10′s password:
Linux n810 2.6.33-rc8-07939-g4fe94ed-dirty #149 Fri Feb 26 14:58:22 AMT 2010 armv6l
…
ubuntu@n810:~$ cat /proc/cpuinfo | grep Hardware
Hardware    : Nokia N810
ubuntu@n810:~$ uname -a
Linux n810 2.6.33-rc8-07939-g4fe94ed-dirty #149 Fri Feb 26 14:58:22 AMT 2010 armv6l GNU/Linux
ubuntu@n810:~$ cat /etc/issue.net
Ubuntu 9.10

—————–

You can download images:

* linux 2.6.33 to n800/n810

* ubuntu karmic minimal image (just console over SSH)

* howto to create your own images

* patches, pkgs and etc

Some notes about Linux 2.6.33 with n8x0:

* Some corrections are necessary to get USB working.

* My kernel configuration define g_ether(USB gadget ethernet) as built-in(CONFIG_USB_ETH=y).

* initfs is not necessary. My kernel configuration changed to bootup directly by flash memory(CONFIG_CMDLINE=”root=1f04 rootfstype=jffs2 console=ttyS2,115200n8″).

* My personal linux-omap tree is available at gitorious

Some notes about ubuntu Karmic with n8x0:

* Generated using rootstock

* Correction to apt works correctly with JFFS2

* Workaround to startup USB interface(IP 10.0.1.10) automatically using udev

* Using openssh-client/server instead of dropbear(lightweight). Dropbear install fails

PS:
* Thanks to Stskeeps, luke-jr from #mer at irc.freenode.net !

* rbelem, post done. enjoy it! http://www.rbelem.info/

* Doubts, questions or comments? Post it here or use #ubuntu-arm at irc.freenode.net

Finalmente estou postando o video de minha apresentação no FISL10. Alguns meses para a TV-SL liberar e mais algumas semanas até finalmentar fazer um post com o link para o video. Acho que preciso reduzir estes tempos.

Video disponível no site da TV-SL:

ou diretamente  HERE.

PS: Já estou pensando no FISL11 !

First I tested it with Maemo using a simple open wlan network and it works fine.

The problems that I faced:

* Missing tools
You will need some tools that does not came with the original image. Some extra packages installed(wireless-tools dropbear-server libicd-network-dummy dropbear-scp) using an extra repositories. I installed the packages with default Maemo kernel(2.6.21-omap1) to have access to internet during the installing of preview packages.

* RD flags did not work properly
Using all flags defined by README the device turn off without any output or error message. I used the “flags no-omap-wd, no-lifeguard-reset” as Briglia and it works.

* Navegate using Maemo browser
Maemo does not recognize the WLAN interface and I’m not able to select a network using the UI. So I connected to network using Xterm, but anyway I was not able to navegate using MaemoBrowser. It was necessary to create a DUMMY connection say the Maemo ICD that network is available.

I did some notes and it’s available on my wiki page.

A few months ago I posted about Mamona Platform on BeagleBoard. That rootfs was based on OMAP3430SDP with some hacks. A few questions about Mamona on Beagleboard have been sent and I want to say sorry for my delay. I’ve been working hard on internal projects at INdT.

Last week I worked to create BeagleBoard machine in Mamona. Not a hard work! Considering that Mamona is OE based then most patches came from OE and just small changes were necessary to boot up a basic Mamona rootfs. The current development is available on mamona.git branch mamona_beagle. Below you can see a small demo and some pictures.

Yesterday I created the project on BeagleBoard website.

You can have more details using the notes I’ve done during development.

Thanks to Texas Instrument for this good project !!!

The answer to Mamona and BeagleBoard: when?:

Now we have Mamona working with TVOUT using this board.  Nice !!

ASAP I will post more details about this topic.

 More pictures …

We’re proud to announce that Firefox 3 is working with Mamona. Thanks to all Mamona team, especially Eduardo Valentin.

Instruction:

Follow Mamona development tutorial replacing  ” bitbake <meta-package>” for “bitbake task-mamona-sdk && bitbake task-mamona-wm && bitbake firefox”.

And you will have Firefox 3 available in your Mamona repository.

More pictures …

Since Friday(July 25th) we’re able to build Midori Browser based on Webkit with Mamona tools. We tested this browser with Nokia N810 and BeagleBoard.

Main steps to Build Midori:

Follow the Mamona development  till Building Mamona.

Replace  ” bitbake <meta-package>” for “bitbake task-mamona-sdk && bitbake task-mamona-wm && bitbake midori” at setion Building Mamona.

And Midori will be available in your Mamona repository.

That’s all!!

More pictures … 

My TODO list include Mamona test with BeagleBoard.

Mamona and BeagleBoard: When? 

I should improve it.

Hi all,

I’m working with an OMAP1610 H2 and it was taking a long time to load and uncompress kernel. Eduardo recommended me some things to be done.

BE CAREFUL –
I’M NOT RESPONSIBLE FOR YOUR ACTS. YOU CAN MISS INFORMATION IF YOU DO NOT FOLLOW THE STEPS CORRECTLY.

1 – Upgrade u-boot

- Install scratchbox for cross-compilation.

- Download the last version of u-boot.

- Configure and Compile u-boot

[sbox-arm: ~/applications/u-boot-1.3.0] > make omap1610h2_config && make

- Copy the new u-boot.bin to your tftpboot directory(details here)

$ cp /scratchbox/users/alecrim/home/alecrim/applications/u-boot-1.3.0/u-boot.bin /tftpboot

- Using minicom, access the current u-boot prompt and load the new u-boot

OMAP1610 H2 # tftp 0×10000000 u-boot.bin
TFTP from server 10.0.0.1; our IP address is 10.0.0.2
Filename ‘u-boot.bin’.
Load address: 0×10000000
Loading: ###################
done
Bytes transferred = 93568 (16d80 hex)

The bold number is import, save it.IT’S YOUR U-BOOT HEXADECIMAL!!

- Unlock the flash memory, erase a sector, copy the new u-boot.bin and lock the flash again.

DANGEROUS!! TAKE CARE!!DANGEROUS!! TAKE CARE!!DANGEROUS!! TAKE CARE!!DANGEROUS!! TAKE CARE!!

REPLACE THE BOLD HEXADECIMAL (16d80)!!! PUT YOUR U-BOOT HEXADECIMAL !!!

OMAP1610 H2 # protect off 00000000 0001ffff
Un-Protected 1 sectors

OMAP1610 H2 # era 00000000 0001ffff

Erasing sector 0 … done
Erased 1 sectors

OMAP1610 H2 # cp.b 0×10000000 0×00000000 0x16d80
Copy to Flash…\done

OMAP1610 H2 # protect on 00000000 0001ffff
Protected 1 sectors
OMAP1610 H2 #

Now, you can restart your board and pray for some output on your serial.

references:
http://tree.celinuxforum.org/CelfPubWiki/OSK_2fuboot
http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=11994&path=templatedata/cm/product/data/omap_1610
http://tree.celinuxforum.org/CelfPubWiki/OSK