ej0rge

  • Content Count

    20
  • Joined

  • Last visited

About ej0rge

  • Rank
    Member

Recent Profile Visitors

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

  1. Clearly getting closer. But i gotta point out, there is more information to be seen on the serial console. usb-to-ttl-serial dongles are cheap and plentiful. Regretfully it has been several months since i worked on this sort of thing and my memory is foggy.
  2. Do you have a serial console? that is the best way to see what is happening during bootup. At first glance i think some detail may be missing from your dts but right now i don't remember enough of my own troubleshooting process. I will look into it again a little later today though. Double check the pinout - you didn't mention what board you are on and not all h3 headers are alike. Also i notice that the raspberry pi overlays for the 3.5 screens, of which there are 3 versions, have an "init" stanza that you might need to copy/paste all or part of. https:
  3. I am very confused. Did you run "sudo apt --add-architecture armhf" and not just "apt --add-architecture"? Also it's libc6 not livc6. try "sudo apt-get install libhybris:armhf" I don't have the specific experience with libhybris but i do have multiarch working on my H5
  4. I have the waveshare 2.8 A tft and touch panel working on the Orange Pi PC2 with one long dtoverlay. Some of my inspiration came from here: Like i said one dtoverlay, both fbtft and the touch panel, no other overlays needed. I admit i am a neophyte and it might be possible to trim this one slightly and use it in combination with the CS1 dtoverlay but it wasn't clear to me how that would work. I am using a 6 inch hand-made cable to connect my waveshare 2.8 A but it is wired straight through on only the needed wires for touch and tft.
  5. I don't have specific experience with widevine but debian-derived distributions including armbian are capable of hosting multiple ABIs. Your s912 is aarm64 but is backward compatible with armhf. Your 32-bit arm binary is armhf. Similar to how an amd64 system is backward compatible with an i386 system. You start with dpkg --add-architecture armhf then apt-get update Then you install 32-bit versions of everything you need for your 32-bit netflix, etc with "apt-get install foo:armhf" and so on. I've only done this on a small scale, but if you
  6. Got it. TFT at least. reset_gpios needed to be 0 0 1 instead of 0 0 0. Yes i should really find where the referece is for what the syntax means instead of trying to intuit it. I'll see if i can tease the touch into working though i don't really need it for my application. Edit: probably gonna start with copypasta from this but with the correct gpio pins: https://github.com/armbian/sunxi-DT-overlays/blob/master/examples/spi-ads7846.dts So far I have only tested this on my orange pi pc2 running 5.4.20 waveshare_32b_28a_opi.dts
  7. Thanks for that. - i was unsure about whether that line needed to change. It loads now, but the screen is still white, so i guess i have more troubleshooting to do. The touch device also is not working. [ 8.040102] ads7846: probe of spi1.1 failed with error -22 [ 8.041249] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 8.060153] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. [ 8.062524] fbtft_of_value: buswidth = 8 [ 8.062534] fbtft_of_value: debug
  8. OK, this is probably related: Is there a way to get a more informative error message?
  9. Yeah, nothing that looks like it is directly related. the only mention of spi is where it complains about not being able to create a device for spi flash that might not exist. During the uboot part of bootup it complains about no boot.env and that might be related. Maybe it's not reading armbianEnv.txt at all? I think i might hook up the serial console so i can log the whole boot process.
  10. I am trying to figure out how to create a dtoverlay to allow my waveshare 2.8a fbtft screen to work. I understand that i the 5.x.y kernels, a dtoverlay is required. I'm starting with the waveshare32b.dts for raspberry pi, found here: https://github.com/swkim01/waveshare-dtoverlays Should be compatible with the 2.8a per waveshare wiki. I'm trying to modify it in sort of the same way as was done in this thread, for another display: The board I'm using for this is an orangepi pc2. But i don't' actually know what I'm d
  11. Looking through the git logs i found this commit: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/drivers/staging/fbtft?h=staging-testing&id=2962db71c7030868b6859d09b2138b55297df95e Which explains why the 5.4.y kernels don't include fbtft_device, and clarifies that the only way to use one of these devices in the 5.4.y kernel is with a dtoverlay. The reference for that would seem to be here: https://github.com/notro/fbtft/wiki/FBTFT-RPI-overlays Naturally, the rpi overlays will have to be, uh, adjusted,
  12. I don't want to talk about how long i beat my head against this but i have it working so i thought i would share. First, in the 5.4.y kernels, the fbtft_device module seems to be missing? So i am using 5.90 oragepizero ubuntu bionic next 4.19.57 as my image, kernel is upgraded to 4.19.62-sunxi via regular apt-get upgrade. I have a genuine waveshare 2.8 A rpi lcd. Waveshare states repeatedly that it is compatible with the 3.2 B rpi lcd except for the screen size and number of buttons, so this should work for the 3.2 B lcd as well. This blog post was pretty
  13. Try changing the cpufreq governor to "userspace" or "performance"