This is just a short page to point out a couple of potential gotchas that aren't really discussed in the available online docs, as well as (hopefully) simplify the install steps a little bit. You may still need to grab the latest copy of the "The Complete Idiot's Guide to installing Dingux (plus some other facts about the Dingoo)" which covers installing from Linux, Mac OS X, and Windows (only up to XP). There are multiple versions of the document for the different OS's, so make sure you have the correct one. There are some versions which describe creating both VFAT and ext3 partitions on the card, as well as using Puppy Linix to create the ext3 partition (for Windows users), however, none of this is necessary any more.
What you'll need:
So just make sure your Mini/microSD card is formatted VFAT and at least 1 GB or so (bigger would allow more ROMs for the emulators and more WAD files to run the 3d-shooters). Put the card in your Dingoo before you start the install process. Follow the instructions to reboot the Dingoo in USB mode; to get USB-mode recognized with udev and the latest kernel, the A320 device must be plugged in (via the mini-USB cable) when you do the "hold the B key and click reset" trick. Verify with "tail -f /var/log/messages".
Once the device is properly recognized, both documented "usbtool-linux" commands will appear to work successfully, however, the flasher install script will fail to run if there is no miniSD card inserted in the A320, so be sure to perform all of the install commands *with* a card inserted in the A320. It doesn't matter what's on it; an empty VFAT card will work fine.
Basically, just follow the readme file in the installer; first run the usbtool command to install the bootloader code, then copy over your kernel file (using the correct zImage for your LCD device) along with a rootfs, and then unzip the local pack (all onto the SD-card). The next time you reboot into your linux install (ie, by holding the "Select" key) it will unpack the rootfs and set everything up for you. Then you can copy more ROMs and WAD files depending on the size of your card. And don't forget to have fun...
Transcript of successful session:
shiva dual_boot_installer-20090916 # ./usbtool-linux 1 hwinit.bin 0x80000000
USBtool v0.4 - (C) 2008 Maurus Cuelenaere
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[INFO] File size: 4576 bytes
[INFO] Searching for device...
[INFO] Found device, uploading application.
[INFO] GET_CPU_INFO: JZ4740V1
[INFO] SET_DATA_ADDRESS to 0x80000000... Done!
[INFO] Sending data... Done!
[INFO] Verifying data... Done!
[INFO] Booting device [STAGE1]... Done!
shiva dual_boot_installer-20090916 # ./usbtool-linux 1 zImage_dual_boot_installer_ILI9331 0x80600000
USBtool v0.4 - (C) 2008 Maurus Cuelenaere
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[INFO] File size: 3256320 bytes
[INFO] Searching for device...
[INFO] Found device, uploading application.
[INFO] GET_CPU_INFO: JZ4740V1
[INFO] SET_DATA_ADDRESS to 0x80600000... Done!
[INFO] Sending data... Done!
[INFO] Verifying data... Done!
[INFO] Booting device [STAGE1]... Done!
If you have problems, another command switch to try would be "usbtool 3" (which just reads the device info and doesn't try to write anything to the NAND flash on the device).
shiva dual_boot_installer # ./usbtool-linux 3
USBtool v0.4 - (C) 2008 Maurus Cuelenaere
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[INFO] Searching for device...
[INFO] Found device, uploading application.
INTC_ISR -> 1000008
INTC_IMR -> ffffffff
INTC_IMSR -> 0
INTC_IMCR -> 0
INTC_IPR -> 0
RTC_RCR -> c9
RTC_RSR -> e6c3ac8
RTC_RSAR -> e6c1caa
RTC_RGR -> 147
RTC_HCR -> 0
RTC_RCR -> c9
RTC_HWFCR -> 2e00
RTC_HRCR -> 20
RTC_HWCR -> 0
RTC_HWSR -> 10
GPIO_PXPIN(0) -> ffffffff
GPIO_PXPIN(1) -> 9effffff
GPIO_PXPIN(2) -> 7fffffff
GPIO_PXPIN(3) -> 7fffffff
CPM_CLKGR -> 0
SADC_ENA -> 0
SADC_CTRL -> 0
SADC_TSDAT -> 0
SADC_BATDAT -> 0
SADC_STATE -> 0
SLCD_CFG -> 0
SLCD_CTRL -> 0
SLCD_STATE -> 0
Here is some kernel log output showing the device being recognized normally and automounted, then
unmounted manually, and then reset (while holding the B key) and re-detected by the kernel correctly
in USB mode:
May 8 10:07:08 shiva kernel: usb 4-5: new high speed USB device using ehci_hcd and address 19
May 8 10:07:08 shiva kernel: usb 4-5: New USB device found, idVendor=07c4, idProduct=a4a5
May 8 10:07:08 shiva kernel: usb 4-5: New USB device strings: Mfr=1, Product=0, SerialNumber=1
May 8 10:07:08 shiva kernel: usb 4-5: Manufacturer: A00A00A00A00
May 8 10:07:08 shiva kernel: usb 4-5: SerialNumber: A00A00A00A00
May 8 10:07:08 shiva kernel: usb 4-5: configuration #1 chosen from 1 choice
May 8 10:07:08 shiva kernel: scsi9 : SCSI emulation for USB Mass Storage devices
May 8 10:07:08 shiva kernel: usb-storage: device found at 19
May 8 10:07:08 shiva kernel: usb-storage: waiting for device to settle before scanning
May 8 10:07:13 shiva kernel: usb-storage: device scan complete
May 8 10:07:13 shiva kernel: scsi 9:0:0:0: Direct-Access China Chip PMP USBDISK V100 PQ: 0 ANSI: 0 CCS
May 8 10:07:13 shiva kernel: scsi 9:0:0:1: Direct-Access China Chip PMP USBDISK V100 PQ: 0 ANSI: 0 CCS
May 8 10:07:13 shiva kernel: sd 9:0:0:0: Attached scsi generic sg8 type 0
May 8 10:07:13 shiva kernel: sd 9:0:0:1: Attached scsi generic sg9 type 0
May 8 10:07:13 shiva kernel: sd 9:0:0:0: [sdg] 8086528 512-byte logical blocks: (4.14 GB/3.85 GiB)
May 8 10:07:13 shiva kernel: sd 9:0:0:0: [sdg] Write Protect is off
May 8 10:07:13 shiva kernel: sd 9:0:0:0: [sdg] Mode Sense: 00 06 00 00
May 8 10:07:13 shiva kernel: sd 9:0:0:0: [sdg] Assuming drive cache: write through
May 8 10:07:13 shiva kernel: sd 9:0:0:1: [sdh] Attached SCSI removable disk
May 8 10:07:13 shiva kernel: sd 9:0:0:0: [sdg] Assuming drive cache: write through
May 8 10:07:13 shiva kernel: sdg:
May 8 10:07:13 shiva kernel: sd 9:0:0:0: [sdg] Assuming drive cache: write through
May 8 10:07:13 shiva kernel: sd 9:0:0:0: [sdg] Attached SCSI removable disk
May 8 10:07:22 shiva gnome-keyring-daemon[3545]: removing removable location: /media/2C35-E6DA
May 8 10:07:22 shiva gnome-keyring-daemon[3545]: no volume registered at: /media/2C35-E6DA
May 8 10:07:36 shiva kernel: usb 4-5: USB disconnect, address 19
May 8 10:07:37 shiva kernel: usb 4-5: new high speed USB device using ehci_hcd and address 20
May 8 10:07:37 shiva kernel: usb 4-5: New USB device found, idVendor=601a, idProduct=4740
May 8 10:07:37 shiva kernel: usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 8 10:07:37 shiva kernel: usb 4-5: Product: JZ4740 USB Boot Device
May 8 10:07:37 shiva kernel: usb 4-5: Manufacturer: Ingenic
May 8 10:07:37 shiva kernel: usb 4-5: configuration #1 chosen from 1 choice
Kernel log and usbtool output showing the error in USB-mode, ie, without doing the reset trick with
the device plugged in:
May 8 09:54:54 shiva kernel: usb 4-5: new high speed USB device using ehci_hcd and address 16
May 8 09:54:54 shiva kernel: hub 4-0:1.0: unable to enumerate USB device on port 5
May 8 09:55:46 shiva kernel: usb 4-5: new high speed USB device using ehci_hcd and address 17
May 8 09:55:46 shiva kernel: hub 4-0:1.0: unable to enumerate USB device on port 5
shiva dual_boot_installer # ./usbtool-linux 3
USBtool v0.4 - (C) 2008 Maurus Cuelenaere
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[INFO] Searching for device...
[ERR] Device not found.
[ERR] Ensure your device is in USB boot mode and run usbtool again.
Thanks to all the folks who made this possible, starting with Ignacio Garcia Perez...
Last updated 05/15/2010 10:12