Firefly Open Source Community

   Login   |   Register   |
New_Topic

RK3288 with virgin SDK build stalls with USB reset, won't boot into Android

13

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
13
Posted at 3/7/2015 10:01:01     

RK3288 with virgin SDK build stalls with USB reset, won't boot into Android

Hello:

I have followed the instructions for "Building Android" (http://wiki.t-firefly.com/index.php/Fir ... android/en).

Builds for both kernel and Android completed successfully.

Used rkflashkit to flash boot.img, kernel.img, misc.img, recovery.img, resource.img system.img and reset board

The Firefly kernel splash screen is displayed, but the device never boots into Android.

The last few lines displayed on the serial debug console are shown below. I have more info if needed, but the wiki wouldn't allow me to attach a file regardless of what extension I used.


Any assistance would be much appreciated - thank you!


[    5.804847] init: /dev/hw_random not found
[    5.805569] android_usb: already disabled
[    5.805660] android_usb: Cannot enable 'adb' (-22)init: property 'ro.serialno' doesn't exist while expanding '${ro.serialno}'
[    5.805736] init: cannot expand '${ro.serialno}' while writing to '/sys/class/android_usb/android0/iSerial'
[    5.903412] iep dpi mode inactivity
[   10.376531] init: /sbin/e2fsck terminated by exit(8)
[   10.376556] init: Operational error while checking volume '/dev/block/platform/emmc/by-name/cache'
[   10.376647] init: Failed to mount /dev/block/platform/emmc/by-name/cache, format it to ext4 now
[   10.378524] init: /dev/hw_random not found
[   10.378595] init: Unable to open persistent property directory /data/property errno: 2
[   10.379491] init: service 'recovery' requires console
[   10.379505] init: service 'console' requires console
[   10.379572] android_usb: already disabled
[   10.379676] android_usb: Cannot enable 'adb' (-22)pcd_pullup, is_on 1
[   10.379730] init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
[   10.379782] init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
[   10.379826] init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
[   10.379840] init: property 'ro.serialno' doesn't exist while expanding '$ro.serialno'
[   10.379852] init: cannot expand '$ro.serialno' while writing to '/sys/class/android_usb/android0/iSerial'
[   10.882512] es8323_mic_state_ctrl read:
[   10.882540] mic_state_switch 0
[   10.882549] hp_det = 0,insert hp
[   10.882556] hp mic use intern
[   17.849171] *****************vbus detect*******************
[   18.028431] Using Buffer DMA mode
[   18.028447] Periodic Transfer Interrupt Enhancement - disabled
[   18.028455] Multiprocessor Interrupt Enhancement - disabled
[   18.028468] OTG VER PARAM: 0, OTG VER FLAG: 0
[   18.028476] ^^^^^^^^^^^^^^^^^Device Mode
[   18.028516] *******************soft connect!!!*******************
[   18.152382] USB RESET
[   18.288377] android_work: sent uevent USB_STATE=CONNECTED
[   18.542471] USB RESET
[   18.682302] USB RESET
[   18.867870] USB RESET
[   19.028983] USB RESET
[   19.214851] USB RESET
[   19.406521] USB RESET

Reply

Use props Report

403

Credits

10

Prestige

12

Contribution

intermediate

Rank: 3Rank: 3

Credits
403
Posted at 3/9/2015 10:31:34     

Re: RK3288 with virgin SDK build stalls with USB reset, won't boot into Android

You can pack the log files into a zip file and upload it .

One way to debug is to replace one image at one time. That's to say, starting from the stock firmware.

1. Flash newly compiled kernel.img, resource.img and boot.img. Check whether the kernel part works.

2. Flash the newly compiled system.img and misc.img (misc.img will make device do wipe data, cache, etc). Check whether system.img works.



        


Reply

Use props Report

13

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
13
Posted at 3/13/2015 05:19:45     
busybee:

Thanks for getting back to me. The suggestion about troubleshooting using 1 image at a time makes sense, I will keep that in mind.

I was able to get the device booted after going back and doing a make clean on both kernel and SDK. The only other thing  I've had to do to address boot problems was once (so far) the parameter file needed re-flashed after flashing all my images.

For now, everything is building and booting.
Reply

Use props Report

14

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
14
Posted at 4/3/2015 13:17:50     
Stillgoing: I had the same issue as you before, After flashing parameter file my box just keeps rebooting itself stuck in a loop or something. Any suggestions ? Also how did you hook the Serial debug cable ? I bout a USB to RS232 cable but cant figure out how to connect and debug.

Thanks in advance.
Reply

Use props Report

6

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
6
Posted at 6/2/2015 18:43:05     
Last edited by achary In 6/2/2015 18:44 Editor

Hi,
I had identical problem, 100% reproducible.

It turned that the reason for it was a recovery.img produced by mkimage.sh script after kernel and Android build.
When I used recovery.img that is included in stock firmware - then things went fine and I was able to boot the device  from my custom Android kernel.

The official wiki on hereclearly suggests using recovery.img and for some reason the recovery.img seems not to run out of the box after I got it built on my Ubuntu machine.

Hope that helps a bit
Regards,
Reply

Use props Report

380

Credits

0

Prestige

0

Contribution

intermediate

Rank: 3Rank: 3

Credits
380
Posted at 7/27/2016 10:15:31     
Last edited by qingfeng623 In 7/27/2016 10:17 Editor

I had identical problem
Reply

Use props Report

380

Credits

0

Prestige

0

Contribution

intermediate

Rank: 3Rank: 3

Credits
380
Posted at 7/27/2016 10:17:19     
I had identical problem.
Reply

Use props Report

380

Credits

0

Prestige

0

Contribution

intermediate

Rank: 3Rank: 3

Credits
380
Posted at 7/27/2016 14:54:02     
check parameter file, console=ttyFIQ0,burn then reboot
Reply

Use props Report

34

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
34
Posted at 12/27/2018 16:46:03     
can you tell me how to reslove this issue? I have a issue similar to yours.According to my LOG ,the kernel is stop at android_work: sent uevent USB_STATE=CONFIGURED .below is my LOG


[    9.369769] PortPower off
[    9.369776] rk_battery_charger_detect_cb , battery_charger_detect 6
[    9.469199] Using Buffer DMA mode
[    9.469211] Periodic Transfer Interrupt Enhancement - disabled
[    9.469217] Multiprocessor Interrupt Enhancement - disabled
[    9.469224] OTG VER PARAM: 0, OTG VER FLAG: 0
[    9.469230] ^^^^^^^^^^^^^^^^^Device Mode
[    9.960145] ***************vbus detect*****************
[    9.962327] rk_battery_charger_detect_cb , battery_charger_detect 1
[   10.139387] Using Buffer DMA mode
[   10.139400] Periodic Transfer Interrupt Enhancement - disabled
[   10.139407] Multiprocessor Interrupt Enhancement - disabled
[   10.139414] OTG VER PARAM: 0, OTG VER FLAG: 0
[   10.139420] ^^^^^^^^^^^^^^^^^Device Mode
[   10.139461] *******************soft connect!!!*******************
[   10.247745] USB RESET
[   10.286060] android_work: sent uevent USB_STATE=CONNECTED
[   10.289708] USB RESET
[   10.364666] android_usb gadget: high-speed config #1: android
[   10.364735] android_work: sent uevent USB_STATE=CONFIGURED
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list