Inforce Computing Forums

inforce computing forums to discuss about inforce products

Flashing the 6640 SBC

Questions and discussions related to Inforce 6640 Micro SBC

by mstoltze » Wed Feb 28, 2018 2:42 pm

1. I have successfully built Android using the supplied script. Now I am trying to flash the board. The instructions say to 'make the target board into fastboot mode'. I can't find any instructions on how to do this, but I discovered that if I hold the volume down button while powering up the board, the system does not boot the full android image. Is this fastboot mode?
2. With the board in this mode and connected to my Ubuntu build computer, a USB device shows up as device ID 18d1:d00d, Google Inc. This is apparently the SBC as it goes away when I disconnect it. Correct?
3. When I run flashall.sh it stalls with a message < waiting for any device >

Please give me some guidance so I can successfully flash the board. Thanks.
mstoltze
 
Posts: 4
Joined: Fri Feb 09, 2018 12:21 pm

by ashwin » Mon Mar 05, 2018 5:53 am

Hi,

Please use sudo ./flashall.sh.

Sometimes permissions give issues in running the flashall script on some systems.
ashwin
 
Posts: 46
Joined: Wed Jul 01, 2015 10:07 pm

by edtguy » Fri Mar 23, 2018 6:21 am

I have a 6420, and experienced a similar issue. Perhaps my solution will help you:

My board has an SW5 switch. The documentation says to hold this down while restarting the board to enter fastboot mode. This did not work for me.
When you are connected via usb, is your 6640 displayed when you execute 'adb devices' but 'fastboot devices' lists nothing? This was my case. I then executed 'adb reboot bootloader', which looked like it shut down the 6420, as the monitor attached to hdmi out 1 went dark and displayed 'no signal'. However, when I typed 'fastboot devices' from the connected linux machine, it listed the 6420, Voila!, I was in fastboot mode and was able to run the script to flash the device.
Hope this helps.
edtguy
 
Posts: 1
Joined: Thu Mar 22, 2018 5:58 am

by jhlim » Mon Oct 22, 2018 4:29 pm

1. I have successfully built Android using the supplied script.

/work/snapdragon_android/Inforce-IFC6640-AndroidBSP-880493-Rel-v2.1/source/LA.UM.5.5.r1-04300-8x96.0_Rel_V2.1/out/target/product/msm8996

-rw-rw-r-- 1 jhlim jhlim 53724456 10월 22 23:30 boot.img
-rw-r--r-- 1 jhlim jhlim 6398184 10월 23 02:00 cache.img
-rw-r--r-- 1 jhlim jhlim 4817212 10월 22 15:48 persist.img
-rw-rw-r-- 1 jhlim jhlim 2043171 10월 22 15:32 ramdisk.img
-rw-rw-r-- 1 jhlim jhlim 5679903 10월 22 23:29 ramdisk-recovery.img
-rw-rw-r-- 1 jhlim jhlim 57361708 10월 22 23:30 recovery.img
-rw-rw-r-- 1 jhlim jhlim 1646717808 10월 23 02:04 system.img
-rw-r--r-- 1 jhlim jhlim 157801696 10월 23 02:00 userdata.img

ramdisk.img and ramdisk-recovery.img are not listed in flashall.sh

-rw-rw-r-- 1 jhlim jhlim 2043171 10월 22 15:32 ramdisk.img
-rw-rw-r-- 1 jhlim jhlim 5679903 10월 22 23:29 ramdisk-recovery.img

are they immediate results ?
jhlim
 
Posts: 3
Joined: Thu Oct 18, 2018 6:52 pm

by jhlim » Mon Oct 22, 2018 10:19 pm

hi mstoltze

my 6640 SBC was Nuga 7.0

I did flash it with Nuga 7.1.1

1. update /etc/udev/rules.d/51-android.rules for usb Linux PC
https://developer.android.com/studio/run/device

2. sudo flashall.sh
jhlim@jhlim-r8:/work/snapdragon_android/Inforce-IFC6640-AndroidBSP-880493-Rel-v2.1/binaries$ sudo ./flashall.sh
< waiting for device >
flashall.sh script is just waiting

3-1. 6640 SBC Power Off
3-2. Keep Volume - Button Pressing
3-3. Press Power on Button

Then flashall.sh script continues to work

jhlim@jhlim-r8:/work/snapdragon_android/Inforce-IFC6640-AndroidBSP-880493-Rel-v2.1/binaries$ sudo ./flashall.sh
< waiting for device >
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'boot' (52465 KB)...
OKAY [ 1.542s]
writing 'boot'...
OKAY [ 0.349s]
finished. total time: 1.891s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.019s]
finished. total time: 0.019s
erasing 'system'...
OKAY [ 0.006s]
sending sparse 'system' (262095 KB)...
OKAY [ 7.678s]
writing 'system'...
OKAY [ 2.629s]
sending sparse 'system' (247475 KB)...
OKAY [ 7.332s]
writing 'system'...
OKAY [ 2.417s]
sending sparse 'system' (253959 KB)...
OKAY [ 7.586s]
writing 'system'...
OKAY [ 2.821s]
sending sparse 'system' (261908 KB)...
OKAY [ 7.421s]
writing 'system'...
OKAY [ 2.957s]
sending sparse 'system' (260864 KB)...
OKAY [ 7.425s]
writing 'system'...
OKAY [ 2.640s]
sending sparse 'system' (261554 KB)...
OKAY [ 7.463s]
writing 'system'...
OKAY [ 2.539s]
sending sparse 'system' (60253 KB)...
OKAY [ 1.705s]
writing 'system'...
OKAY [ 0.441s]
finished. total time: 63.061s
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.019s
target reported max download size of 536870912 bytes
sending 'recovery' (56017 KB)...
OKAY [ 1.626s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 1.996s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.019s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.012s]
sending 'cache' (6248 KB)...
OKAY [ 0.208s]
writing 'cache'...
OKAY [ 0.116s]
finished. total time: 0.336s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.042s]
finished. total time: 0.042s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.012s]
sending 'userdata' (154103 KB)...
OKAY [ 4.458s]
writing 'userdata'...
OKAY [ 1.264s]
finished. total time: 5.734s
erasing 'persist'...
OKAY [ 0.019s]
finished. total time: 0.019s
target reported max download size of 536870912 bytes
sending 'persist' (4704 KB)...
OKAY [ 0.155s]
writing 'persist'...
OKAY [ 0.079s]
finished. total time: 0.234s
rebooting...

finished. total time: 0.012s
jhlim
 
Posts: 3
Joined: Thu Oct 18, 2018 6:52 pm


Return to INFORCE 6640™ Micro SBC

cron

Contact Us.