All Activity

Is this the changes ? I got still the same 😐

All Armbian board configurations files live in build/config/board/ Besides the Pcduino2 Cubieboard and OlinuXino-lime board, I don't know what other A10 boards still have some level of support. After that the next step would probably be to confirm that it works with uboot. Here you have another config file and dts. For any tweaks to uboot you will need to pass uboot-patch when running compile.sh. Note that when you do this you will need to open a new tab and navigate to cache/sources/u-boot-worktree/ Similiarly for the kernel you would navigate to cache/sources/kernel/ currently 6.12 is "current" while 6.14 is "edge" Hope this helps Ryzer

so, how should be looking my armbianEnv file ?

My mistake I was suggesting based on prior comments found on the Orange Pi Zero3 thread but after reviewing again it looks like the port part of the overlay is no longer necessary either so as Kris777 suggested just the interface name should hopefully now suffice. According to wiki, the main i2c interface should be i2c3: https://linux-sunxi.org/Xunlong_Orange_Pi_Zero2

For production, boxes are much more interesting than boards. We just need to deal with a honest manufacturer. The last dtb from @mmie4jbcu worked very well for me in a x88 pro 20.

Same as before.

Hi! Great, that's a good starting point. So where could I find a reference file I can edit and align with my tablet? And where should I place this file? How would this file (possibly) connect to some dts? (This is just for my curiosity) Thank you!

HI, I dont believe it is necessary to recreate the Topwise A721 dts as it should already be included in the kernel sources used. What most likely needs to be done as a minimum is config file so that the Armbian build system recognizes the board and knows how to handle it. Admittedly I have never added a board so I can only speculate. A problem you may face is that the internal LCD may no longer work with the latest kernels. best of luck Ryzer

oh right, then maybe there is a few things you can help me with in future as I still getting to grips with my esp32. Don't worry it look difficult at first but gets easier. Now I believe I know what the problem, on the overlays line modify it to i2c0-pi and i2c1-pi. This appears to be a common problem with armbian-config overlay functional. My own A10 and A20 systems also has this problem as well.

maybe add manually in the file /boot/armbianEnv.txt the entry: overlays=i2c0 i2c1 i2c2

thank you for your help

I've added trough the armbian-config the current, but no joy. Tried a few from ChatGPT - no joy as well. I am not into this, since it's my first ( so far only ESP32 ), and honestly I had no idea that this requires this much stuff just to run a basic feature😐 Any help is greatly accepted. This is the /boot/armbianEnv.txt : verbosity=1 bootlogo=true console=both disp_mode=1920x1080p60 rootdev=UUID=f5d36c6f-cd6a-4f3b-a0a8-b0e85ac089e5 rootfstype=ext4 overlay_prefix=sun50i-h616 overlays=sun50i-h616-i2c0-pi sun50i-h616-i2c1-pi usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

@jwillb00 I can’t think of anything else. I’ll try to compile another image when I have time.

That solves it thank you very much for your time! If I want to change between boards like Rockpro64, Raspberry Pi4, etc. is there anything that needs to be considered as far as "reset" to a fresh state. For the guide I am writing I would like to make sure there is no lingering configuration that could cause problems when switching between builds for different boards.

Hi! I have an old Allwinner A10 based tablet that runs on Android. I want to install some other OS on it. I tried the instructions on linux-sunxi.org and created a page for the tablet: https://linux-sunxi.org/Softwinners_crane I extracted the FEX file from an image I got from the manufacturers a long time ago: http://github.com/linux-sunxi/sunxi-boards/pull/72/files The linux-sunxi mailing list pointed out that my tablet is similar to Topwise A721, so I used that dts file to compile u-boot and the kernel, and tried to boot it through an SD card. Trying to boot that, u-boot starts, and then gets stuck at "Starting kernel..." Then I found this: After following this and building armbian, I realised that there is no script.bin to replace anymore (I'm guessing because now we use device trees?), so unable to boot this as well. What should I do to make this work with armbian? My guess is that I need to create a new dts or correct the Topwise A721 dts (https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/allwinner/sun4i-a10-topwise-a721.dts) and then try again. The only problem is that I have no experience with device trees. Would really appreciate help on getting this to work, thanks! :)

Hi Yordan, Are you sure you have correctly enabled the i2c overlay on your board? what is the output of cat /boot/armbianEnv.txt? If something is showing up even with nothing apparently connected they your are likely targeting a different bus. It is possible what you are seeing is the address of the internal pmic although this normal shows up as UU. Best of luck Ryzer

All things being equal....... steve@fedora43:~$ uname -a Linux fedora43 6.16.0-0.rc0.250528gfeacb1774bd5.5.fc43.aarch64 #1 SMP PREEMPT_DYNAMIC Wed May 28 19:45:02 UTC 2025 aarch64 GNU/Linux kernel-6.16.0-0.rc0.250529g90b83efa6701.6.fc43. created by jforbes 6 hours ago for Fedora 43 .

Hello. I wonder if this issue is connected to my issue - to show something on i2c, while there is nothing, and not be able to communicate on it ?

@Nick Aseems like that still didn't work. is there anything you do for your builds that is not on the github page? I'll look into it some more tomorrow.

Hello. I'm trying to communicate with i2c ( i've connected ADS1115 on it if this maters ), but even without anything connected on it - it shows 0x30 on it, and I am not sure how to make it works. Please help ! 😐