flatmax / buildroot.rockchip Goto Github PK

Hi!
I'm trying to build the buildroot, i'm using Ubuntu 22.04 running on WSL, Windows 11.
And i get this error:

BINMAN .binman_stamp Wrote map file './simple-bin.map' to show errors binman: Node '/binman/simple-bin/fit': subnode 'images/@atf-SEQ': Failed to read ELF file: Python: No module named 'elftools' make[1]: *** [Makefile:1115: .binman_stamp] Error 1

I did every step from the README, but I can't make it work.

Hope any one can help me.
Thank you.

Hi there, first thanks for your efforts. I'm attempting to build an image for the rock pi s. I found the missing .bin files from the TODO here:

https://github.com/radxa/rkbin/tree/master/bin/rk33

and managed to get it to produce a sdcard.img. However, when I put that on an sdcard, no boot activity happens. I have a usb -> uart bridge plugged into the appropriate pins (at least for the radxa stock debian image).

This is on v12 hardware.

I started with buildroot 2022.02.1 and 80af258 of this repo.

Any suggestions would be very welcomed.

1.I meet the error "[email protected]: Permission denied (publickey)" when running "git clone [email protected]:flatmax/buildroot.rockchip.git buildroot.rockchip.ext"
I choose to run "git clone https://github.com/flatmax/buildroot.rockchip.git buildroot.rockchip.ext"
2.I meet the error when I run "make rkbin". Makefile.legacy:9: *** "You have legacy configuration in your .config! Please check your configuration."。
I guess it is because of the version of the buildroot but I can't correct it.

When the lib mraa is installed with apt it receives this MRAA version (v2.1.0-22-gb24cd50) on the Radxa ROCK Pi S.

• When done using buildroot, the version looks like this. Version 2022.02.1 on Unknown platform

code

#include <iostream>
#include <mraa.hpp>

int main() {
    // Inicializar o barramento I2C
    mraa::I2c i2c(0);  // O número 0 refere-se ao barramento I2C 0

    // Verificar se o barramento I2C foi inicializado corretamente
    if (!i2c.address(0x0A)) {
        std::cerr << "Erro ao inicializar o barramento I2C" << std::endl;
        return 1;
    }

    // Ler um byte do dispositivo no endereço 0x0A
    uint8_t dataRead;
    if (i2c.read(&dataRead, 1) != mraa::SUCCESS) {
        std::cerr << "Erro ao ler do dispositivo I2C" << std::endl;
        return 1;
    }

    std::cout << "Valor lido: " << static_cast<int>(dataRead) << std::endl;

    return 0;
}

• The code above runs normally in the debian version, in the version with buildroot I have this error

# ./i2c-list 
terminate called after throwing an instance of 'std::invalid_argument'
  what():  Invalid i2c bus
Aborted

Using, it ok

# i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- 0a -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

I don't know if it's appropriate to open an issue here, but I would like to compile this mraa lib to run on my image. can you help me ?

CM3 crashes at memory intensive programs. Seems DDR controller is missing or misconfigured. dmc is not working

See this thread I made months ago with issue and temporary solution:
https://forum.radxa.com/t/buildroot-image-crashes-at-high-ram-usage-possible-u-boot-dtb-issue/18889/5

I try to build on radxa rock 3a, but failed.
I followed the instructions, in the step "Now build buildroot as per usual", can't finish make.

problem 1:
remote: Repository not found.
fatal: 仓库 'https://github.com/rockchip-linux/device-custom.git/' 未找到
...
This is the second time in a row; bailing out

problem 2:
--2022-02-27 19:54:59-- http://sources.buildroot.net/rkdevice-0fe366cf14a6d5d552a5bddbc7b8ff58260ae6e6-br1.tar.gz
正在解析主机 sources.buildroot.net (sources.buildroot.net)... 104.26.1.37, 104.26.0.37, 172.67.72.56, ...
正在连接 sources.buildroot.net (sources.buildroot.net)|104.26.1.37|:80... 已连接。
已发出 HTTP 请求，正在等待回应... 404 Not Found

It seems that that repository and that file don't exist. How can I fix this problem?

Hi there, built this successfully on WSL2 (Win11) today but have been unable to boot from SD card. Could this be an issue with the flashing mechanism? Why do the instructions state to unmount the disk before using dd?

As I am developing in WSL2 I flashed the sdcard.img using BalenaEtcher (and also tried with Rufus, and several SD cards). I can confirm that the Rock 3A is working both with Ubuntu and Debian images provided by Radxa.

Thanks for this repo :)

I followed the steps to build, however I have the same result for the rk3308 chip and the others.

➜  $ tree -L 1
├── buildroot
└── buildroot.rockchip.ext

rock pi S tested with version : git checkout 2022.02.1 ok

exec command

➜  $ source buildroot.rockchip.ext/setup.rk3308.sh buildroot          
can't find the file /home/castro/kernel-rock/configs/rk3308_defconfig
please fix this script

as defconfig already exists in buildroot, it worked. I already apologize if I'm doing something wrong.

following the instruction in READE for build rock5b, got below error

  CC      examples/standalone/hello_world.o
  LD      examples/standalone/hello_world
  OBJCOPY examples/standalone/hello_world.srec
  OBJCOPY examples/standalone/hello_world.bin
  LDS     u-boot.lds
  LD      u-boot
/root/buildroot/output/host/bin/aarch64-buildroot-linux-uclibc-ld.bfd: arch/arm/mach-rockchip/built-in.o: in function `fdt_fixup_modules':
/root/buildroot/output/build/uboot-stable-5.10-rock5/arch/arm/mach-rockchip/rk3588/rk3588.c:1164: undefined reference to `_u_boot_list_2_driver_2_rockchip_otp'
/root/buildroot/output/host/bin/aarch64-buildroot-linux-uclibc-ld.bfd: arch/arm/mach-rockchip/built-in.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `_u_boot_list_2_driver_2_rockchip_otp' which may bind externally can not be used when making a shared object; recompile with -fPIC
/root/buildroot/output/build/uboot-stable-5.10-rock5/arch/arm/mach-rockchip/rk3588/rk3588.c:1164:(.text.rk_board_dm_fdt_fixup+0xc): dangerous relocation: unsupported relocation
/root/buildroot/output/host/bin/aarch64-buildroot-linux-uclibc-ld.bfd: /root/buildroot/output/build/uboot-stable-5.10-rock5/arch/arm/mach-rockchip/rk3588/rk3588.c:1164: undefined reference to `_u_boot_list_2_driver_2_rockchip_otp'
make[2]: *** [Makefile:1284: u-boot] Error 1
make[1]: *** [Makefile:461: __build_one_by_one] Error 2
make[1]: Leaving directory '/root/buildroot/output/build/uboot-stable-5.10-rock5'
make: *** [boot/uboot/uboot.mk:533: /root/buildroot/output/build/uboot-stable-5.10-rock5/.stamp_dotconfig] Error 2

Not sure why, but this system works for the rock3a v1.3. It doesn't seem to boot for the rock3a v1.31

Hi, is it possible to have buildroot on Rock Zero 3W?
I wasn't able to even on the Rock 3A, but I would need the radxa Zero 3W hardware, a pair, for a project that needs buildroot. But if it is not possible to compile it for this device, then I will have to think of something else.

Thank you

Build can`t be finished because https://github.com/rockchip-linux/tools.git does not exist anymore.

Hi , I am working on a Banana Pi R2-Pro. I am getting the following error on the serial console at boot:
"...

Trying to boot from MMC2
No misc partition
spl: partition error
Trying fit image at 0x4000 sector

Verified-boot: 0

Checking uboot 0x00200000 ... sha256(b8816e87e3...) + OK

Checking fdt 0x00309860 ... sha256(d32827d3ac...) + OK

"

This is after it tries to read the (not useful) info on the emmc (MMC1).
Note however, that this is much farther than I could get using anything from SinoVOIP.

Any advice or assistance would be most welcome.

Thanks,

Erik

I'm trying to build the quartz64_defconfig, but building linux fails because it cant find libyaml. I have tried installing and uninstalling libyaml-dev on the host. I'm not sure what else to do.

dtc needs libyaml for DT schema validation support. Install the necessary libyaml development package

I'm using a Radxa CM3 module on a Raspberry Pi CM4 IO Board.
I built the image as described, and flashed it onto the internal eMMC.
The board starts U-Boot SPL, but then hangs after verifying the checksums:

[Skip DDR Initialization Block]

U-Boot SPL board init
U-Boot SPL 2017.09 (Sep 13 2022 - 17:35:53)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
TryMMC error: The cmd index is 1, ret is -110
Card did not respond to voltage select!
mmc_init: -95, time 10
spl: mmc init faileerror: -95
Trying to boot from MMC1
## Verified-boot: 0
## Checking uboot 0x00a00000 ... sha256(87fbe2d509...) + OK
## Checking fdt 0x00b2e3e8 ... sha256(2154df9e4a...) + OK
## Checking optee 0x08400000 ... sha256(b8cddafab0...) + OK

I also tried to write the image onto an sdcard, but that didn't work as well (maybe a different dtbo is needed). Even if it worked on an external sdcard, I would like it to boot from the internal eMMC.