shepper

I started down this path and realized that the patches are applied to downloaded linux kernel source. Normally, the kernel source is "cleaned" even if the build fails. I then found the sakura pi github page and the page has more recent commit than the Rock-s0, incorporates the kernel.dtsi while adhering the the u-boot requirements for rockpi's. U-boot for Rockpi. I'd like to base my build on the more up-to-date code. The easist way to do this is set CLEAN_LEVEL="" but I'm running into issues with the patches in GitHub: Sakura-Pi failing to apply. Essentially, I would iike to have the patches apply, not necessarily build and have the files generated by the patches remain. I have a large dtb file, extracted from Sovol's OEM firmware, that I would like to copy/paste into the generated *.dtb file, rename the *csc file and the defconfig file, and then generate a patch against clean source. Conceptually, this should work and I'm suprised it is this difficult to generate a new board for an existing family. Alternatively, a script could generate a file from a highlited portion of a patch and generate a file. Or is is possbile to run ./compile.sh a step at a time? It would be helpful in this setting, very instructive about the process and would narrow down build failures. Am I on the right path? Any step-by-step examples and or links to helpful scripts?

The Rock-s0 has the same rk3308b processor and the build uses a BL31binary, with u-boot. The SV06Ace has the same cpu and BL31/u-boot. I reviewed this thread and was trying to follow the example commit provided. It is a little difficult to work through a commit as not all of the paths to the files are present in my depth=1 git clone. Is it possible to download the commit for the Rock-s0 and use it to patch the build directory? If I could run the patch, then I would have some actual files to copy and edit. The maintainer of the Rock-s0, linked on the Armbian Info page for the s0 has not made any recent commits. The last Rock-s0 commit was where it was moved back to an older bootloader scheme. # Rockchip RK3308 quad core 512MB SoC WiFi BOARD_NAME="SV06 Ace" BOARD_VENDOR="sovol" BOARDFAMILY="rockchip64" BOARD_MAINTAINER="shep" BOOTCONFIG="sv06ace-rk3308_defconfig" BOOT_FDT_FILE="rockchip/sv06ace.dtb" KERNEL_TARGET="current" KERNEL_TEST_TARGET="current" DEFAULT_CONSOLE="serial" SERIALCON="ttyS0" MODULES_BLACKLIST="rockchipdrm analogix_dp dw_mipi_dsi dw_hdmi gpu_sched lima hantro_vpu panfrost" HAS_VIDEO_OUTPUT="no" BOOTBRANCH_BOARD="tag:v2024.10" BOOTPATCHDIR="v2024.10" BOOT_SCENARIO="binman" DDR_BLOB="rk33/rk3308_ddr_589MHz_uart0_m0_v2.07.bin" BL31_BLOB="rk33/rk3308_bl31_v2.26.elf" FORCE_UBOOT_UPDATE="yes" OVERLAY_PREFIX="rk3308" function post_family_config__rocks0() { declare -g BOOTDIR="u-boot-${BOARD}" declare -g BOOTSCRIPT="boot-rockchip64-ttyS0.cmd:boot.cmd" family_tweaks_bsp() { #overrides rockchip64_common.inc #Install udev script that derives fixed, unique MAC addresses for net interfaces #that are assigned random ones bsp=$SRC/packages/bsp/rockpis rules=etc/udev/rules.d Specifically, where are following files, referenced in /build/boards/*.csc located? BOOTCONFIG=*.defconfig" BOOT_FDT_FILE="*.dtb" The declared boot scripts Thanks

I'm putting together a build for a 3D printer, rk3308b-s board that has no ethernet, just a Fn-link wifi chip that is a knock-off of an rtl8192fs. I pulled the OEM dts and it describes the chip as an rtl8192cs. I'm pretty sure this is an out of kernel driver and my searches indicate I put source in userpatches. What do I need to add in the board/*.csc file to build to an image with the kernel module(s)? I do have a ralink ra2400, a mt7201 and some supported realtek dongles and If connected, I could git the code build and moprobe the module to test. Ideally, I would like to incorporate the driver via dkms in a armbian build. Can someone point me to the process?

I don't have a working board to add yet. I followed the documentation on creating a ~/build/config/boards/sv06ace.csc file but got lost about how to bring in the rk-kernel.dts values into the build. I started a new https://forum.armbian.com/topic/58141-rk3308b-build-using-sysfirmwareftb-on-sovol-sv06-ace/ since the question could apply to other 3D printer boards.

Per the title, I was able to extract an ftb file and convert it to dtb and dts file. I would like to use the community build framework and build Armbian for SV06 Ace. The initial plan was to base the new board/*csc files on other rk3308b boards; sakurapi and rock-s0 and then pull configuration values from the OEM dts file. I'm confused about the dts structure in Community builds and the proper locations for defconfig, dts and dtsi files. I've worked with the files in OpenWRT where they are rigidly structured - something that would be a monumental task for Armbian community builds. The OEM dts file does not use any includes/dtsi files. If successful, I would like to publish on github similiar to @Torte https://github.com/torte71/armbian-mksklipad50 Can someone point me to the relevant documentation for Armbian dts files?

I've setup an Armbian build environment that was able to build a Rock-S0, trixie, minimal image. Using the patch for the Rock-S0 also rk3308b based, as a basis, I would like to create a sv06-Ace patch using the rk-kernel.dts that I managed to pull from the OEM SV06 Ace firmware. If I get a working Armbian image for the SV06, Mainline klipper should be doable. Can someone point me to the documentation on howto do this. rk-kernel.dts

@Torte continued to help on his github site. The boot.img of the OEM firmware appears to set up a serial framebuffer screen and some shenanigans with the camera. I'm pausing the thread for now - need to figure out a path to reverse engineer the boot.img. Otherwise, alternative boards will need to be adapted.

It looks like mksclient is python code can be patched. Sovol3D forum Enable LED light toggle in Mainsail I followed the steps and was able to get an LED toggle in Mainsail on my SV06 Ace I did loose the touchscreen control of the LED but that's acceptable. I only need the LED when using the Camera to check for Failed prints and previously left the LED on during printing. Now I can save a little electricity😀. To me this also has pertinent implications to the thread. mksclient must be a python blob that can runs on boot. If were willing to tolerate the "black box" close source nature of mksclient, a touch screen supporting build, targeting the OEM electronics, should be possible.

Klipper Load Cell Documentation The kx711 is specifically referenced near the bottom of the documentation. It needs slow speeds and I believe has been incorporated into recent Klipper releases. I posted the file output on graphics, framebuffer and drm to @Torte github link. Also found an informative YouTube video on adding a Klipper Touch Screen, over serial, and configuring it. I'm adverse to tossing electronics into landfills - motivation to invest some time into a build for the Sovol boards and tolerate the mksclient propriatary blob. If the touch screen proves to be a show stopper, I think the makerbase MKS-SKIPR board, A supported USB wifi dongle and an HDMI touch screen could be used.

I did establish a wifi connection and ssh sovol@IPaddress. Have the following: sovol@sovol:/$ ls -a -C . data lib opt run srv userdata .. dev lost+found packages sbin sys usr .resized etc media proc sdcard system var bin home mnt rockchip-test sha256sum.README tmp vendor boot info oem root sha256sum.txt udisk sovol@sovol:/$ uname -a Linux sovol 5.10.160 #54 SMP PREEMPT Mon Aug 5 22:22:56 CST 2024 aarch64 GNU/Linux Could not cd to root/ and tried to su using mks, makerbase, sovol and 1234 as root passwds. Edit: I can run root commands with sudo The boot/ directory only contained grub/, no hidden files and no *dtb. Edit: Regained wifi after changing channel ?congestion. I looked at the FCCid site and the photos submitted to the FCC show a Realtek rtk8189FTV chip. It looks like the Fn-Link chip was substituted perhaps due to Mainland/Taiwan tensions. Not sure the FCC knows about the chip substitution or if new wifi test data was generated. The wifi on this board is crippling in many ways, Crowsnest cam access saves me many trips up/down the stairs to check for print failures. Still, it does not look like Sovol will be providing any more firmware updates. The two that are available can only be installed by a wifi connection using OTA (Over The Air). Paranoia is high for wireless connections that you know nothing about. I'm wondering about replacing the mainboard with the mks-skipr and adding a wifi module with mainstream kernel support. May be a better path to MainStream klipper and reliable mainstream wifi. Edit: Was able to scp/pull the following files: config-5.10 gpio.txt ip_address.txt rockchip_config. Building my own image still may be an option but will need to deal with the wifi driver, a python script for crowsnest camera and the LED light. Edit: Armbian-mkspi has patches for rtl8189fs. Image building is doable - not sure if wifi will be improved but Mainline Klipper, a more recent kernel, packages with updates can be had on stock boards.

I'm awaiting delivery of a new extruder heater/nozzle and it seems the wifi is reluctant to connect. Previously, the wifi would not connect until a calibration had been performed and it will not calibrate due to the extruder heater failing. I did upload the Sovol SV06 Ace mainboard schmatic to the O.P. but it is for board version 1.1. Hopefully I can connect, ssh in and get the *dtb file once the nozzel is replaced. Then cross check the *.dtb with the schematic. The new board,v1.2, likely uses the same Broadcom BCM43430 Fn-Link FG89FTSM13-W3 chip that Sovol Kipper Screen v1.2 Orange Pi Plus 2E uses. It may also have an additional fan socket. For future reader/search hits, you actually have to use radxa linux upgrade_tool. It will be a couple of days before I can follow up. I found one issue with the wifi chip, it is not broadcom based. It is an Fn-Link manufactured knock-off of a realtek rtl8189FTV/rtl8189fs. The driver is not in the mainline linux kernel but needs to be built as a module using Realtek source code. Armbian example of building the module. Armbian forum search shows code has been orphaned by Realtek Fn-Link no longer manufacturers the chip. The original source has issues and updated source, from 3rd parties, can be found. I searched Arch Linux AUR and found luckfox-pico/rtl8189fs. My OP incorrectly lists the wifi as Broadcom but I can no longer edit it.

I'm pretty sure is an skipr derivative: the Sovol SV06 Ace GPL github page has empty skiprs.conf.ini files. Your link mentions getting the dts dtb descriptor file for the OEM firmware. It is not on the Sovol page but the second option indicates that it can be extracted from the Sovol Firmware file. A quick search found an amlogic unpacker utility. Is their such a utility for rockchip? I did try to mount the Sovol OEM image as a loopback without success. If anyone is aware of a reliable guide, I'd appreciate getting pointed in the right direction. Edit: Found RKTools Linux_Pack_Firmware It does make me a little nervous but I think this is how most routers update their firmware. Ideally, I would like to boot an initframfs image to test but uboot did not have any pause and "Ctl+C" repeatedly pressed did not halt the boot. I tried several times before concluding that Sovol was making this as difficult as possible. I had another thought, the rkdevtool can download the image and I believe the Radza upgrade_tool can also download the image - documentation is scant

Hi, I'm new to the forums and am looking into replacing OEM Klipper firmware on a Sovol SV06 Ace, The main board looks very similar to the MKS Skipr with the following notable differences: rk3308 B emmc soldered on No SD card. Wifi/Bluetooth added - Original boards used realtek and the latest version uses Broadcom. OEM wifi is hit or miss on connecting and hopefull will be improved with Trixie based Armbian. Sovol has mostly complied with the GPL and source/configuration files are on github. IIRC the kernel version was 5.1x I'm a long time Linux user (Slackware 8.1), have contributed OpenWRT builds and have built custom Linux kernels. I think I've mapped out the install: flash the appropriate ambian image to a formated USB2.0 drive - Ideally with wifi ssid/wpa key ssh sovol@ip login sovol/sovol. su, suspect the root passwd will be makerbase. plug in usb, id drive in dmesg and mount dd if /dev/usb* of=/devmmcblk* Unmount drive and hopefully boot and access over wifi ssh. Install/configure Kipper/Mainsail... I have a recovery path that I have tested using rkdeveloptool/upgrade_tool and the original Sovol firmware. I've perused the armbian github pages looking the MKS Skipr build but have not found it yet. I'm willing to build a tailored (stripped if worthwhile) kernel. I'd appreciate any comments about broadcom wifi access and if newer kernels and newer wpa supplicant builds improve access enough to make it worthwhile. Comments on the overall plan. Pointers Sovol RG-4Z V1.1 SIZE.pdf