Differences between revisions 28 and 29
Revision 28 as of 2009-10-25 12:06:09
Size: 7482
Editor: OsamuAoki
Comment:
Revision 29 as of 2009-10-25 15:46:07
Size: 7753
Editor: OsamuAoki
Comment:
Deletions are marked like this. Additions are marked like this.
Line 135: Line 135:
TBD Ubuntu source has ("{{{grep -R spider *}}}") few interesting lines:

 * {{{arch/arm/mach-mx51/mx51_erdos_splash.c:static volatile char *fb_show_spider_logo_mem;}}} and like
 * {{{drivers/video/mxc/mxcfb_sharp_wsvga.c: * 2009/07/21 : fb_show_spider_logo() use.}}} and like

Translation(s): none

(!) ?/Discussion

DebianOn is an effort to document how to install, configure and use Debian on some specific hardware. Therefore potential buyers would know if that hardware is supported and owners would know how get the best out of that hardware.

The purpose is not to duplicate the Debian Official Documentation, but to document how to install Debian on some specific hardware.

If you need help to get Debian running on your hardware, please have a look at our user support channels where you may find specific channels (mailing list, IRC channel) dedicated to certain types of hardware.

Models covered
PC-Z1 ?NetWalker

Sub-models :
- Video card
- Screen size: 5" WSVGA (1024x600) with touchscreen
- Internal wireless card

Overall Status

Here is overall status of Debian on Sharp PC-Z1 (NetWalker).

Debian on microSD

So far, it seems to be able to install Debian by using the recovery microSD card. (NetWalker PC-Z1 Debian : This link is to Japanese page)  This requires you to boot system as recovery mode and root is on microSD card.

Debian on MTD

In order to install to on board mtd flash, ubi.img needs to be created and placed onto the recovery microSD card.

Resource for hacking

Here are some resources to use Sharp PC-Z1 (NetWalker) by both Debian and Ubuntu.

For English users: How to change Sharp NetWalker PC-Z1 OS into English.

Compatible hardware

  • This PC-Z1 comes with internal wifi card as eth0.

  • Any USB connected wired Ethernet adapters seem to work fine as eth1 without any action.

    • I use Logitec LAN-TX/U2H3B (3 USB port hub + Ethernet)

Kernel and user land source as provided

{i} Sharp official GPL compliance site: not working as of Oct 25, 2009. This is sad ...

{i} Kernel source: http://netbook-remix.archive.canonical.com/updates/pool/public/l/linux-fsl-imx51/

<!> The armel architecture is known to use "char" as "unsigned" which is not normal behavior thus breaks many existing softwares working fine on i386.

Ubuntu kernel provided is patched. You need to use it for now to get proper hardware supports. Many user land softwares are patched for armel too.

APT line can be added to get sources for kernel and other applications:

deb-src http://ports.ubuntu.com/ubuntu-ports jaunty main universe
deb-src http://netbook-remix.archive.canonical.com/updates/dists/jaunty-araneo/ jaunty main universe

URL links for browsers:

/!\ Although it is tempting to put archive such as Ubuntu security updates for Ubuntu system as provided, it will likely to break installed softwares such as Firefox. I guess update from pertinent canonical archive is needed for proper armel patched updates.

{i} Kernel cross compile hint: NetWalker Kernel Rebuild (JPN)

UFO packages

There are 3 packages which are not found on the repository.

  • imx-lib : platform specific libraries for imx platform. VPU firmware.
    • Freescale i.MX515 (ARMv7) is CPU used.
    • Why not on repository?
  • libfsl-mm-core
    • Freescale multimedia core libraries.
    • Why this is not on repository?
  • spider-lcfont
    • Sharp non-free font. (This is understandable.)

These should have beem installed as a part of initial installer image.

<!> Directories related to the imx-lib package are set to UID=1000 (first login user). Buggy feature.

Recover script

The official recover script will let you create microSD (2GB). That is essentially:

  • Download files using recover.sh script to microSD card.
    • os.tar.bz2 : root file system content for the recover system run from microSD slot.
    • zImage : kernel to used to update the system.
    • ubi.img : rootfile system image (Large!)
  • Insert microSD (if you removed.)
  • Reboot with both buttons for mouse on left top corners pressed well after you see sharp logo.
    • Linux system is booted from microSD card.
    • /etc/rc2.d/S01upfirm is executed to call a program /usr/local/bin/update_spider.sh.

    • /usr/local/bin/update_spider.sh (Its configuration file: spider.srp) updates system by:

      • ubi.img (RFS ubifs) to MTD NAND Flash device (I guess)

      • zImage (Kernel) to NOR BOOTLOADER Flash device (I guess) -- merely placing kernel at /boot may not be good enough

I tried to create alternative recover script for our normal Debian PC: spider-recovery This was intended to be used with USB connected reader on PC.

This was tested to download files but this does not boot recover system as is. But if this is run on NetWalker, this script create bootable microSD. I only see difference as:

  • ext2 created by Debian lenny on amd64: Filesystem flags: signed_directory_hash
  • ext2 created by Ubuntu 09.4 armel: Filesystem flags: unsigned_directory_hash

This is the one causing difference. The original ext3 hash algorithms assumed that variables of type char were signed, as God and K&R intended. Unfortunately, this assumption is not true on some architectures. There were patch to fix kernel (2009-05-08 11:58:01). The armel architecture is known to use "char" as "unsigned".

The file in microSD needs to be modified if they are created on non armel system. The work around is to remove symlink at /etc/rcS.d/S20checkroot.sh on such microSD card to ignore "root not sync".

Bootloader

This seems to use Redboot.

Per, comments in update_spider.sh:

#   spider.srp
#    6,rootfs.jffs2   (RFS jffs2)
#    5,ubi.img        (RFS ubifs)
#    4,zImage         (Kernel)
#    3,info.bin       (System information)
#    2,fis.bin        (Redboot fis)
#    1,redboot.bin    (Redboot)

Normally, it is wise not to touch NOR flash since it will make your system unbootable. If you break it, you need hardware such as JTAG connected to somewhere on main board to fix your system.

Internal hardware photos

You can see internal hardware photos at http://hitaki.net/diary/20090928.html.

Kernel diff

Ubuntu source has ("grep -R spider *") few interesting lines:

  • arch/arm/mach-mx51/mx51_erdos_splash.c:static volatile char *fb_show_spider_logo_mem; and like

  • drivers/video/mxc/mxcfb_sharp_wsvga.c: * 2009/07/21 : fb_show_spider_logo() use. and like