

watou
-
Posts
7 -
Joined
-
Last visited
Reputation Activity
-
watou reacted to dfahren in Help wanted to test a new OpenVFD alternative
@jock
Yes indeed, the driver written bei Jean-Francois is already integrated in Armbian by your patch, I know. Yes it works with the correct dts all is good. I struggled quite a bit until I arrived at the solution outlined in my last posting and I also wanted to have the writing 'boot' to show up right at the get-go in the LED line display. So I had to amend his driver a bit.
One additional thing I could do to the driver is making the writing configurable in the dts, so that you only have to edit the text to show some other writing once the tv box boots up. This might be pretty easy, now I'm looking for some spare time ....
-
watou reacted to dfahren in Help wanted to test a new OpenVFD alternative
@Jean-Francois Lessard
You won't believe it, but I found my error(s) ....
For the solution I had to look at the dts Paolo (https://github.com/paolosabatino/leds-fd6551) suggested in his code. I missed a line that effectively makes SDA really open-drain. However, pinctrl is not relevant in this context.
The fist line is bloody important, the second not so:
i2c-gpio,sda-output-only; i2c-gpio,scl-output-only; Although they do incur warnings in the kernel log, they are indispensable because without them, i2c signals don't reach the fd6551 controller.
Now everything works as expected. It shows (in fact, it showed ...) 88:88 right at the start and after that the actual time. Great!
I'm going to write a pull request for Nicolas' Github repo so that he can integrate it with the Armbian distribution.
I also edited your tm16xx source code to show 'boot' instead of 88:88, which is not my cup of tea.
You also have to make sure you compile the driver als built-in and not as a kernel object. So you get the 'boot' writing roughly around second 2.8 in the boot process when plugging in the mains adapter and this is early enough for me.
I attach all of the sources to this post. I hope you don't mind too much that I messed with your code and I apologize upfront.
Best wishes,
Deetsh
tm16xx_boot.c display-client-snippet.dts
-
watou reacted to Hqnicolas in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
You're the first reporting, so, if when you have Armbian in your device, and it shows 8gb, it's 8gb.
about the wifi/ethernet problem:
it's a BUG made by the chinese developer that misconfig pinout's in dtb, that we can fix here...
50% of the problem is recognizing the problem, 45% is fighting it and 5% is talent you are at 50% already.
start your journey against the other 45% and find the 5% along the way.
-
watou reacted to Hqnicolas in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
the Github actions still working, it will be released in 5 hours.
Stay on Armbian Mainline 6.6. I'ts stable and updated,
the Joshua Riek h96 v56 max 6.1 Project is for iA that uses the RKnpu. and it's old and unstable.
-
watou reacted to Hqnicolas in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
@DreamDreams @dfahren
this is already the second patch update for joshua riek that I made so now I will send an board add request.
https://github.com/Joshua-Riek/ubuntu-rockchip/pull/1179
https://github.com/Joshua-Riek/linux-rockchip/pull/40
https://github.com/Joshua-Riek/linux-rockchip/pull/39
-
watou reacted to Vincenzoernst1 in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
@Hqnicolas
update
-
watou reacted to Hqnicolas in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
I want to make it clear to everyone that now The H96 MAX Became Full supported by armbian Mainline
26/08/2024 Latest Release:
https://github.com/armbian/community/releases/tag/24.11.0-trunk.25
desktop:
https://github.com/armbian/community/releases/download/24.11.0-trunk.25/Armbian_community_24.11.0-trunk.25_H96-tvbox-3566_noble_current_6.6.47_gnome_desktop.img.xz
Server:
https://github.com/armbian/community/releases/download/24.11.0-trunk.25/Armbian_community_24.11.0-trunk.25_H96-tvbox-3566_bookworm_current_6.6.47_minimal.img.xz
-
watou reacted to GBEM in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
Thanks, @Hqnicolas
Curiously, It's both the reset button method, and eMMC CLK shorting MASK ROM modes that go away. The device boots into MASK ROM mode, as opposed to a normal boot, however there's no USB device available to flash with. Trash the bootloader and you get the MASK ROM (CLK shorting) mode back.
I'm not bothered by it. It's just something to be aware of I guess. Sooner or later someone is going to say that their box is comprehensively bricked. Without an SD card socket or TTL port to upset the offending eMMC bootloader, to a certain extent that may be true.
Golly, I can't tell you all just how very pleased I am with Armbian on my H96 Max V56 TV box. It works so remarkably well, and is a tremendous credit to all those that have diligently worked on it, and have brought it to this stage. I can't wait to see where it goes from here. Awesome!
GBEM 👽
-
watou reacted to Hqnicolas in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
@watou @pocosparc
Keep your eyes on this topic and this project
for things like this
-
watou reacted to Hqnicolas in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
Updated Release for Kernel 6.6.45
Google Driver Alternatives 24.8.0 Trunk554
Armbian 24.8.0 Noble Desktop Kernel 6.6.45 official
Debian 12 Bookworm minimal Kernel 6.6.45 official
Official Links:
https://github.com/armbian/community/releases/tag/24.8.0-trunk.554
Armbian_community_24.8.0-trunk.554_H96-tvbox-3566_bookworm_current_6.6.45_minimal.img.xz.torrent
Armbian_community_24.8.0-trunk.554_H96-tvbox-3566_noble_current_6.6.45_gnome_desktop.img.xz.torrent
-
watou reacted to Hqnicolas in Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
https://github.com/armbian/community/releases/tag/24.8.0-trunk.495
I Will test it,
will need to remove my TTL enabled server.
@paradigman I tested it in an TTL disabled and it doesn't boot.
Tomorrow I will Migrate my TTL enabled server to test these images in a clear device.
Update:
TTL DEBUG: