dkebler
-
Posts
20 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by dkebler
-
-
I wanted to build the cli version but didn't see an obvious way to do that with conf variables and the docs don't illuminate that choice.
so I tried
BUILD_MINIMAL=no
BUILD_DESKTOP=no
and that seems to do force the cli version.
Just suggesting that this might be easier to grok if the variable was say
BUILD_TYPE=(desktop|cli|minimal|custom) with maybe default cli
where custom might be a rootfs that is custom (like one I put together) and thus doesn't need to be reconstructed from the custom-image script. Maybe setting custom then RELEASE could hold the path to the tarball?
If that seems better maybe I can try making a pr?
BTW this is not necessarily a beginner topic but didn't see a category for just generic building discussion.
-
armbian-config has a way to update the kernel within a major version but can one upgrade from 5.15 to 6.1 (current/edge).
I assume if not then I have to build my own image?
What I am after is jammy or bullseye with 6.1 kernel to support some hardware not supported in 5.15. I know the rolling releases (Lunar/Sid) have this kernel but I need a LTS release with 6.1.
-
[SOLVED]
That worked including touch! I downloaded the sid image and added the dts file. I didn't know that armbian had a overlay add command. Plus I don't know enough about kernels and overlays to come up with that dts file so THX!
As I look at that code I now see that's a way to enable (okay) a stanza/device in an existing dtb module without having to recompile it. So I have learned something!
My goal was to set up home assistant on this board but since I had the touch screen I bought originally for running android (now images of that are way old) I wanted to also set up a minimal X and load a browser in kiosk mode pointing to the home assistant page. Now with your help I can do that! Eventually when 6 kernel ends up in stable release I can switch to that.
again THX.
-
OKE I got my script issue resolved needed to use the dts file and only need to precompile it not the other files. My new version of the script is below
Was able to compile with the changes you suggested but had to add also the backlight and avdd stanzas. Not sure if they are needed?
So I booted and the hdmi goes blank but then the panel does not come up (super sad).
So I went back and removed the avdd-supply and backlight but that did not help.
So definitely suck now. Hopefully the hardware if functioning. I have no way to tell.
I guess I should try the 6.0 kernel but all the current armbian images for rockpro64 are using 5.15 and I have no experience compiling a kernel and I don't think armbian-config will upgrade across major releases.
mipi_panel: panel@0 { compatible = "feiyang,fy07024di26a30d"; reg = <0>; avdd-supply = <&avdd>; backlight = <&backlight>; dvdd-supply = <&vcc3v3_s0>; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; mipi_in_panel: endpoint { remote-endpoint = <&mipi_out_panel>; }; }; }; };#!/bin/bash SRC=/usr/src/linux-source-5.15.80-rockchip64 ARCH=arm64 DIR=$SRC/arch/$ARCH/boot/dts SOC=rockchip INCLUDE=$SRC/include CHIP=rk3399 DEV=$CHIP-rockpro64 DEP1=$CHIP DEP2=$CHIP-opp DST=$DEV.dtb cp $DIR/$SOC/$DEP1.dtsi . cp $DIR/$SOC/$DEP2.dtsi . # cp $DIR/$SOC/$DEV.dtsi . cp $DEV.dtsi.edits $DEV.dtsi cp $DIR/$SOC/$DEV.dts $DEV.dts.tmp cpp -nostdinc -I $INCLUDE -undef -x assembler-with-cpp $DEV.dts.tmp > $DEV.dts dtc -O dtb -b 0 -o $DST $DEV.dts
-
I wrote up a little script to deal with includes before running dtc per https://stackoverflow.com/a/36298460/4695378
First I tried just remaking the dtb file with the unchanged rk3399-rockpro64.dtsi
but throws an error in the rk3399.dtsi dependency file
Error: rk3399.dtsi:15.1-2 syntax error
FATAL ERROR: Unable to parse input tree
I did nothing but copy that file so not understanding why there is a syntax error in a file that was NOT changed.
Anyway, stuck at this point with idea of making a new rk3399-rockpro64.dtb
I see some armbian images are now shipping the 6 kernel but not the rock64pro ones :(. Even if they did I think I still have to make the dtb file as the dtsi file has those as status "disabled" instead of "okay"
So how does one compile a one off dtb file from dtsi that has dtsi dependencies cause I seem to be missing something here.
QuoteSRC=/usr/src/linux-source-5.15.80-rockchip64
ARCH=arm64
DIR=$SRC/arch/$ARCH/boot/dts
SOC=rockchip
INCLUDE=$SRC/include
CHIP=rk3399
DEV=$CHIP-rockpro64
DEP1=$CHIP
DEP2=$CHIP-opp
DST=$DEV.dtb
cp $DIR/$SOC/$DEP1.dtsi $DEP1.dtsi.tmp
cp $DIR/$SOC/$DEP2.dtsi $DEP2.dtsi.tmp
cp $DIR/$SOC/$DEV.dtsi $DEV.dtsi.tmp
cpp -nostdinc -I $INCLUDE -undef -x assembler-with-cpp $DEP1.dtsi.tmp > $DEP1.dtsi
cpp -nostdinc -I $INCLUDE -undef -x assembler-with-cpp $DEP2.dtsi.tmp > $DEP2.dtsi
cpp -nostdinc -I $INCLUDE -undef -x assembler-with-cpp $DEV.dtsi.tmp > $DEV.dtsi
dtc -O dtb -b 0 -o $DST $DEV.dtsi
-
ok can grab the kernel source via armbian-config. I'll try editing and compiling the 5.15 dtsi first.
-
For 5.15 Kernel.
There are no dtsi files in the image in order to insert and compile.
Can I just compile the entire 6.0 dtsi you pointed to and replace that dtb completely or will that break things?
Otherwise i guess I have to go grab the dtsi for 5.15 and edit as you say and then compile.
Alternatively I could upgrade the entire kernel to 6.0 but again don't know if that will break things.
What did you do?
-
Thx for info. I haven't had a chance to try yet but I'll report back when I do
-
-
ok so I try to load the module manually and get
modprobe --first-time drm_mipi_dsi modprobe: ERROR: could not insert 'drm_mipi_dsi': Module already in kernel
so it's already in the kernel so WHY is the DSI device not recognized and loaded (its not listed with lsmod)IF it's auto detected in order to load well the cable to the lcd is connected and it was working with android.
-
Still trying to get this to work.
I did see that the kernel config has enabled it. So apparently that kernel module is loaded.
`CONFIG_DRM_MIPI_DSI=y`but
`CONFIG_DRM_PANEL_DSI_CM=m`is a loadable module
The two DSI modules that that be loaded are apparently
`cat /lib/modules/$(uname -r)/modules.builtin | grep dsi`kernel/drivers/gpu/drm/drm_mipi_dsi.ko kernel/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.ko
`so I added those to /etc/modules
dw_mipi_dsi drm_mipi_dsibut on reboot they are not listed by
lsmod.| grep dsiSo am I barking up the right tree? How come these built-in modules won't load in this way?
-
I've got jammy running but I have a dsi display for the board and I'd like that to work (well the tp port too) with jammy. Looking at armbian config I see no setting for it. I know the display works fine as if I load an aryufan android image it works as it is set to use DSI by default.
Does this kernel know about the DSI port? Do I have to build a custom kernel? If not then what boot env line will get it going?
-
I tried flashing the spi u-boot, 2020 arufan version. Honestly not sure it took as I saw nothing on the monitor so had no idea if it was successful but now jammy server/cli version boots
-
-
yup, it's stuck at the exact same place .
`booting using the ftd blob...`
I used 5.18 (latest) so this hasn't been resolved with 5.18 jammy edge. These are likely CI generated and only us who actually have boards know this isn't booting.
focal versions and dietpit versions are booting so only the jammy versions are the problem.
Not sure how we can resolve this. I don't know enough to track down the problem.,
Thoughts?
-
Nevermind, 😙 kept trying reformatted stick again and it worked.
So for those having this issue make sure to format your stick to MBR not GPT and then make a FAT32 partition.
-
Getting stuck out of the gate (of course never goes as documented🤣)
https://puhoy.github.io/posts/armbian_on_espressobin/
While attempting to flash the required uboot update I keep getting a "permission" type error
I've tried with usb stick and sd card, formated ext4, formatted fat and various permutations including simple filename....all give the same error even though usb and mmc commands say the media is there
This is a v5. I have an identical one I set up a few years ago with ubuntu 18 but I did not have to flash this new uboot.
Any thoughts? Do one of the jumpers have to be set in order to flash?
Marvell>> usb info 1: Hub, USB Revision 3.0 - U-Boot XHCI Host Controller - Class: Hub - PacketSize: 9 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 1: Hub, USB Revision 2.0 - u-boot EHCI Host Controller - Class: Hub - PacketSize: 64 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 2: Mass Storage, USB Revision 2.0 - SanDisk Corporation Staples Relay SNDK7E38850327C07602 - Class: (from Interface) Mass Storage - PacketSize: 64 Configurations: 1 - Vendor: 0x0781 Product 0x5202 Version 0.32 Configuration: 1 - Interfaces: 1 Bus Powered 200mA Interface: 0 - Alternate Setting 0, Endpoints: 2 - Class Mass Storage, Transp. SCSI, Bulk only - Endpoint 1 In Bulk MaxPacket 512 - Endpoint 1 Out Bulk MaxPacket 512Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi usb Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found ** File not found flash-image-DDR3-2g_2cs_7-1000_800.bin ** Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from usb exit not allowed from main input shell.Marvell>> mmc info Device: sdhci@d0000 Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.4 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi mmc Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "mmc" to "spi" Card did not respond to voltage select! mmc_init: -95, time 42 MMC Device 1 not found No SD/MMC/eMMC card found Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from mmc exit not allowed from main input shell.
-
Looking at master branch for that tag that would be no as there is no
patch/kernel/sunxi-dev folder in the master for that tag
https://github.com/armbian/build/tree/v2021.05/patch/kernel
so does this patch have to be moved into the sunxi-current to be included in the release (or manual) builds from master branch?
So if I want build to inlcude this which branch/tag should I use? It's not clear to me. Or...when might this patch eventaully make it into the master branch latest tag?
I've never built a kernel or complete image for armbian so I'm kinda stabbing in the dark when it comes to repo structure and where commits get put and when and why. Any tips welcome.
-
so has this patch been incorporated into any of the most recent builds?? https://github.com/armbian/build/commit/d49be78b702d7779f78d2655126a56e7f2ea7426
I just downloaded (7/10/21) Armbian_21.05.1_Pinebook-a64_focal_current_5.10.34_xfce_desktop.img.xz
and it has the same issue so I am guessing no?
In which case if I build it myself it should be incorporated? i.e. the build is based on latest source?
How to run just the custom-image script on an already built image
in Beginners
Posted · Edited by dkebler
If I understand the custom-image script is run as a chroot after the image is built.
So didn't see anything specifically in the docs but can I ONLY run (from compile script) the custom image script on an already already built image (in /output/images)?
Along the same lines can I chroot at any time to the image via the compile script?
I should mention that I am using the docker container build for arm on my amd machine. (i.e. ./compile.sh docker.... )