Giter Site home page Giter Site logo

radxa / meta-radxa Goto Github PK

View Code? Open in Web Editor NEW

This project forked from nishantpoorswani/meta-radxa

8.0 8.0 18.0 929 KB

OpenEmbedded BSP Layer for the Radxa boards

License: GNU Lesser General Public License v3.0

BitBake 16.51% Batchfile 6.01% Makefile 0.34% C 64.08% Shell 5.77% NASL 0.53% Pascal 5.72% PHP 0.20% C++ 0.84%

meta-radxa's Introduction

Meta-radxa

Table of contents

  1. Introduction
  2. Dependencies
  3. List of Radxa Boards supported
  4. Using the meta-radxa layer
    1. Step 1:Fetching the Source
    2. Step 2:Setting up the Environment
    3. Step 3:Bblayers.conf Setup
    4. Step 4:Local.conf Setup
    5. Step 5:Building the Image
  5. Serial Console
  6. Login Details
  7. Networking
    1. Wifi Connectivity
    2. Bluetooth Connectivity
  8. Release Info
  9. Change Log
  10. Contributing
  11. Reporting Bugs
  12. Maintainers

Introduction

The OpenEmbedded/Yocto Project BSP layer for the Radxa machines

Dependencies

The meta-radxa layer depends on:

URI: git://git.yoctoproject.org/poky
branch: dunfell

URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe meta-networking meta-python meta-multimedia meta-gnome meta-xfce
branch: dunfell

List of Radxa Boards supported

  1. RockPi-4A
  2. RockPi-4B
  3. RockPi-4C
  4. RockPi-E
  5. RockPi-N10
  6. RockPi-PX30
  7. RockPi-S
  8. Radxa-Zero

Using the meta-radxa layer

Step 1: Fetching the source

Fetch the source using the commands given below:

~ $ mkdir yocto
~ $ cd yocto
~/yocto $ git clone --depth 1 git://git.yoctoproject.org/poky -b dunfell
~/yocto $ cd poky
~/yocto/poky $ git clone --depth 1 git://git.openembedded.org/meta-openembedded.git -b dunfell
~/yocto/poky $ git clone --depth 1 https://github.com/radxa/meta-radxa.git -b dunfell
~/yocto.poky $ git clone --depth 1 https://github.com/YoeDistro/meta-python2.git -b dunfell

Step 2: Setting up the Environment

~/yocto/poky $ source oe-init-build-env

Step 3: bblayers.conf Setup

  • You can simply copy the bblayers.conf.sample present in meta-radxa/conf folder to the build/conf folder and rename it to bblayers.conf
~/yocto/poky/build $ cp ../meta-radxa/conf/bblayers.conf.sample conf/bblayers.conf
OR
  • Add the layers manually as given below to the bblayers.conf in the build/conf folder
  ${TOPDIR}/../meta \
  ${TOPDIR}/../meta-poky \
  ${TOPDIR}/../meta-yocto-bsp \
  ${TOPDIR}/../meta-openembedded/meta-oe \
  ${TOPDIR}/../meta-openembedded/meta-networking \
  ${TOPDIR}/../meta-openembedded/meta-python \
  ${TOPDIR}/../meta-openembedded/meta-multimedia \ 
  ${TOPDIR}/../meta-openembedded/meta-gnome \
  ${TOPDIR}/../meta-openembedded/meta-xfce \
  ${TOPDIR}/../meta-python2 \
  ${TOPDIR}/../meta-radxa \

Step 4: local.conf Setup

  • You can simply copy the local.conf.sample present in meta-radxa/conf folder to the build/conf folder and rename it to local.conf and uncomment the machine for which you want to build an image
~/yocto/poky/build $ cp ../meta-radxa/conf/local.conf.sample conf/local.conf
~/yocto/poky/build $ nano conf/local.conf
OR
  • Add the following lines in the build/conf/local.conf
MACHINE ?= "xxxx"
DISTRO_FEATURES_append = " pam systemd x11"
VIRTUAL-RUNTIME_init_manager = "systemd"
PACKAGECONFIG_append_pn-systemd = " resolved networkd"
DISTRO_FEATURES_remove = "wayland"

Replace xxxx with the machine you want to build the image for. All supported machines can be found in meta-radxa/conf/machine.

Step 5: Building the Image

  • If you wish to build a minimal image use the command given below:
~/yocto/poky/build $ bitbake -k radxa-minimal-image
OR
  • If you wish to build a console image use the command given below:
~/yocto/poky/build $ bitbake -k radxa-console-image
OR
  • If you wish to build a desktop image use the command given below:
~/yocto/poky/build $ bitbake -k radxa-desktop-image

At the end of a successful build, you should have a gpt.img image in build/tmp/deploy/images/MACHINE/ folder. The gpt.img can be directly flashed on the sd-card

Serial Console

The Serial Console for RockPi-4, RockPi-E and RockPi-N10 is enabled on UART-2. The Serial Console for RockPi-S is enabled on UART-0.

Helpful Links:

Login Details

Username: root
Password: rock

Networking

Network Devices available:

  • Wifi
  • Ethernet
  • Bluetooth

Wifi Connectivity

  • Using Commandline Based GUI(nmtui) [Available on console and desktop images]

nmtui is a curses based GUI. You can start it by running the following command:

nmtui
  • Using Commandline Utility(nmcli) [Available on console and desktop images]

nmcli is a command-line tool for controlling NetworkManager and reporting network status.

List available devices

nmcli dev

Turn on Wifi

nmcli r wifi on

Scanning different devices

nmcli dev wifi

Connect to WiFi Hotspot

nmcli dev wifi connect "SSID" password "PASSWORD"

Note:You need to replace “SSID” and “Password” with your actual WiFi’s SSID and password.

Bluetooth Connectivity

  • Bluetooth on RockPi-4B/RockPi-4C

Activating bluetooth:

hciconfig hci0 up

Check Bluetooth device:

 $ hciconfig
 hci0:   Type: Primary  Bus: UART
         BD Address: 43:45:C5:00:1F:AC  ACL MTU: 1021:8  SCO MTU: 64:1
         UP RUNNING 
         RX bytes:876 acl:0 sco:0 events:62 errors:0
         TX bytes:4755 acl:0 sco:0 commands:62 errors:0
  • Bluetooth on RockPi-E

Manual setup for bluetooth:

Bluetooth is activated by default on the RockPi-E

Check Bluetooth device:

 $ hciconfig
 hci0:   Type: Primary  Bus: USB
         BD Address: 74:EE:2A:55:23:F7  ACL MTU: 1021:8  SCO MTU: 255:12
         UP RUNNING 
         RX bytes:40357 acl:34 sco:0 events:814 errors:0
         TX bytes:216782 acl:379 sco:0 commands:101 errors:0
  • Bluetooth on RockPi-N10

Activating bluetooth:

hciconfig hci0 up

Check Bluetooth device:

 $ hciconfig
 hci0:   Type: Primary  Bus: UART
         BD Address: 22:22:70:B2:10:6F  ACL MTU: 1021:8  SCO MTU: 255:12
         UP RUNNING 
         RX bytes:1399 acl:0 sco:0 events:45 errors:0
         TX bytes:3458 acl:0 sco:0 commands:45 errors:0
  • Bluetooth on RockPi-S

Activating bluetooth:

hciconfig hci0 up

Check Bluetooth device:

 $ hciconfig
 hci0:   Type: Primary  Bus: UART
         BD Address: 22:22:70:B2:10:6F  ACL MTU: 1021:8  SCO MTU: 255:12
         UP RUNNING 
         RX bytes:1399 acl:0 sco:0 events:45 errors:0
         TX bytes:3458 acl:0 sco:0 commands:45 errors:0

Release Info

  1. RockPi-4
  • Kernel version: 4.4.154-109-b04eccb4588e333bdaf3ba7e6e4186d2ebe53770
  • U-Boot version: 2017.09-04d66f4b45a47531b5ff6cdbddcdc2cc35fa7aea
  1. RockPi-E
  • Kernel version: 4.4.194-12-615ae743115011bbe1cd1edc5c9118bf95527f54
  • U-Boot version: 2019.10-7b93f1b8bce4106266d4a38dde96fd8080faccea
  1. RockPi-N10
  • Kernel version: 4.4.167-c36a21e2be755919e8b406069206e67126b7e712
  • U-Boot version: 2017.09-7c49a7da79caf2f68bc1074dfa21864d7f23b9e1
  1. RockPi-PX30
  • Kernel version: 4.4.189-dc47906e88166ae315f0472743de4d80f2bea786
  • U-Boot version: 2017.09-cfc37de87bc064b2d6d384566e24c5e4245f113a
  1. RockPi-S
  • Kernel version: 4.4.143-55-6b7accbc999b6caa8ef603b9d904c99694d0bf41
  • U-Boot version: 2017.09-233a23e3ed0b3e5250253ee455c3c5df2080f99c

Change Log

  • Added board support for RockPi-N10
  • Added board support for RockPi-PX30
  • Added board support for RockPi-4A
  • Added board support for RockPi-4C
  • RockPi-4 Kernel updated to 4.4.154-109-b04eccb4588e333bdaf3ba7e6e4186d2ebe53770
  • RockPi-4 U-Boot branch updated from stable-4.4-rockpi4 to rk3399-pie-gms-express-baseline
  • RockPi-4 U-Boot updated to 2017.09-04d66f4b45a47531b5ff6cdbddcdc2cc35fa7aea
  • RockPi-4 boards support SPI + NVME booting
  • RockPi-4b dtb changed from rockpi-4b-linux.dtb to rk3399-rock-pi-4b.dtb
  • RockPi-S Kernel updated to 4.4.143-55-6b7accbc999b6caa8ef603b9d904c99694d0bf41
  • RockPi-S U-Boot updated to 2017.09-c93a0fc70993c12e605b1312577252ca9cdec6c8
  • RockPi-S and RockPi-E gpt images have now been updated to use the 2 partition instead of the tradition 5 partition
  • Use ttySx as debuger console instead of ttyFIQ0 for RockPi-S and RockPi-E
  • Major Reorganization in U-Boot recipes. New structure will make it easier for adding new boards
  • Added recipe for making desktop images
  • Added recipe for setting up BT firmware and driver at boot for Rockpi-4, RockPi-E, RockPi-N10 and RockPi-S
  • Added recipe for kernel-headers, file-system resize at boot, mraa and create-ap
  • Added board support for Radxa-Zero

Contributing

Please use github for pull requests: https://github.com/nishantpoorswani/meta-radxa/pulls

Reporting bugs

The github issue tracker (https://github.com/nishantpoorswani/meta-radxa/issues) is being used to keep track of bugs.

Maintainers

meta-radxa's People

Contributors

floion avatar nishantpoorswani avatar pheki avatar radxastephen avatar radxayuntian avatar stepheninvamrs avatar thanhlev avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

meta-radxa's Issues

Dunfell branch u-boot compile failure for RockPi 4B

Hi,
I am trying to build the dunfel branch. Right now I get this problem:

| pack input ./u-boot-dtb.bin
| pack file size: 999306
| crc = 0x4158999f
| pack /home/floion/builds/balena-rockpi/build/tmp/deploy/images/rockpi-4b-rk3399/u-boot.img success!
| Image Type:   Rockchip RK33 (SD/MMC) boot image
| Data Size:    73728 bytes
| E: [mergetrust] filter_elf radxa-binary/rk3399_bl31_v1.26.elf file failed
| merge failed!
| out:trust.img
| WARNING: exit code 255 from a shell command.

Do you know if we need to update the rkbin binaries too? Is the branch compiling for you?

Newer kernel version

Hello,

Are there any plans supporting newer kernel and mesa version for Rock Pi 4 models. Currently meta-radxa is using downstream linux 4.4 and mesa 20.0.2, which is 2 years old.

Best regards!

Yocto kirkstone support

Hi,

What are your plans for supporting the newest LTS release of Yocto (kirkstone) in this meta-layer?

yocto build boot baudrate

I've build dunfell release

bitbake radxa-minimal-image

and connect terminal to UART2

at boot time there are garbage symbols
I connect oscilloscope and found bits duration about 660 ns, it is 1.52 Mbps. Is it OK?
It is not standard baudrate.

After boot with minimal image I see console on the HDMI display, but I have not connection via UART2.

GPU support

meta-rockchip, which looks to be geared toward the rockchip EVBs instead of RADXA's board, has support for libmali. Why does that not exist in meta-radxa? We cannot use the GPU when building with yocto without support for the Mali-G52 HW. Please add this support.

Yocto ROCK 5 support

Hi, will you be supporting the ROCK 5 anytime soon? @jack-ma, could you possibly please add this to the to-do list as well?

Would be very grateful if you could do this

Thanks!

I2C problems

I followed the instructions to build a yocto dunfell image for a Rockchip Pi 4b.

I build a console image
~/yocto/poky/build $ bitbake -k radxa-console-image

Testing i2c without connecting any i2c slaves get the following results:

i2cdetect -l  
i2c-0	i2c       	rk3x-i2c                        	I2C adapter
i2c-1	i2c       	rk3x-i2c                        	I2C adapter
i2c-9	i2c       	DesignWare HDMI                 	I2C adapter

i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: UU UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --  

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

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

If I connect some i2c-slaves, the result is exactly the same.

The i2c-address 0x18 should be shown for the connected sensor.

What's going wrong? Do I have to activate some settings and if yes where?

do_image_rockchip_radxa_gpt_img fails

I try bitbake -k radxa-desktop-image and bitbake -k radxa-mininal-image. Result is the same.

ERROR: radxa-desktop-image-1.0-r0 do_image_rockchip_radxa_gpt_img: Execution of '/home/.../Yocto_Radxa/dunfell_ext/tmp/work/rockpi_4b_rk3399-poky-linux/radxa-desktop-image/1.0-r0/temp/run.do_image_rockchip_radxa_gpt_img.1772092' failed with exit code 127
ERROR: Logfile of failure stored in: /home/.../Yocto_Radxa/dunfell_ext/tmp/work/rockpi_4b_rk3399-poky-linux/radxa-desktop-image/1.0-r0/temp/log.do_image_rockchip_radxa_gpt_img.1772092
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: 893152.000000 = 687040 * 1.300000
| DEBUG: 893152.000000 = max(893152.000000, 65536)[893152.000000] + 0
| DEBUG: 893152.000000 = int(893152.000000)
| DEBUG: 893152 = aligned(893152)
| DEBUG: returning 893152
| DEBUG: Python function set_image_size finished
| DEBUG: Executing python function extend_recipe_sysroot
...
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_image_rockchip_radxa_gpt_img
| 0+0 records in
| 0+0 records out
| 0 bytes copied, 5.569e-05 s, 0.0 kB/s
| Warning: The resulting partition is not properly aligned for best performance: 64s % 2048s != 0s
| Model:  (file)
| Disk /home/.../Yocto_Radxa/dunfell_ext/tmp/deploy/images/rockpi-4b-rk3399/radxa-desktop-image-rockpi-4b-rk3399-gpt.img: 1051MB
| Sector size (logical/physical): 512B/512B
| Partition Table: gpt

| pack /home/.../Yocto_Radxa/dunfell_ext/tmp/deploy/images/rockpi-4b-rk3399/u-boot.img success!
| /home/.../Yocto_Radxa/dunfell_ext/tmp/work/rockpi_4b_rk3399-poky-linux/radxa-desktop-image/1.0-r0/temp/run.do_image_rockchip_radxa_gpt_img.1772092: line 265: /home/.../Yocto_Radxa/dunfell_ext/tmp/deploy/images/rockpi-4b-rk3399/mkimage: No such file or directory
| WARNING: /home/.../Yocto_Radxa/dunfell_ext/tmp/work/rockpi_4b_rk3399-poky-linux/radxa-desktop-image/1.0-r0/temp/run.do_image_rockchip_radxa_gpt_img.1772092:1 exit 127 from '/home/.../Yocto_Radxa/dunfell_ext/tmp/deploy/images/rockpi-4b-rk3399/mkimage -n rk3399 -T rksd -d /home/.../Yocto_Radxa/dunfell_ext/tmp/deploy/images/rockpi-4b-rk3399/radxa-binary/ddr.bin /home/.../Yocto_Radxa/dunfell_ext/tmp/deploy/images/rockpi-4b-rk3399/idbloader.img'
| ERROR: Execution of '/home/.../Yocto_Radxa/dunfell_ext/tmp/work/rockpi_4b_rk3399-poky-linux/radxa-desktop-image/1.0-r0/temp/run.do_image_rockchip_radxa_gpt_img.1772092' failed with exit code 127
ERROR: Task (/media/egor/work/My_Designs/RockPi4/yocto_poky_dunfell/poky/build/../meta-radxa/recipes-core/images/radxa-desktop-image.bb:do_image_rockchip_radxa_gpt_img) failed with exit code '1'

WLAN errors on boot and after boot, Wi-Fi is not working

During the boot and three times after the boot I got in the console messages:

[   24.089010] dhd_open: Enter ffffffc0dcbd5000
[   24.089419] 
[   24.089419] Dongle Host Driver, version 1.579.77.41.2 (r)
[   24.090038] wl_android_wifi_on in 1
[   24.090365] wl_android_wifi_on in 2: g_wifi_on=0
[   24.090786] wifi_platform_set_power = 1
[   24.091136] ======== PULL WL_REG_ON(-1) HIGH! ========
[   24.091605] [WLAN_RFKILL]: rockchip_wifi_power: 1
[   24.092125] [WLAN_RFKILL]: wifi turn on power. -1
[   24.396183] sdio_reset_comm():
[   24.412326] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[   24.432018] mmc_host mmc2: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0)
[   24.493068] sdio_read_cis: 5 callbacks suppressed
[   24.493510] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[   24.500225] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[   24.506988] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[   24.518871] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[   24.533432] mmc2: queuing unknown CIS tuple 0x81 (9 bytes)
[   24.747401] mmc_host mmc2: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[   24.852774] dwmmc_rockchip fe310000.dwmmc: Successfully tuned phase to 101
[   24.853471] sdioh_start: set sd_f2_blocksize 256
[   24.854487] 
[   24.854487] 
[   24.854487] dhd_bus_devreset: == WLAN ON ==
[   24.855325] F1 signature read @0x18000000=0x15294345
[   24.860348] F1 signature OK, socitype:0x1 chip:0x4345 rev:0x9 pkg:0x2
[   24.861763] DHD: dongle ram size is set to 819200(orig 819200) at 0x198000
[   24.862465] dhd_bus_set_default_min_res_mask: Unhandled chip id
[   24.863245] dhd_conf_read_config: Ignore config file /system/etc/firmware/config.txt
[   24.864064] Final fw_path=/system/etc/firmware/fw_bcm43456c5_ag.bin
[   24.864626] Final nv_path=/system/etc/firmware/nvram_ap6256.txt
[   24.865161] Final clm_path=/system/etc/firmware/clm_bcmdhd.blob
[   24.865696] Final conf_path=/system/etc/firmware/config.txt
[   24.866198] dhd_set_bus_params: set use_rxchain 0
[   24.866630] dhd_set_bus_params: set txglomsize 36
[   24.867717] dhdsdio_download_code_file: Open firmware file failed /system/etc/firmware/fw_bcm43456c5_ag.bin
[   24.868683] _dhdsdio_download_firmware: dongle image file download failed
[   24.869331] dhd_bus_devreset Failed to download binary to the dongle
[   24.869920] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   24.870402] dhd_wl_ioctl: returning as busstate=0
[   24.870836] dhd_dbg_detach_pkt_monitor, 2204
[   24.871224] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   24.871752] wifi_platform_set_power = 0
[   24.872220] ======== PULL WL_REG_ON(-1) LOW! ========
[   24.872693] [WLAN_RFKILL]: rockchip_wifi_power: 0
[   24.873174] [WLAN_RFKILL]: wifi shut off power.
[   24.873594] wl_android_wifi_on: Failed
[   24.873960] dhd_open : wl_android_wifi_on failed (-35)
[   24.874441] dhd_stop: Enter ffffffc0dcbd5000
[   24.874849] wl_android_wifi_off in 1
[   24.875188] wl_android_wifi_off in 2: g_wifi_on=0, on_failure=1
[   24.875748] dhd_wl_ioctl: returning as busstate=0
[   24.876268] dhd_dbg_detach_pkt_monitor, 2204
[   24.876692] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   24.877193] sdioh_disable_func_intr: error for read SDIO_CCCR_IENx : 0xffffff92
[   24.877844] wifi_platform_set_power = 0
[   24.878182] ======== PULL WL_REG_ON(-1) LOW! ========
[   24.878635] [WLAN_RFKILL]: rockchip_wifi_power: 0
[   24.879060] [WLAN_RFKILL]: wifi shut off power.
[   24.879466] wl_android_wifi_off out
[   24.879808] dhd_stop: Exit
[   24.880115] dhd_open: Exit ret=-1
[   24.881726] dhd_open: Enter ffffffc0dcbd5000
[   24.882131] 
[   24.882131] Dongle Host Driver, version 1.579.77.41.2 (r)
[   24.882735] wl_android_wifi_on in 1
[   24.883051] wl_android_wifi_on in 2: g_wifi_on=0
[   24.883459] wifi_platform_set_power = 1
[   24.883798] ======== PULL WL_REG_ON(-1) HIGH! ========
[   24.884377] [WLAN_RFKILL]: rockchip_wifi_power: 1
[   24.884802] [WLAN_RFKILL]: wifi turn on power. -1
[   25.188364] sdio_reset_comm():
[   25.204359] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[   25.224084] mmc_host mmc2: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0)
[   25.286929] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[   25.293718] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[   25.300488] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[   25.312329] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[   25.326807] mmc2: queuing unknown CIS tuple 0x81 (9 bytes)
[   25.539699] mmc_host mmc2: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[   25.740703] dwmmc_rockchip fe310000.dwmmc: Successfully tuned phase to 101
[   25.741399] sdioh_start: set sd_f2_blocksize 256
[   25.742311] 
[   25.742311] 
[   25.742311] dhd_bus_devreset: == WLAN ON ==
[   25.743148] F1 signature read @0x18000000=0x15294345
[   25.748259] F1 signature OK, socitype:0x1 chip:0x4345 rev:0x9 pkg:0x2
[   25.749769] DHD: dongle ram size is set to 819200(orig 819200) at 0x198000
[   25.750473] dhd_bus_set_default_min_res_mask: Unhandled chip id
[   25.751255] dhd_conf_read_config: Ignore config file /system/etc/firmware/config.txt
[   25.752078] Final fw_path=/system/etc/firmware/fw_bcm43456c5_ag.bin
[   25.752653] Final nv_path=/system/etc/firmware/nvram_ap6256.txt
[   25.753188] Final clm_path=/system/etc/firmware/clm_bcmdhd.blob
[   25.753722] Final conf_path=/system/etc/firmware/config.txt
[   25.754225] dhd_set_bus_params: set use_rxchain 0
[   25.754656] dhd_set_bus_params: set txglomsize 36
[   25.755685] dhdsdio_download_code_file: Open firmware file failed /system/etc/firmware/fw_bcm43456c5_ag.bin
[   25.756749] _dhdsdio_download_firmware: dongle image file download failed
[   25.757438] dhd_bus_devreset Failed to download binary to the dongle
[   25.758018] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   25.758501] dhd_wl_ioctl: returning as busstate=0
[   25.758935] dhd_dbg_detach_pkt_monitor, 2204
[   25.759324] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   25.759852] wifi_platform_set_power = 0
[   25.760331] ======== PULL WL_REG_ON(-1) LOW! ========
[   25.760790] [WLAN_RFKILL]: rockchip_wifi_power: 0
[   25.761276] [WLAN_RFKILL]: wifi shut off power.
[   25.761687] wl_android_wifi_on: Failed
[   25.762029] dhd_open : wl_android_wifi_on failed (-35)
[   25.762499] dhd_stop: Enter ffffffc0dcbd5000
[   25.762885] wl_android_wifi_off in 1
[   25.763213] wl_android_wifi_off in 2: g_wifi_on=0, on_failure=1
[   25.763751] dhd_wl_ioctl: returning as busstate=0
[   25.764247] dhd_dbg_detach_pkt_monitor, 2204
[   25.764652] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   25.765207] sdioh_disable_func_intr: error for read SDIO_CCCR_IENx : 0xffffff92
[   25.765865] wifi_platform_set_power = 0
[   25.766217] ======== PULL WL_REG_ON(-1) LOW! ========
[   25.766673] [WLAN_RFKILL]: rockchip_wifi_power: 0
[   25.767114] [WLAN_RFKILL]: wifi shut off power.
[   25.767522] wl_android_wifi_off out
[   25.768057] dhd_stop: Exit
[   25.768325] dhd_open: Exit ret=-1

During the build I've got warnings:
WARNING: .../meta-radxa/recipes-connectivity/bluetooth/bluetooth-rockpi-s.bb: Unable to get checksum for bluetooth-rockpi-s SRC_URI entry install-module-hci-uart.service: file could not be found
WARNING: .../meta-radxa/recipes-connectivity/bluetooth/bluetooth-rockpi-s.bb: Unable to get checksum for bluetooth-rockpi-s SRC_URI entry rtl8723ds-btfw-load.service: file could not be found
WARNING: .../meta-radxa/recipes-connectivity/bluetooth/bluetooth-rockpi-s.bb: Unable to get checksum for bluetooth-rockpi-s SRC_URI entry install_module_hci_uart: file could not be found
WARNING: .../meta-radxa/recipes-connectivity/bluetooth/bluetooth-rockpi-e.bb: Unable to get checksum for bluetooth-rockpi-e SRC_URI entry blacklist-bt.conf: file could not be found

Critical wireless problems with the products utilizing AW-NB197SM module

We're seeing a definite pattern on our RockPi 4B based miners which utilizes AW-NB197SM module. Local tests has shown that a firmware/driver crash happens and then the module gets disconnected from the system and doesn't return back. Here you can find the system logs of such incident attached.

aw-nb197sm-wifi-disconnection-20220320-00.log

The crash happens at 1072nd second, around 8 mins after connecting to the AP at 576th second.

After making a wired connection with the device, ip link command shows the wlan0 device is down.

3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DORMANT group default qlen 1000
    link/ether XX:XX:1d:e3:XX:XX brd ff:ff:ff:ff:ff:ff

Unfortunately module never recovers from this state and the link stays down forever if the device is not rebooted. None of the nmcli commands help to get the link back up. Even that would help, it wouldn't solve anything because our devices are working unattended and a big portion of them are working solely on wireless networks.

This is a pretty serious issue and we need all the help we can get very urgently.

Right now I'm trying to install the newest brcmfmac driver but couldn't succeed with the backports.

Here's the system info:

       _,met$$$$$gg.          rock@rockpi-4b 
    ,g$$$$$$$$$$$$$$$P.       -------------- 
  ,g$$P"     """Y$$.".        OS: Debian GNU/Linux 10 (buster) aarch64 
 ,$$P'              `$$$.     Host: ROCK PI 4B 
',$$P       ,ggs.     `$$b:   Kernel: 4.4.154-116-rockchip-g86a614bc15b3 
`d$$'     ,$P"'   .    $$$    Uptime: 11 mins 
 $$P      d$'     ,    $$P    Packages: 773 (dpkg) 
 $$:      $$.   -    ,d$$'    Shell: bash 5.0.3 
 $$;      Y$b._   _,d$P'      Terminal: /dev/pts/0 
 Y$$.    `.`"Y$$$$P"'         CPU: (6) @ 1.416GHz 
 `$$b      "-.__              Memory: 120MiB / 1926MiB 
  `Y$$
   `Y$$.                                              
     `$$b.
       `Y$$b.
          `"Y$b._

ROCK 4 SE support

Hi, will you be supporting the ROCK 4 SE anytime soon?

Thank you!

gbm_surface_create_with_modifiers not found

Hello,

I am building minimal image (bitbake -k radxa-minimal-image) for Rock pi 4b rk3399, and I am trying to run a flutter app (using meta-flutter), but there is an error:
gbm_surface_create_with_modifiers not found

Is there a way to add a support for that function?

Best regards!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.