I built my own root filesystem for the wiz for a time with Qt libraries. But IMHO you are missing graphic acceleration, but it is working.
I did not try to build the libraries for the root filesystem that was shipped by GPH.
No, because the runtime environment of the original wiz rootfs is rather old.
So the binaries are not compatible.
What works if I want execute old binaries:
for i in dev proc sys; do mount -o bind "/${i}" "/mnt/original-rootfs/${i}"; done
chroot /mnt/original-rootfs
I think it is not very interesting. But with the working USB host, the kernel sources and wpa_supplicant I can use now WEB/WPA/WPA2 WLAN with my wiz.
So I can now use ssh and scp / sftp to have a shell and transfer files.
It is working fine.
So I can use gdbserver for debugging now.
As yoku stated before "step 1: Make 2 partitions on SD card, vfat for uImage & ext2/ext3 for rootfs"...
I created a few partitions on a SD card.
The first parition is a FAT12 one with the uImageUP and a dummy update.gz.
The uImageUP will use the second partition of the SD card (I used ext2 FS)...
Prevent the kernel to use the cmdline tag (the bootargs given by u-boot): works
Use a rootfs from SD cards: works
---
Also working:
SD card inserted and the R not pressed while booting
--> normal startup
SD card inserted and the R is pressed while booting
--> use kernel and rootfs from SD...
I will prepare it. Name the kernel uImageUP and modify it, that the internal command line is used and not the CMDLINE TAG.
So it should be possible to use the kernel and the rootfs from the SD card.
Toolchain done...
Kernel configuration done... ('tuning' will never end *g*)
The kernel is configured and works fine with the existing rootfs.
Next step will be the rootfs.
Hello!
What are the differences between uImage and uImageUP?
I cannot find this information anywhere.
Are the file named uImage loaded by the uboot and used without write the blob to the NAND?
Are the file uImageUP loaded and written to the NAND?