December 4, 20232 yr Author after check firefly roc pc dts, they almast same as my dump from jianpian box. I have done the develop, but I still don't understand why WIFI only works once. and BT still not work. I may need to disable WIFI BT in original OS, and try again.
December 5, 20232 yr Delete this: wifi@1 { compatible = "brcm,bcm4329-fmac"; reg = < 0x01 >; interrupt-parent = < 0x63 >; interrupts = < 0x0a 0x04 >; interrupt-names = "host-wake"; pinctrl-names = "default"; pinctrl-0 = < 0x64 >; phandle = < 0xf8 >; }; Edited December 5, 20232 yr by maka
December 5, 20232 yr Author 2 hours ago, maka said: Delete this: wifi@1 { compatible = "brcm,bcm4329-fmac"; reg = < 0x01 >; interrupt-parent = < 0x63 >; interrupts = < 0x0a 0x04 >; interrupt-names = "host-wake"; pinctrl-names = "default"; pinctrl-0 = < 0x64 >; phandle = < 0xf8 >; }; why? I check other rk3566 board with this wifi/bt chip, also don't have wifi@1. if I remove this would bt works?
December 5, 20232 yr I think it will work if you have firmware and loads. Maybe that refuses. dmesg | grep -i error '
December 9, 20232 yr Author wifi works, with remove sd-uhs-sdr104; or change it to sd-uhs-sdr50; but bt still not work: [ 23.521445] Bluetooth: hci1: BCM: failed to write update baudrate (-110) [ 23.522130] Bluetooth: hci1: Failed to set baudrate [ 25.541403] Bluetooth: hci1: command 0x0c03 tx timeout
December 11, 20232 yr Quote wifi works, with remove sd-uhs-sdr104; or change it to sd-uhs-sdr50; I see , you have inherited wrong nodes from your github downloaded file that are not present in firefly or box-demo dtbs. Maybe you have to use these ones as reference.
December 12, 20232 yr Author a mistake happens in u-boot, I forget to change/add boot device, only MMC1 is boot device, but MMC1 is wifi in dts. MMC2 is emmc. I have to buy a male-to-male usb cable and a rom. (less than 1RMB together) when I write the post, I suddenly realize I don't need to buy a rom, I can use RKdevtool to flash the uboot only!! let m try it when usb cable arrive.
December 13, 20232 yr Author @maka do you know how to drive front LED dispaly, it can display "boot", "WIFI" and time.
December 13, 20232 yr I don't use the display because I tinker just for fun 🙃 I believe you must have nodes for vfd and drive the display with a service like openvfd. Here is one related for an rk3566 android box. }; meson-vfd { compatible = "amediatech,aml_vfd"; dev_name = "meson-vfd"; vfd_data_gpio = <0x6d 0x14 0x00>; vfd_clock_gpio = <0x6d 0x15 0x00>; vfd_stb_gpio = <0x6d 0x16 0x00>; status = "okay"; };
December 19, 20232 yr Author my uboot bootable, but with some wrong config, 1, board is wrong 2, sysboot not support.
December 20, 20232 yr Author done, with my uboot, it boot automatically to debian-13. but for now: ethernet, bt are enabled but not work. openvfd, LED, IR receive are not enabled. next step fix those.
December 20, 20232 yr Author Quote ning@Jianpian:~$ uname -a Linux Jianpian 6.5.0-5-arm64 #1 SMP Debian 6.5.13-1 (2023-11-29) aarch64 GNU/Linux ning@Jianpian:~$ journalctl -b 12月 20 15:03:51 Jianpian kernel: Booting Linux on physical CPU 0x0000000000 [0x412fd050] 12月 20 15:03:51 Jianpian kernel: Linux version 6.5.0-5-arm64 (debian-kernel@lists.debian.org) (gcc-13 (Debian 13.2.0-7) 13.2.0, GNU ld (GN> 12月 20 15:03:51 Jianpian kernel: KASLR disabled due to lack of seed 12月 20 15:03:51 Jianpian kernel: Machine model: Rockchip RK3566 JianPian 8G TV Box ning@Jianpian:~$ free -m total used free shared buff/cache available 内存： 7689 257 7432 1 150 7431 交换： 0 0 0 ethernet fixed. almost done.
December 21, 20232 yr Author Uboot: https://github.com/zhangn1985/u-boot/tree/jianpian kernel: https://github.com/zhangn1985/linux-stable/tree/jianpian
December 22, 20232 yr Author my kernel saves the dts for jianpian. Vendor dts for bluetooth wireless-bluetooth { pinctrl-names = "default\0rts_gpio"; pinctrl-0 = <0x13c>; clock-names = "ext_clock"; clocks = <0x138 0x01>; BT,wake_gpio = <0x13a 0x11 0x00>; BT,reset_gpio = <0x13a 0x0f 0x00>; uart_rts_gpios = <0x13a 0x0d 0x01>; compatible = "bluetooth-platdata"; BT,wake_host_irq = <0x13a 0x10 0x00>; pinctrl-1 = <0x13d>; status = "okay"; phandle = <0x1e7>; }; pinctrl-0, pinctrl-1 and uart_rts_gpio are decription for gpio2 RK_PB5, which is uart1 rtsn pin. phandle <0x13a> is gpio2. My mainline dts for bluetooth: &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1m0_xfer &uart1m0_ctsn &uart1m0_rtsn>; status = "okay"; uart-has-rtscts; bluetooth { compatible = "brcm,bcm43438-bt"; clocks = <&rk809 1>; clock-names = "lpo"; device-wakeup-gpios = <&gpio2 RK_PC1 GPIO_ACTIVE_HIGH>; host-wakeup-gpios = <&gpio2 RK_PC0 GPIO_ACTIVE_HIGH>; shutdown-gpios = <&gpio2 RK_PB7 GPIO_ACTIVE_HIGH>; pinctrl-names = "default"; pinctrl-0 = <&bt_host_wake_l &bt_wake_l &bt_enable_h>; vbat-supply = <&vcc3v3_sys>; vddio-supply = <&vcca1v8_pmu>; }; }; but bluetooth failed: Quote [ 14.433949] Bluetooth: hci0: command 0xfc18 tx timeout [ 22.498017] Bluetooth: hci0: BCM: failed to write update baudrate (-110) [ 22.498690] Bluetooth: hci0: Failed to set baudrate [ 24.514009] Bluetooth: hci0: command 0x0c03 tx timeout [ 32.737999] Bluetooth: hci0: BCM: Reset failed (-110)
February 15, 20242 yr On 12/22/2023 at 5:41 AM, ning said: My mainline dts for bluetooth: good Job! you was working hard for so long. rk3566-jianpian.dts
September 16Sep 16 @Astlin I'm working on update https://github.com/armbian/build/blob/main/config/boards/jp-tvbox-3566.tvb I will generate some images for you to test since you are the only here that already have a JP-TV box
September 18Sep 18 @Astlin This U-boot was updated on PR: https://github.com/armbian/build/pull/10723 Test Image: https://drive.google.com/file/d/1QvW1Gb-Ik7TTOT9DGVJAHyj_RGm5LcTb/view?usp=drive_link
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.