All Activity
- Past hour
-
CONFIG_SUNXI_CCU=y CONFIG_SUN50I_A64_CCU=y CONFIG_SUN50I_A100_CCU=y CONFIG_SUN50I_A100_R_CCU=y CONFIG_SUN50I_H6_CCU=y CONFIG_SUN50I_H616_CCU=y CONFIG_SUN50I_H6_R_CCU=y CONFIG_SUN6I_RTC_CCU=m CONFIG_SUN8I_H3_CCU=y CONFIG_SUN8I_DE2_CCU=y CONFIG_SUN8I_R_CCU=y It's compiled into the kernel You are right there is calibration code here. static int ccu_iosc_32k_prepare(struct clk_hw *hw) { struct ccu_common *cm = hw_to_ccu_common(hw); u32 val; if (!have_iosc_calibration) return 0; val = readl(cm->base + IOSC_CLK_CALI_REG); writel(val | IOSC_CLK_CALI_EN | IOSC_CLK_CALI_SRC_SEL, cm->base + IOSC_CLK_CALI_REG); return 0; } static void ccu_iosc_32k_unprepare(struct clk_hw *hw) { struct ccu_common *cm = hw_to_ccu_common(hw); u32 val; if (!have_iosc_calibration) return; val = readl(cm->base + IOSC_CLK_CALI_REG); writel(val & ~(IOSC_CLK_CALI_EN | IOSC_CLK_CALI_SRC_SEL), cm->base + IOSC_CLK_CALI_REG); } static unsigned long ccu_iosc_32k_recalc_rate(struct clk_hw *hw, unsigned long parent_rate) { struct ccu_common *cm = hw_to_ccu_common(hw); u32 val; if (have_iosc_calibration) { val = readl(cm->base + IOSC_CLK_CALI_REG); /* Assume the calibrated 32k clock is accurate. */ if (val & IOSC_CLK_CALI_SRC_SEL) return LOSC_RATE; } val = readl(cm->base + IOSC_32K_CLK_DIV_REG) & IOSC_32K_CLK_DIV; return parent_rate / IOSC_32K_PRE_DIV / (val + 1); } static unsigned long ccu_iosc_32k_recalc_accuracy(struct clk_hw *hw, unsigned long parent_accuracy) { struct ccu_common *cm = hw_to_ccu_common(hw); u32 val; if (have_iosc_calibration) { val = readl(cm->base + IOSC_CLK_CALI_REG); /* Assume the calibrated 32k clock is accurate. */ if (val & IOSC_CLK_CALI_SRC_SEL) return 0; } return parent_accuracy; }
- Today
-
Tanix TX66 RK3566 4GB/32GB 8K 2.4/5WIFI 1GiB BT USB2/3 SD IR SPDIF
realcam replied to realcam's topic in Rockchip CPU Boxes
The box can be toothpicked into a loader from where there are options available including ADB - which I also have no experience with. When trying to boot a generic rk3566 LE image from SD the device stays dark. Which means to me it's trying to boot. Good but not progress. I now have a UART adaptor but didnt get a word over the line yet. UART may need enabling or may be misconfigured or may not be a UART port at all. Flying blind is not great. ADB may be a more productive approach. Eyeballing the board there is a wifi 2.4/5 & BT chip (LGX9358) which had me worried cos no search engine hits but device tree says wifi_chip_type = "ap6398s" and this seems known. I tried to contact the manufacturer wrt general information and about getting maybe access to their (legacy) kernel SDK, but haven't heard back yet. Other sources suggest that this manufacturer is not interested in open source software on their products. Maybe this is true, maybe not, I'll wait, it's only been a week. There is a lot to learn and I havent spent much time on this yet, busy with other stuff. - Yesterday
-
TV Box Status Information Template Version 1.0 ======================================= TV Box Name: Leelbox S1 (PCB marking: "A95X_DDR4" "V1_1 2160906") CPU: AMLogic S905X RAM: 1 GB DDR4 (reported: 860 MiB) - 2 x SpecTek (Micron) "PPE05-075" "F1646" Armbian build file name: Armbian_community 24.5.0-trunk.226 DTB file used: meson-gxl-s905x-p212.dtb Kernel Version: Linux 6.6.22-current-meson64 Distribution Installed: Bookworm Working Ethernet (Yes/No): Yes Max Ethernet Speed that works (100/1000): to be verified Does wifi work (Yes/No): Yes (RTL8189ETV) Does bluetooth work (Yes/No): No Does HDMI audio work (Yes/No): Not tested Comments: - also sold as ABOX-A1 according to online sources; - installation to MMC worked without issue using the dedicated script.
-
in the past I had a script to power on/off my TV through home assistant. The CEC supports putting devices in sleep and waking them up. If this works in Kodi then the standard kernel interface is available in Armbian. The important part is the hardware support - very few devices support sending CEC data but if Kodi can change input and turn on/off already, then we should be all good with Armbian and OPI5.
-
That was one of the first things I tried but the result was the same. I know the document and I think there is code in "drivers/clk/sunxi-ng/ccu-sun6i-rtc.c". It is compiles as a kernel module but it doesn't get loaded. I'll put a few printk to see if its called and what happens inside.
-
@OttawaHacker What specifically do you mean regarding "on/off" thing? Previously, I updated the Kodi config for for my CEC remote to manage how certain functions work with the remote in CEC. This was done through the menus in Kodi. If you can explain what you're trying to do, I'll try it on my setup. I usually leave the CEC setup so that the TV and other devices are not turned off or switched to/from when the events happen. If you go to Settings / System / Input / Peripherals and then select CEC Adapter, a list of items that can be modified is displayed. I don't know if all of them work or if it depends on your TV, other devices etc. Have a look. Let me know if you want me to post the list.
-
My current TV doesn't have CEC but I'm planning to replace it with something that has CEC support and would really like to automate the on/off thing... Is cec-utils supported or is there an alternate kernel API?
-
This is amazing!!!! Is Wayland supported yet? I'll give this a shot once all these updates make it to the official pre-release images.
- 28 replies
-
- Orange Pi 5
- Orange Pi 5B
-
(and 1 more)
Tagged with:
-
That did it, @royk. Now I can boot from NVME. Thank you!
- 28 replies
-
- Orange Pi 5
- Orange Pi 5B
-
(and 1 more)
Tagged with:
-
linux-libc-dev packages not available after 23.02
valium replied to valium's topic in Advanced users - Development
I have created a small patch and pull request to package the linux-libc-dev headers in the Armbian build process. https://github.com/armbian/build/pull/6408 I'am open to work on suggestions if you notice anything. -
I found more information on 32kHz clock. Starting at page 275. https://www.scs.stanford.edu/~zyedidia/docs/allwinner/h616.pdf 3.13.3.4.6. RC Calibration The basic circuit of RC calibration is shown in Figure 3-39. Whether to output the calibrated RC clock can be selected by the RC_Cali_SEL control bit, the calibration principle is as follows. http://nskhuman.ru/allwinner/h616reglist.php?nreg=153 3.13.3.5.3. Fanout Set the bit0 of 32K_FANOUT_GATING_REG to 1, and ensure that external pull-up resistor and voltage are normal, then 32.768 kHz fanout square wave can be output. Fanout: The clock source of fanout can select RTC_32K, or 32K divided by PLL_PERI(2X), or 32K divided by HOSC. http://nskhuman.ru/allwinner/h616reglist.php?nreg=161 /* * There are other differences between models, including: * * - number of GPIO pins that can be configured to hold a certain level * - crypto-key related registers (H5, H6) * - boot process related (super standby, secondary processor entry address) * registers (R40, H6) * - SYS power domain controls (R40) * - DCXO controls (H6) * - RC oscillator calibration (H6) * * These functions are not covered by this driver. */ I guess there's no function to calibrate the internal RC oscillator yet. https://github.com/torvalds/linux/blob/master/drivers/rtc/rtc-sun6i.c This is the 32K_FANOUT_GATING_REG. #define SUN6I_LOSC_OUT_GATING 0x0060 rtc->ext_losc = clk_register_gate(NULL, clkout_name, init.name, 0, rtc->base + SUN6I_LOSC_OUT_GATING, SUN6I_LOSC_OUT_GATING_EN_OFFSET, 0, &rtc->lock); If we can find out which clock source we are using and change it to something more accurate? All though, Calibrating the RTC is the ideal solution. On these cheap boxes there is no external 32KHz oscillator.
-
Description When booting U-Boot for rockchip64 or rk3588 devices, the error Failed to load '...-fixup.scr' pops up. This PR fixes this error by checking if the file exists before trying to load it. This PR partially fixes https://github.com/armbian/build/issues/6398 Unfortunately, I was not able to fix the error with missing kaslrseed (even though it may only be cosmetic). Note: U-Boot uses Hush cli language. Not this Hush cli (!) but a different old Hush shell in Busybox which is very badly documented overall unfortunately. I could not find any Hush functionality or a U-Boot command to check if the command kaslrseed exists. Should we include CONFIG_CMD_KASLRSEED for every rockchip64 and rk3588 device? Jira reference number AR-2105 How Has This Been Tested? Just compiling a new uboot image and installing it with dpkg -i (+ armbian-config after that) did not work. [x] Compiled a new image, flashed it and checked U-Boot log ./compile.sh build BOARD=nanopc-cm3588-nas BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article
-
Just remove armbian from the list. There won't be any further updates anyways. Userspace is way outdated.
-
Hi all, I have a Rock64, running ioBroker, and want to update the npm/nodejs to update all the adapters - mainly MQTT with which I have some problems. Trying to run apt update or iob nodejs-update, I run into: The repository 'http://apt.armbian.com stretch Release' does no longer have a Release file. in several versions. Can you help me? Sources.list is (changed, this works now) deb-src [trusted=yes] http://archive.debian.org/debian stretch main non-free contrib deb [trusted=yes] http://archive.debian.org/debian-security stretch/updates main non-free contrib Armbian.list is: deb https://apt.armbian.com stretch main stretch-utils stretch-desktop With hopful regards Martin
-
Description Added the necessary parts to create linux-libc-dev packages when creating armbian images. This functionality was not added to the new build system but worked just fine up until v23.02. In my opinion linux-libc-dev should always be created when building an armbian kernel as the kernel versions often differ greatly from the ones natively in the distros (eg. debian bookworm: 6.1.76 vs. armbian current 6.6.21). Also the armbian package source previously included the package but does not anymore, so the latest updates available were 23.02.2. See also https://forum.armbian.com/topic/36140-linux-libc-dev-packages-not-available-after-2302/#comment-184962 How Has This Been Tested? Used the updated scripts to build deb packages and images for bananapi and rpi4b. The created package linux-libc-dev installs the expected headers. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article
-
Description Fix/rewrite-kernel-config two kernel configs (mvebu64-current and sun50iw9-btt-legacy) to adapt them to the latest wireless driver updates in drivers_network.sh. Without doing a rewrite-kernel-config refresh, their kernel builds might potentially fail due to misconfigured wireless driver modules. Checklist: [x] My changes generate no new warnings View the full article
-
@Joel @amazingfate Just tried the 6.1 image (Armbian_24.2.4_Orangepi5-plus_jammy_vendor_6.1.43_kde-neon-amazingfated_desktop.img.xz) and installed to the NVME (with only 1 ext4 partition) with armbian-install. Initially it didn't boot, there are no files in /boot. After copying the files from the boot partition of the SD-card to the /boot folder of the NVME and changing the UUID in armbianEnv.txt to the UUID of the NVME it boots.
- 28 replies
-
- Orange Pi 5
- Orange Pi 5B
-
(and 1 more)
Tagged with:
-
@SteeMan - I ended up setting the environment variable BOARD_NAME in /etc/defaults/armbian-motd for the V1 boards - thanks again
-
I have the same issue and just tried to get a serial dump but I get absolutely nothing. I've connected to pins 32 TX and 33 RX + GND. I confirmed I have the right pins by booting a known good image and get something starting with `U-Boot TPL 2022.04-armbian (Nov 25 2023 - 12:49:32)`. Is there anything we can check on the SD as to why it doesn't boot?
-
Information installing armbian on M8S+ (amlogic s812)
bellad replied to nobuteru's topic in Amlogic CPU Boxes
i've try Armbian_21.11.0-trunk_Aml-s812_focal_current_5.14.0.img with dtb file : meson8b_hd18q meson8b_m200_1G meson8b_m201_1G meson8b_m201C_512M meson8b_m201d meson8b_m203a meson8b_m202_512M meson8b_m203b meson8b_mk808bplus meson8b_mxq meson6-atv1200 meson8b-ec100 meson8b-mxq meson8b-odroidc1 meson8m2-m8s meson8m2-mxiii meson8m2-mxiii-plus meson8m2-wetek-core meson8-minix-neo-x8 meson8-tronsmart-s82 no result good i search dtb file with AP6330 wifi can you help , please thank you -
search for linux-headers-5.8.5-sunxi
Иван Томшин replied to Иван Томшин's topic in Software, Applications, Userspace
I've updated. Now my version is 6.1.47-current-sunxi. This is a very new Linux. I have a similar problem. Where can I tell the headers for this version. There is none of them -
Yes, it crashes. It looks like it’s related to nvme drive activity. Running 6.8-rc7 atm.
-
Description We are using out-dated hdmi patches and now mainline has hdmi phy merged. HDMI bridge driver is WIP by collabora but I can get it work on rock5b. Comparing deleted 0032 patch and new 0040 patch for rock5b, we can see devicetree is a llitle different from the old one, for example, we don't need node hdmi-con and hdmi0_out. We have to rewrite all these boards with hdmi support referring to rock5b: [ ] hinlink h88k [ ] rock 5a [x] rock 5b [ ] nanopi r6s/r6c [ ] khadas edge2 [ ] orange pi 5/5b [ ] orange pi 5 plus How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh kernel BOARD=rock-5b BRANCH=edge DEB_COMPRESS=xz KERNEL_GIT=shallow [x] HDMI works on rock5b Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article