8 8

About This Club

Running Armbian on all kinds of ARM based TV boxes. Select a topic clicking on a tab above. If you are new to Armbian for TV boxes you should start by reading the FAQ entry "Status of Armbian on TV boxes - Please read first": https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
  1. What's new in this club
  2. Hi Jock! I definetly have not read. I have not opened the box before installing armbian. My mistake. @fabiobassasend me an e-mail to charlesbauer@gmail.com with your address than I will send to you the box. Regards, Charles Bauer
  3. @Charles Bauer Apparently you did not read the first page carefully: Unbricking may be complicated, because neither me nor @fabiobassahad the chance to tinker with a board with eMCP. The problem is most probably related to memory initialization. A serial log is required for confirmation, but we already have seen a situation like that and I don't think this is different. Memory initialization is the first thing that is going to be done during bootstrap and thus, when it goes bad, the board is knocked down and requires manual intervention to get into maskrom mode. Doing this job require some skills in electronic and some non-common equipment because you need to find and ground the eMMC (eMCP in this case) clock pin. What you can do to help development is send the bricked board to @fabiobassa for him to analyze
  4. please look at page 33 @jock and a @gnusmag45 have this topic about the JWA60 memory its a eMCP Memory https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/?do=findComment&comment=124401
  5. Hi all! I have bricked my new mx9 pro! hehe I have installed armbian via stepnand and it does not show anything on the screen now. No signal! I have tried to recognize it through otg cable but windows did not detect it. Have you seen it? I am not sure if the memory is nand. During the instalation I think it has said that is. But I am not completily right. See below the photos of the board. Any help will be appreciated because I want to buy another one and try again. Thank you guy! your are awesome! Charles Bauer charlesbauer@gmail.com
  6. Stick with the autodetected (ap6334). Just follow the instructions in this last post: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318-tv-box-boards/?do=findComment&comment=127240
  7. Hello everyone, I am not having any luck with the wifi on the H96 Max X3. I see posts saying the wifi on this box work with meson-sm1-sei610-ethfix.dtb / meson-sm1-H96max-X3.dtb or h96max-x2-test-bus80-gpu-volt.dtb but they are not working for me. I did put the BCM4335C0.hcd in /lib/firmware/brcm and the driver apparently loaded. Everything else seems to be working ok. A few posts mentioned it works with kernel 5.6rc1 and 5.7 but I couldn't find those images. I tried all the images Mr. Balbes have on https://users.armbian.com/balbes150/arm-64/ and I also tried installing the headers. It works fine with Emulec and Android. I see this message below.. (brcmf_chip_cores_check: CPU core not detected) is this the reason wifi is dead? dmesg brcmfmac and these are the files in /lib/firmware/brcm If anyone can give me a hint... it would be amazing Thank you, Leco
  8. I think I have messed some things up, now it doesn't find the Wi-Fi at all. Oh well. I'll start fresh with a clean install tomorrow or the day after, fix the changes and get back to you. Should I start with ap6330 or ap6334 in /boot/armbianEnv.txt? Should I change to any of the lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt before I change the lib/firmware/brcm/brcmfmac4330-sdio.txt?
  9. Thanks @Werner. Any suggestions where I might be able to look to see what's going on with HDMI? Happy to dig/explore, just don't know where to start.
  10. Tvboxes are maintained by community members and can be different from official Armbian in any shape or form so documentation might not be matching these images.
  11. Hi, I was looking to into overlays as something that I maybe needed to fiddle with. In the documentation (https://docs.armbian.com/User-Guide_Armbian_overlays/) is points to /boot/armbianEnv.txt but this file doesn't exist. Is the equivilant file: /boot/extlinux/extlinux.conf for these images? There is only a line FDT but it seems to point to /boot/dtb/rk3188-ugoos-ut2.dtb Regards Cameron.
  12. @curse I think I spot the issue: from dmesg I see that the brcmfmac driver is using the standard nvram file, but the standard nvram does not work because it is for BCM4334 and not for AP6334. This time I propose you to paste this file over /lib/firmware/brcm/brcmfmac4330-sdio.txt, reboot and try again. If the problem is that one, it is very strange because the driver is supposed to find automatically the right nvram file, it has always worked that way but for some reason this time does not.
  13. Restored wlan-ap6334 to wlan-ap6330, then tried without changing firmware txt, then tried with the first, then with the second, with a reboot between the different changes. Still no luck on the wifi. Adding the dmesg and also the output from a journalctl command nmcli told me to try yesterday. nmcli connection up TP-Link_Guest_DC24 --ask Passwords or encryption keys are required to access the wireless network 'TP-Link_Guest_DC24'. Password (802-11-wireless-security.psk): ••••••••• Passwords or encryption keys are required to access the wireless network 'TP-Link_Guest_DC24'. Password (802-11-wireless-security.psk): ••••••••• Error: Connection activation failed: Secrets were required, but not provided Hint: use 'journalctl -xe NM_CONNECTION=3428676b-6d74-424f-bd6e-de783780a395 + NM_DEVICE=wlan0' to get more details. I haven't opened the box yet, so no photos, but I can probably do that during the week. With some luck I can continue to tinker some tomorrow, then probably Monday, I'll travel on to my mom's place (am visiting my sister now), where I won't have easy access to ethernet for the box, only WiFi, and slightly more problematic to download test files to it, but I'll manage. I guess I can use the good old manual way with a USB stick Thanks for all the help so far @jock dmesg.txt NM_CONNECTION.txt
  14. @curse I'm looking into the dtb and everything seems to be in place. I see that the dtb tells the wifi chip is ap6330, but rk3318-box detects ap6334. They are two different chips, could you please try to change wlan-ap6334 to wlan-ap6330 in /boot/armbianEnv.txt file? I see there are many clones here and there, maybe some cloned the wrong id. edit: photos of the board and logs (dmesg) are still particularly appreciated edit2: BTW the behaviour you are describing is often related to a wrong nvram. First restore wlan-ap6334 in /boot/armbianEnv.txt, then download this file and write over the existing /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt file. You may even try this other version to see if it works and/or has better performance.
  15. By using this script -> extract-dtb I managed to extract some dtb files on my mac from the tvbox-backup file Multitool created. I assume that you @jock know more than me about dtb files, any of them that are more interesting than the others? ./extract_dtb.py tvbox-backup Dumped 00_kernel, start=0 end=9267808 Dumped 01_dtbdump_rockchip,rk3328-evb.dtb, start=9267808 end=10316384 Dumped 02_dtbdump_rockchip,rk3328-evb.dtb, start=10316384 end=11364960 Dumped 03_dtbdump_rockchip,rk3328-evb.dtb, start=11364960 end=12413536 Dumped 04_dtbdump_rockchip,rk3328-evb.dtb, start=12413536 end=76546112 Dumped 05_dtbdump_Rockchip_RK3128h_liantong_board.dtb, start=76546112 end=117966848 Dumped 06_dtbdump_rockchip,rk3328-box-avb.dtb, start=117966848 end=160110592 Edit I managed to make dts files from all except 00_kernel. Looking through them, it looks like the 6th is the most interesting. It's the only one with any mention of wireless or wlan. (the relevant parts, copy/pasted) wireless-bluetooth { uart0-gpios { rockchip,pins = <0x01 0x0a 0x00 0x7e>; phandle = <0x99>; }; }; -------------------------------------------------------- wireless-bluetooth { compatible = "bluetooth-platdata"; uart_rts_gpios = <0x71 0x0a 0x01>; pinctrl-names = "default\0rts_gpio"; pinctrl-0 = <0x98>; pinctrl-1 = <0x99>; BT,power_gpio = <0x71 0x15 0x00>; BT,wake_host_irq = <0x71 0x1a 0x00>; status = "okay"; }; wireless-wlan { compatible = "wlan-platdata"; rockchip,grf = <0x1c>; wifi_chip_type = "ap6330"; sdio_vref = <0x708>; WIFI,host_wake_irq = <0x71 0x13 0x00>; status = "okay"; }; ------------------------------------------------------ uart0_gpios = "/pinctrl/wireless-bluetooth/uart0-gpios"; 06_dtbdump_rockchip,rk3328-box-avb.dts
  16. I saw at the previous page that @Gausushad the same box and the same WiFi problem. It looks like it should work, but just don't connect. @easybhad gotten it to work for Libreelec, he said in a post over there, so it should be possible. I took a backup of the eMMC yesterday, so I have the original ROM available. I also extracted the dtb a few months ago but it's on my desktop Linux computer at home in Spain and I'm currently in Sweden visiting family I haven't seen in almost two years(pre-pandemic), but I can probably figure out how to do it on my MacBook or on Windows from the original ROM. Or perhaps it's easier to install xubuntu in VirtualBox... Thanks for the help so far @jock. At least I have come further than before.
  17. @curse Sorry for the late answer, but I just spot the post edit right now. wlan and bluetooth, despite being on the same chip, are connected to the SoC in different ways: wlan is connected via high-speed sdio bus, bluetooth via common UART; also they are physically different chip parts that just share some things (the radio part), so it may happen that one work and the other does not. Since rk3318-config correctly reports the right chip, it is attached to the right sdio bus. Now there there may be some board peculiarities that does not make it work. In the first post of this thread there are some good things that help in debugging, in particular if you can provide photos of the board and the original firmware or the original dtb I can inspect it and try solve the issue. If you can spot some marking/signatures on the board, you can see if there is a match in rk3318-conf when it asks for "led/gpio configuration". At the moment there are just two supported boards: YK_RK3328 (found on my HK1 Max) and X88_PRO_B ( @lucky62's box); maybe yours is a different one that require some minor adjustment to make wifi work.
  18. @extremeaudio both of your questions are answered by the FAQ posts in the TV Box forums: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus
  19. Hi, Firstly I have searched the forums, google and docs.armbian.com before posting this. I have and old TV Box (specs below) that I would like to try and re-purpose as a Home Assistant server. I'm not looking to do anything else with it. If you feel I'm wasting time here and would be better off buying some supported device, please say so. So far: 1) Have created and SD Card from @balbes150 repository - specifically buster with no desktop (https://users.armbian.com/balbes150/rk3188/) 2) Device boots from SD Card but no HDMI output. (If I boot the stock Android ROM - HDMI works perfectly.) 3) Wired LAN works and I can SSH to the box, create an account, etc. (WiFi doesn't seem to be working - I tried adding in ntmui but I can't make it activate) Ideally I would like to; 1) Get HDMI working - I believe USB Keyboard and Mouse might be working - I see them in lshw output 2) Get Wifi working - But this isn't a deal breaker 3) Backup the android firmware and put Armbian on the internal storage 4) There is also IR, SPDIF outputs but these are nice to have's - I believe also I mioght need to do something to enable hardware video accelaeration, but for my needs, again not critical. <EDIT> 5) Bluetooth and the 8GB onboard storage </EDIT> Can you please point me to the appropriate articles/info/tasks for the above? I"m happy to work things out for rmyself if I need to but I don't know where to start. TV Box Specs: RK3188. Brand is CloudGateCircle but lshw specifies product: UGOOS UT2 (ARMv7 rev 0 v71) 2GB RAM, 8GB Internal Storage I can run any commands/post output, files, photos, etc. (armbianmonitor-U attached) Thanks in advance Cameron. armbianmonitor-U.txt
  20. This usually works on official Armbian builds. On not official Armbian, who knows. TV boxes Armbian are community work / mainly just hacked together. Your topic was moved to the TV boxes club, where is the place to ask such questions.
  21. Hi. Running buster on Amlogic 912 arm box T95Z Max. As mentioned, the ethernet doesnt work but wifi does. Tried all the dtbs, no dice. Also, wanted to transfer the OS from SD to EMMC but neither does armbian-config have the boot option nor does nand-sata-install work. It says unrecognised command. Have absolutely no clue where to go from here. Any help appreciated.
  22. Sweet. I'll do some testing and get back to you. Edit Testing done. Most things seem to work. Ethernet OK HDMI Video out OK HDMI Audio Ok Bluetooth Audio OK However, I don't seem to be able to connect to WiFi. Odd since Bluetooth and WiFi is the same chip. Armbian-Config and nmcli see it, it also shows the available networks but when trying to connect. No luck. rk3318-config says that I have a Broadcom BCM4335/AmPac AP6334 chip. Somehow the WiFi times out after 90 seconds and after it has asked me twice for the password, which I know is correct. Also, no network settings icon is visible near the clock where the sound and Bluetooth icons are. No Web Browser seems to be installed, though the menu item for Web Browser is there. No problem since I had ethernet and could install a Web Browser (and without ethernet or wifi, there is no need for a browser) So... H96 Max plus (written with a '+'). RK3328. 4GB RAM and 64GB eMMC. Confirmed mostly working. Next edit The version I tried was: Armbian 21.08 - Ubuntu Focal desktop [xfce] - mainline kernel 5.10.41 - Build date: 2021-05-30
  23. Yeah, you're right: the thread title is a bit misleading, because rk3318 and rk3328 are fundamentally the same chip. It is so because I have no rk3328 to work on, so can't guarantee and test anything on that. People reported that the images works as well on rk3328 boards, so you're invited to try and report if it works for you. There are good chances that the images works fine, and ap6330 is well supported in mainline kernel, including bluetooth!
  24. Resolved by using a different imaeg download. so was working the whole time.
  25. I had missed this thread thinking it was only about RK3318 devices, but do I understand it correctly if I say it's for RK3328 devices as well? I have a H96 Max Plus RK3328 4/64 box that I've been fighting with for a while. I mostly have had problems with the WiFi. Reading through this thread seems to show that the ap6330 WiFi I have isn't impossible after all. I've mostly had problems finding a good dtb, that includes it. Would there be a chance that this would work on my box?
  26.