Debian on rk3229 is it possible?

[fabiobassa]

hello @suppenkasper

well I guess you have to recompile the module itself because it could be compiled for other kernel
just to let you know if you do apt-get update then you can install headers for your kernel and compile if you have sources for that dongle , of course !!

here are kernel headers for your respeaker

https://github.com/respeaker/deb/tree/master/archive/pool/main/l/linux-4.4.138-respeaker-r0

[primoitt]

Hello fabiobassa

I just sent you a private msg.. Plz check your inbox. Thank you!

[Reddwarf]

Hello!
I just got an Q66 box with RK3229 cpu, it this project still going and is there any interest for my details (android, HW config etc?)

[fabiobassa]

hello Reddwarf ,

yes the project is going on , the problems as already said in this post are:

1) the ddr aren't egual, each board needs its own loader, actually ONE solution is using original rkxxxxxxxx.img loader
2) some board using emmc, some other using nand. It is necessary compile kernel and adjust resources ( dtb) to use or not a driver that is incompatible in case of emmc or nand ( must use one OR other )
3) depending on dimension of firmware and of board is necessary adjust the mtdparts in parameters.txt
4) not decent graphical hardware acceleration avaible, we can use those boards as ftp, dlna servers, voip but not yet possible use them as players for videos
This is the reason isn't yet been released a guide, a team is making all efforts to have ONE quite satisfull guide to at least give guidelines

I can say that original loader from android for that particular board + original uboot from android for that particular board + original trust from PARTICULAR android ( trust_with_ta_ga4fd2d1.img ) are actually giving a quite universal way to boot the board.

then is COMPULSORY adjust parameters.txt to give the right location of rootfs and is possible use kernel-4.4.138-respeaker-r0 and resources-rk3229-respeaker-v2.dtb from respeaker project to at least give life to board .

and follow the uart log to have an idea of what is needed to change to give right path to kernel for finding rootfs

I suppose will quite never exist an UNIVERSAL image to flash will be alway necessary tweak on every single board so uart connection are needed
Now some questions:
1) which android rom your board uses?
2) have you access to uart logs?

cheers

[xwx]

Can you please upload somewhere the loader that can boot linux I have some spare boxes would like to try. Thanks.

[hannah]

Can you please upload somewhere the loader that can boot linux I have some spare boxes would like to try. Thanks.

I too am interested.

[nmocruz]

Hi, I'm interested to I have a r39 4k box docooler 1gb, to try,

[fabiobassa]

Hello all good people
The loader for booting from internal storage is the same one included in original stock ROM
Universal loader for booting from SD (  not only Linux but any os) doesn't exist and is not enough say I have 1 giga/8giga

Is needed uart log for debug the right one

[xwx]

I completly agree, tried different loaders, u-boot ... same result , when I'll have some spare time will try to take the logs. maybe the bord have some HW jumpers that indicates how to boot or maybe SD is attached to different pins for booting who knows... maybe logs will show... Bought them only for cheap linux device hope will succed.

[fabiobassa]

xwx
Exactly !!!
I just want to support my personal experience: two IDENTICAL boards ( see previous attached photos) but one emmc and the other nand !

Well bootloader and uboot of one is not working on the other

[xwx]

Some boot loogs :
Android system wthat diesn't boot:

DDR Version V1.09 20190628
In
ID:0xFFF
300MHz
DDR3
Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
mach:2
OUT
Boot1 Release Time: May 13 2019 17:02:59, version: 2.56
ChipType = 0xc, 407
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
SdmmcInit=0 NOT PRESENT
StorageInit ok = 53416
SecureMode = 0
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part:  0, name:            uboot, start:0x4000, size:0x2000
GPT part:  1, name:            trust, start:0x6000, size:0x2000
GPT part:  2, name:             misc, start:0x8000, size:0x2000
GPT part:  3, name:    baseparameter, start:0xa000, size:0x800
GPT part:  4, name:         resource, start:0xa800, size:0x8000
GPT part:  5, name:           kernel, start:0x12800, size:0x10000
GPT part:  6, name:              dtb, start:0x22800, size:0x2000
GPT part:  7, name:             dtbo, start:0x24800, size:0x2000
GPT part:  8, name:             logo, start:0x26800, size:0x8000
GPT part:  9, name:           vbmeta, start:0x2e800, size:0x800
GPT part: 10, name:             boot, start:0x2f000, size:0x10000
GPT part: 11, name:         recovery, start:0x3f000, size:0x20000
GPT part: 12, name:           backup, start:0x5f000, size:0x8000
GPT part: 13, name:            cache, start:0x67000, size:0x80000
GPT part: 14, name:           system, start:0xe7000, size:0x400000
GPT part: 15, name:         metadata, start:0x4e7000, size:0x8000
GPT part: 16, name:           vendor, start:0x4ef000, size:0x40000
GPT part: 17, name:              oem, start:0x52f000, size:0x20000
GPT part: 18, name:              frp, start:0x54f000, size:0x400
GPT part: 19, name:         security, start:0x54f400, size:0x1000
GPT part: 20, name:         userdata, start:0x550400, size:0x93fbdf
find part:uboot OK. first_lba:0x4000.
find part:trust OK. first_lba:0x6000.
LOADER Check OK! 0x60200000, 146345
TOS    Check OK! 0x68400000, 168037
Enter Trust OS
INF [0x0] TEE-CORE:init_primary_helper:381: Initializing (1.1.0-393-g746912b #296 Fri Jul 12 03:49:20 UTC 2019 arm)

INF [0x0] TEE-CORE:init_primary_helper:382: Release version: 2.0

INF [0x0] TEE-CORE:init_primary_helper:383: Next entry point address: 0x60200000

Linux SD that doesn't boot:

[,.%fB.+'7u?2]]U-U--|??
DDR Version V1.09 20190628
In
ID:0xFFF
300MHz
DDR3
Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
mach:2
OUT
Boot1 Release Time: May 13 2019 17:02:59, version: 2.56
ChipType = 0xc, 407
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=7460MB
FwPartOffset=2000 , 0
StorageInit ok = 159481
SecureMode = 0
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x63337df8 signature is wrong
recovery gpt...
GPT 0x63337df8 signature is wrong
recovery gpt fail!
LOADER Check OK! 0x61000000, 289867
TOS    Check OK! 0x68400000, 355792
Enter Trust OS
INF [0x0] TEE-CORE:init_primary_helper:377: Initializing (1.1.0-290-gac72e46-dev #1 Tue May  8 00:52:17 UTC 2018 arm)

INF [0x0] TEE-CORE:init_primary_helper:378: Release version: 1.9

INF [0x0] TEE-CORE:init_primary_helper:379: Next entry point address: 0x61000000

Other Android that booted:

DDR Version V1.06 20170902_dbg
In
300MHz
DDR3
Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
mach:2
OUT
Boot1 Release Time: Nov  9 2017 15:32:49, version: 2.47
ChipType = 0xc, 380
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
SdmmcInit=0 2
StorageInit ok = 64849
SecureMode = 0
Code check OK! theLoader 0x60000000, 78641
Code check OK! theLoader 0x68400000, 89203
Enter Trust OS
INF TEE-CORE:init_primary_helper:319: Initializing (1.0.1-72-gf230aa2 #2 Fri Sep 29 10:22:10 UTC 2017 arm)
INF TEE-CORE:init_primary_helper:320: Release version: 2.0
INF TEE-CORE:init_teecore:79: teecore inits done


U-Boot 2014.10-RK322X-06-02501-g0dab20b-dirty (Dec 06 2017 - 18:43:48)

CPU: rk322x
cpu version = 3
CPU's clock information:
    arm pll = 600000000HZ
    periph pll = 600000000HZ
    ddr pll = 600000000HZ
    codec pll = 500000000HZ
Board:  Rockchip platform Board
Uboot as second level loader
DRAM:  Found dram banks: 1
Adding bank:0000000060000000(0000000040000000)
Reserve memory for trust os.
dram reserve bank: base = 0x68400000, size = 0x00100000
128 MiB
GIC CPU mask = 0x00000001
rk dma pl330 version: 1.4
remotectl v0.1
pwm freq=0x11e1a3
pwm_freq_nstime=0x355
SdmmcInit = 0 20
SdmmcInit = 2 0
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659bb94c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659bbb4c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659cb74c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659cb94c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659bb94c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659bbb4c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659cb74c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659cb94c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659bb94c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659bbb4c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659cb74c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659cb94c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659bb94c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659bbb4c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659cb74c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659cb94c
ERROR: v7_dcache_inval_range - start address is not aligned - 0x659bb94c
ERROR: v7_dcache_inval_range - stop address is not aligned - 0x659cb94c
storage init OK!
Using default environment

GetParam
Load FDT from resource image.
can't find dts node for fixed
No pmic detect.
DRAM: dram freq:300MHz
SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 2017-12-06#2.37
empty serial no.
normal boot.
checkKey
vbus = 1
board_fbt_key_pressed: ir_keycode = 0x0, frt = 0
no fuel gauge found
no fuel gauge found
can't find power_ctr node for lcdc0
HDMI: no pull up gpio
can't find dts node for deviceinfo
rk_hdmi_register:fail to read deviceinfo
hdmi baseparamer 0x0@0-0
left = 0, right = 0, top = 0, bottom = 0, overscan = 0
panel->left = 100 , panel->right = 100 ,panel->top = 100, panel->bottom = 100, panel->overscan = 100
tve baseparamer 0x0@0-0
[EDID-EXTEND] It is a  CEA 861 Series Extension.
no baseparametr,find best edid mode,vic=16
hdmi_dev->video.vic is 16
hdmi_dev_config_video vic 16 color_output 3 color_output_depth 8
pixel clk is 148500000 tmds clk is 148500000
hsync_pol 1 vsync_pol 1
[HDMI] sucess output HDMI.
read logo on state from dts [1]
no fuel gauge found
checkKey
vbus = 1
board_fbt_key_pressed: ir_keycode = 0x0, frt = 0
Hit any key to stop autoboot:  0
load fdt from resouce.
ERROR: [get_entry_ram]: Cannot find logo_kernel.bmp!
Secure Boot state: 0
kernel   @ 0x62000000 (0x006b86c0)
ramdisk  @ 0x65bf0000 (0x001678c4)
bootrk: do_bootm_linux...
   Loading Device Tree to 65600000, end 65614966 ... OK
Add bank:0000000060000000, 0000000008400000
Add bank:0000000068500000, 0000000037b00000
WARNING: could not set reg FDT_ERR_BADOFFSET.

Starting kernel ...

fabiobassa maybe you have logs from succesfull linux boot ?
Thanks.

[xwx]

Hi,
Could boot linux, what I understood that board shouldn't have any loader, then it will normaly boot with sdcard, and also loader and and u-boot from respeaker are specific to that board(or type of the boards) otherwise you need to compile them from sources.

[fabiobassa]

xwx

Ok you right:
Look the first two logs they are speaking of GPT while the android that is booting speaks of rkparameters.

Regarding booting from SD , yes must no liader WT ALL or you must ground pin click of nand to ground ( dangerous thought)

[xwx]

No need to ground simply erase internal flash(can be dome with Android rk tools) and it will boot from SD. The first log with GTP is from Android 9 it is interesating, second log is using ondoard loader that triest to boot SD but it's waiting for different partitioning...I think everything depends on loader on Optee_os part.

[fabiobassa]

xwx
You so right that can't imagine.
Android 9 is not booting on those boards ( yet) but partitioning you can change in maskrom mode.
I am not home unyun Monday but I will put here some got partitions and some ideas for booti g from sd