First impressions of an unwilling board

Astralix

Ok, the fun has only lasted short time...

While just showing a youtube overview screen, the board rebooted and is again trapped in a boot loop.

U-Boot 2014.10-RK3288-02 (Nov 26 2014 - 09:28:44)

CPU: rk3288
CPU's clock information:
arm pll = 600000000HZ
periph pll = 300000000HZ
ddr pll = 200000000HZ
codec pll = 594000000HZ
Board:        Rockchip platform Board
DRAM:  Found dram banks:1
Adding bank:0000000000000000(0000000080000000)
128 MiB
storage init OK!
Using default environment

GetParam
check parameter success
Unknow param: MACHINE_MODEL:rk30sdk!
Unknow param: MACHINE_ID:007!
Unknow param: MANUFACTURER:RK30SDK!
Unknow param: PWR_HLD: 0,0,A,0,1!
failed to prepare fdt from boot!
power key: bank-0 pin-5
can't find dts node for ricoh619
pmic:act8846
Can't find dts node for fuel guage cw201x
SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 2014-11-26#2.17
empty serial no.
checkKey
vbus = 1
no fuel gauge found
no fuel gauge found
read logo_on switch from dts [0]
no fuel gauge found
got recovery cmd from misc.
failed to load fdt from recovery!
kernel   @ 0x02000000 (0x00608530)
ramdisk  @ 0x04bf0000 (0x00275b8f)
Secure Boot state: 0
bootrk: do_bootm_linux...
Loading Device Tree to 0480b000, end 04826184 ... OK
Add bank:0000000000000000, 0000000080000000

Starting kernel ...


[    0.000000] Booting Linux on physical CPU 0x500
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.0 (dujw@tchipserver2) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #63 SMP PREEMPT Thu Dec 11 17:22:26 CST 2014
[    0.000000] CPU: ARMv7 Processor [410fc0d1] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Rockchip RK3288 (Flattened Device Tree), model: rockchip,rk3288
[    0.000000] hdmi init vic is -1
[    0.000000] rockchip_ion_reserve
[    0.000000] cma: CMA: reserved 16 MiB at 2e800000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] Boot mode: RECOVERY (2) flag: RECOVER (0xc3524203)
[    0.000000] PERCPU: Embedded 9 pages/cpu @c1ed4000 s14016 r8192 d14656 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 522768
[    0.000000] Kernel command line: console=ttyFIQ0 androidboot.hardware=rk30board androidboot.console=ttyFIQ0 board.ap_has_alsa=0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init  mtdparts=rk29xxnand:0x00002000@0x00000000(parameter),0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00008000@0x0000e000(kernel),0x00010000@0x00016000(boot),0x00010000@0x00026000(recovery),0x0001a000@0x00036000(backup),0x00040000@0x00050000(cache),0x00002000@0x00090000(kpanic),0x0018000�DDR Version 1.00 20141007
In
Channel a: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Channel b: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Memory OK
Memory OK
OUT

It is the unmodified DualBoot v0930 image.

EDIT:

As I got a US power supply, I used the USB adapter cable connected to a USB3 HUB that is powered by a 5A supply.

This doesn't work... I used some test cables from the lab to do a flying adaption of US to Euro (don't try this at home!) and it boots again into Linux or Android.

So, if you encounter same problem you should try to change the way you supply power to the fly

EDIT:

The FAN is labeled 5V so I connected it to the 5V labeled upper contacts of the right extention port. What I didn't see was, that there are two contacts labeled FAN+ / FAN- at the lower end of this port. Using these pins while again supplying power with the USB adapter cable, it works more stable. Still testing this.

It looks like the fan introduces too much ripple into the 5V power train if it is connected to the upper 5V pins.

So the correct connection of the fan should be mentioned in the starter guide under a chapter mechanical assembly?

http://wiki.t-firefly.com/index.php/Fir ... r_guide/en

Astralix

Astralix

Hey again,




It is now definitely clear: You need to keep care that you use a good power supply.?

A 3.5A USB HUB does not work reliable. Even on a USB3 HUB it may give random reboots.

I used lab cords to adapt the 5V/3A US power supply delivered with the firefly and now all images of 2014-11-11 and 2014-12-11 do work without obvious problems.




So firefly team, please check the schematics, the FAN+/- pins on the right connector are not mentioned anywhere else again. So where are they connected? Can the fan be turned off on power-down or can it be regulated by PWM?




And please add precise tags to the git repository at bitbucket so people don't have to guess which version will work and please check the inconsistency between the voltages mentioned in the schematics and the rk3288-firefly.dts.




Please add these findings to the wiki so other people do not run into the same trap.




After a short test with Ubuntu, I can say that this board looks like a really nice piece of hardware and I hope I find enough time for testing in the next days...




Astralix

cappybob

Astralix

Glade to see you around,? I see you found the board glitch with power, I am running the 3amp supply?with a?fan, keyboard, mouse, ssd, and game controller pretty much full time, also have played with .dts and added a few tenths here and there.? Did additional research on schematics and power input plug-in?is internally protected with a 3amp fusible link.? Saw also the discussion of heat and fan on irc? At the shipped frequency (Software). the 1.80 MHZ will run really hot, personally I try to keep my units below 70 C.? The Unit as shipped can approach that figure, so I have added a?heat sink and fan.?

later cappybob

busybee

Astralix, glad to hear that you have solved the problem.

Thanks for your suggestion. We'll have the doc updated.