hexdump

  • Content Count

    323
  • Joined

  • Last visited

2 Followers

About hexdump

  • Rank
    Embedded member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Piezo - did you already try "sysctl -w kernel.sched_rt_runtime_us=-1" - it works well for me for jackd ... best wishes and good luck - hexdump
  2. @Seth - it might be good to get the dtb from the box - in case no other way works, this approach so far worked for nearly every android tv box for me: https://github.com/hexdump0815/u-boot-misc/tree/master/misc.h616-legacy/android-device-tree-copy good luck - hexdump
  3. @SteeMan - just to come back to what you said about the jock builds for rk3288 and rk322x: i think the only way to get the amlogic tv boxes somehow supported in armbian is that someone is or even better a few people are starting to setup and maintain a proper csc line for them like jock did for rk3288 and rk322x - it will not work in the long term to try to support them based on old balbes150 images and a lot of hacks around them ... i'm not having the time and energy to step in here, but i think all the information should be there based on the research balbes150, various others and me have do
  4. @jernej - well done! - it works well on my h313 x96q box
  5. @SteeMan - but it is important to be aware that the boot process for rockchip, allwinner and especially amlogic is very different in the detail and for amlogic there is a high risk to brick a box if you try to completely replace the boot loader like it can be done quite easily for allwinner or rockchip. it could even be done for amlogic (i'm running several boxes this way) but its too complicated and risky to do it this way. btw. when installing to emmc it is very important to not overwrite the beginning of the emmc as the legacy u-boot searches for its dtb somewhere there and will
  6. @jernej - from irc i remember that some special u-boot hack was required for you to enable hdmi - is this still required or did you find another way to get it working? will have a look at your code over the weekend.
  7. @SteeMan already explained very well how my u-boot files are supposed to be used ... some notes regarding those u-boot files: for most of them i built two versions: one with "-serial" in the name - they have serial console support enabled and hdmi/usb kbd support disabled and the other version is without "-serial" and has the serial console disabled and hdmi/usb kbd enabled. i built those two versions as i noted that leaving both consoles (serial plus hdmi/usbkbd) enabled together did not work reliable - it looks like noise on the serial line in this case can confuse u-boot (so that it hangs),
  8. @robertoenr - it might be related or it might be not - i think there is just one way to find it out and that is to try it good luck and best wishes - hexdump
  9. @nightguest - if you want to seriously put some effort into getting your h96max h2 to boot then here is how to get there: https://github.com/hexdump0815/u-boot-misc/issues/2 - but be warned this is not easy, so if you just want to get linux on it the easy way then it might be better to search for another box best wishes - hexdump
  10. @SteeMan - nice to hear that the u-boot images are working well - regarding your ethernet problem please give this patch a try: http://lists.infradead.org/pipermail/linux-amlogic/2020-December/009360.html - it fixes some messed up clocks as soon as audio is compiled into the kernel on boxes with gbit ethernet good luck and best wishes - hexdump
  11. @SteeMan - in case you want to experiment (i.e. not sure if it really works), you might play around with chainloading the g12a-u-boot.bin (s905x2) and sm1-u-boot.bin (s905x3) from https://github.com/hexdump0815/u-boot-misc/releases/tag/200926-01 or gxb-u-boot.bin (s905) or gxl-u-boot.bin (s905x) from https://github.com/hexdump0815/u-boot-misc/releases/tag/200718-01 ... basic chainloading goes like this - https://github.com/hexdump0815/imagebuilder/blob/master/boot/boot-amlogic_gx-aarch64/s905_autoscript.txt - maybe compare it to the balbes150 boot scripts for fancier ways and most probably bet
  12. @Werner - it might be better (at least in the beginning) to use a plain mainline as a base as i guess this is what the authors of the patches use when creating them ... mixing it with another tree with lots of own patches in them might make it harder to debug problems
  13. but those are fixed ip cores in the hardware and not loaded later - if you want to get rid of those i think you have no chance to get a useable system going at all ...
  14. i think you can run some allwinner socs (at least the h6) and some rockchip socs nearly blob free as they do the memory setup themself, have open source atf (and sometimes optee too) and u-boot. maybe a free usb wifi might be required as boards sometimes come with wifi requiring blobs. this way one might even be able to make a cheap h6 tv box into a blob free system
  15. i agree with @jock - rk3318/rk3328 usually use pwm for voltage control, so it should and i guess will work - at least for us it did for all the boxes we ran across