search

dmitrysmagin / dingoo-linux

Automatically exported from code.google.com/p/dingoo-linux
1 stars 2 forks source link

linux usb boot does not work after A320 poweron, needs to boot to ucos first #14

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. poweroff device from original OS
2. hold B
3. insert usb cable (device will poweron into usb boot mode)
4. optional reset while holding B does not help too
5. device loads hwinit and zimage fine but no linux on display and no usb
serial device appears, sadly I don't have serial port so no idea where it
is stuck. after kernel is loaded it no longer talks to usbboot so it
started something

The only way that works for me is to boot into original system first,
attach usb, unmount cards and reset while original system is running, then
it boots fine.

It doesn't matter much now but may mean that hw initialization is
incomplete so there may be same problem when booting linux directly.

black dingoo with 1.03 firmware

Original issue reported on code.google.com by fano...@gmail.com on 31 May 2009 at 10:55

GoogleCodeExporter commented 9 years ago 
i had this problem also but it's not due to the bootloader i think although i'm 
not
certain. But i did find a workaround. it sounds stupid but it works :
just type lsusb you will notice your linux (my ubuntu 9) box will hang and not
directly display the usb devices, the 1st time it does not show the dingoo 
device but
the 2nd time you run lsusb "Bus 001 Device 097: ID 601a:4740" pops up (this is 
the
dingoo) only upload the hwinit file and zimage file when you see that. If you 
do it
too early linux won't boot. so i think it's something related to the host linux 
box
and not about the bootloader (although i'm not certain). Just try it out, it 
works
for me.

Original comment by joyrider...@hotmail.com on 31 May 2009 at 7:12

GoogleCodeExporter commented 9 years ago 
Well, actually I have the same issue when using usb_boot.exe from Windows so at 
least
it is not oddity of linux host. I wonder what serial console would say. It can 
be
anything (like mmc interface not properly initialized so mounting root fs did 
not
work). Either we'll see this issue when trying 'native' linux boot from flash 
and it
needs to be be solved or we won't see it so it doesn't matter.

Original comment by fano...@gmail.com on 1 Jun 2009 at 10:24

GoogleCodeExporter commented 9 years ago 
Could you please check again if this problem persist in the latest release?

Original comment by igga...@gmail.com on 4 Sep 2009 at 11:43

GoogleCodeExporter commented 9 years ago 
i have the same problem. i upgraded my black dingoo with 9331_3 lcd from 1.10 
to 1.20
custom.

i connected it in usb-mode:

[28456.030051] usb 2-4: new high speed USB device using ehci_hcd and address 13 

[28456.183230] usb 2-4: configuration #1 chosen from 1 choice  

lsusb shows: Bus 002 Device 025: ID 601a:4740

after that i did:

root@htpc:~/x# ./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!       

root@htpc:~/x# ./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!       

in debian lenny the second usbtool-start had an error -110 but with ubuntu 9.10 
it is
a little bit better (as you see above) but:

the black screen remains. if i try to repeat one of the both usbtool-starts i 
get an
error:

root@htpc:~/x# ./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:
[ERR]  Error sending control message (-110, error sending control message: 
Connection
timed out)

so it seems something is happening - but what?!

Original comment by qwertol...@googlemail.com on 20 Dec 2009 at 9:33