robertoj

it is possible to install octoprint in a more powerful ARM (32bit) SBC, then move the project folder with its VENV folder, to a smaller ARM (32bit) SBC, fix something and then run it https://dev.to/geekypandey/copy-venv-from-one-folder-to-another-and-still-be-able-to-use-it-3m49 https://www.youtube.com/watch?v=iZlgLrWed1I

Thank you for your work The concept sounds super useful to me... I will try it

Did you try: apt update apt-cache search rear

Usually it means that you need to install a *-dev package apt-cache search ffmpeg-dev ... or try other key words Also make sure you have installed build-common and python3-dev If you cant install with pip, is it available in debian? apt-cache search python3 |grep ffmpeg

Hello, I am having a lot of fun making my first apps with python and tkinter... and with my recent good experiences with LCD TFT displays, I want to create an "appliance" project. I can start non-GUI apps with systemctl service files, and they run with the proper user permissions... and I don't worry about giving it root access. But I would like to do the same with GUI apps. They would be full screen, 320x240 on the LCD TFT. All I can do now is: * start with armbian minimal (with orange pi zero in my case) * add the DTS for LCD and touch, and the ko for spi-gpio (as seen in my threads in the orangepi zero section) * install the bare minimum for X11: xorg, xorg-video-fbdev, xorg-input-evdev, python3-tk, openbox, xterm * create an auxiliary starter script: launch_my_app.sh #!/bin/sh openbox --startup 'python3 /home/roberto/tkinter_test/tktest.py' Then, I execute from within my python project folder, in an ssh session as my username DISPLAY=:0.0 sudo startx ./launch_my_app.sh Then my tkinter app runs, until I press ctrl-C in the ssh. But I feel that sudo is unnecessary and too much for a cybersecurity perspective. Is there a way to make it start automatically? (it would be ideal if xorg would exit if the window is closed) Sample python code. Credits: https://www.pythonguis.com/tutorials/create-gui-tkinter/

Which available kernel version makes this WiFi work correctly?

It turned out that my USB power cable was too long... I replaced it with the previous short one and I am back in business. I am experimenting with NOT USING CS. Good progress: In the DTS, comment out with "/*" the line cs-gpios = <&pio 0 13 0>; /* PA13 chip select */ Also, change this line num-chipselects = <1>; to <0> Previous result of: sudo cat /sys/kernel/debug/pinctrl/1c20800.pinctrl/pinmux-pins ... New result, with NO CS configuration: ... ... ^ with my next steps, I hope to verify that PA13 is available for other things It plays an h264 file with no hiccups mplayer -vo fbdev2:/dev/fb0 mj_remember_time.mp4

I meant to only change the kernel. I have never modified any of my SPI flash orange pis, because I fear bricking them.

Can you step back in armbian images until you find a linux version that doesn't show this problem?

In armbianenv.txt, erase the overlay “tve” (abbreviation of tv signal encoder) if you don’t use any analog outputs, can the pins be used as GPIO?

For anyone interested in connecting the ili9341 to an orange pi zero, and use the adafruit DRM driver: ili9341-spi1-drm.dts I made these experiments, since the LCD is the only one chip in the SPI bus. * disconnect the LCD's Chip Select -> LCD remains white * connect the LCD's Chip Select to GND -> LCD displays the login line and linux crashes soon after <- it might be my orange pi zero, which needs a heatsink Update: this thread also refers to orange pi zero 3... the solution (with touch function) is in this post: https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#findComment-204672

I simply rotated the image with the "rotation" parameter in the LCD DTS, and turned the screen 180 degrees physically. I will try the min, max swap later, but right now I am on a roll, making my tkinter apps work Another thing I will try is not using a chip select pin at all, since LCD and touch-chip are on different buses now.

I decided to use the gpio-spi driver, to emulate software spi just for the touch chip ADS7846/XPT2048, and use a different DTS file Here is what I think would work: ads7846-spi-gpio.dts I used these references: https://www.kernel.org/doc/Documentation/devicetree/bindings/spi/spi-gpio.txt https://stackoverflow.com/questions/78905378/how-do-i-use-spi-gpio-driver-in-linux https://gist.github.com/BjoernSch/39d3bca950a3b025b806decc2b686bbc and need to check this too: http://terminal28.blogspot.com/2015/12/bitbanging-spi-on-raspberry-pi-via-spi.html http://terminal28.blogspot.com/2016/05/enabling-spi1-on-raspberry-pi-bzero23.html My DTS compiles well but the linux in my armbian image did not include spi-gpio.ko, in /lib/modules/6.6.44-current-sunxi/kernel/drivers/spi/ Therefore, I am building a new OS image. Does anyone see a problem with my DTS? Update:) it works good stability now the only problem is that both x-axis and y-axis are reversed (not swapped). More updates on the way

Is it just for allwinner chips? Is this a change for good and toward stability, or is it a mistake?

Did you ever solve your problem?

Thank you. I will try that, and I learned about the xinput_calibrator, which I will apply next time. (and https://github.com/reinderien/xcalibrate/blob/main/xcalibrate is a new interesting project) Now I am focusing on moving the touchscreen pins to an independent gpio-based SPI set of pins... we will know whether the LCD crash is from interfering SPI commands. I did an experiment with the "backlight = <&backlight_gpio>" parameter as shown in https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-LCD-ADAFRUIT-24-SPI0-00A0.dts and https://forums.raspberrypi.com/viewtopic.php?t=358240 but so far it ended up in a kernel not loading. I will leave this task for last. If the DTS configuration does not specify CPHA and CPOL, what is the default setting of the SPI protocol?

I learned netplan recently, because I was unable to use armbian-config or nmtui (the underlying mechanism used by armbian-config)

If it works all the time, nothing else gets disabled, no new dmesg warnings appear due to this, it would be a good indicator but a dtbo (compiled from a dts) sometimes need to be changed when Linux is upgraded (like some changes with spi and tft changes)… and the orange pi official OS images are very old. so in general, a dtbo copied from an old os to a new os, might not work all the time. Needs to be tested. do you see a dts file with the same name as the dtbo?

I missed the part where you ask for overlay help change directory to /boot/dtb/sun..../overlays/ There are several readme files, find the ones that apply to your H618 chip. Find an overlay that refers to USB host. Do you use a cable to convert USB-C to USB-A-female? If it works, then the next step after reboot is the lsusb test. Also, look at any error messages printed by both linux ko's dmesg|grep cp210x dmesg|grep usbserial execute "sudo armbianmonitor -u" and show your /boot/armbianEnv.txt

In newest Armbians, we are using netplan, instead of NetworkManager https://docs.armbian.com/User-Guide_Networking/ Edit a config file sudo netplan apply

https://github.com/raspberrypi/linux/issues/6067 https://github.com/raspberrypi/linux/pull/6029 https://forums.raspberrypi.com/viewtopic.php?p=2206990&hilit=ads7846#p2206990 https://github.com/raspberrypi/bookworm-feedback/issues/88 There seems to be some instability in the ads7846 driver in the latest linux. If anyone is having a good experience with ads7846, please indicate how you did it.

Does the esp32 show up as a ttyUSB or ttyACM when plugged to your Linux PC? is there something new in the result of lsusb? can you plug something else in that USB port? can you send a photo of your connections?

Can you show an example of spi-gpio being used for an ads7846 touch screen?

Whats the difference between 2 and 8? I am having similar doubts with an spi ili9341, but I don't knwo how that DTS line works

I could run lightdm with apt install xinit xterm xauth x11-apps xserver-xorg lightdm xserver-xorg-input-evdev xserver-xorg-video-fbdev /usr/share/X11/xorg.conf.d/99-fbdev.conf: Section "Device" Identifier "myfb" Driver "fbdev" Option "fbdev" "/dev/fb0" EndSection However, the cursor is moving at 90-degrees from my finger movement. Also, it is very unstable... it crashes, leaving a white screen. The white screen remains after reboot, and I can only make it work again by removing and connecting the 5V power. Can someone share how they installed a window manager with ili9341? is 24MHz too fast? Would native cs1 help anything?