ldiaz

Members
  • Content Count

    35
  • Joined

  • Last visited

1 Follower

About ldiaz

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Hi, I've been running Octoprint on armbian for several months with good results of a couple of printers with good performance no relevant problems. Installation process is not complex but I decided to build a simple a plug&play meta-distribution like OctoPi for Rpi boards but based on armbian so it can be used potentially in any of the supported boards. I started with the popular Opi Zero as it is really cheap and the four cores of the H2+ processor handle perfectly a 3d printer load and is 3 times cheaper than a typical RPI3B that octoPi requires. You can find it here: https://github.com/ludiazv/octocitrico Built-in features are: Core (installed and enabled): Optimized armbian Debian buster. Latest stable octoprint version. Selection of top octoprint plugins. HAProxy with self signed keys for ssl access. Avahi service: Bonjur addvertisement (this enable to acces with host-name.local via ssh or http/s) SSH console access. USB OTG console access (if available in the board) Enabled i2c-dev,spidev (if available on the board) 3D printer related software (installed but disabled): Klipper PlatformIo core for building 3D printer firmware. Marlin 1.1.x & Marlin 2.x.x firmware (bugfix versions) Extras (installed but disabled): MPGStreamer USB camera support (experimental) SMB shares to remote edit configuration files from a remote PC. Feedback and contributions are welcome. Thanks armbian guys for the awesome work you do.
  2. For LTS it seems that problem has been found: https://twitter.com/orangepixunlong/status/1270540655551320065?s=20
  3. Have you tried using sysfs directly? Have you recheck the port used? The formal is : (Position of letter in alphabet - 1) * 32 + Pin number
  4. I think not but I have not tested it as I use this box as headless server. That's why I needed ethernet. meson-sm1-sei610-ethfix.dtb meson-sm1-sei610-ethfix.dts
  5. Yes. I will publish latter today now I do not have the here the box! My box is 4G /32G I think it have external ephy to theoretically connecto 1Gbps ehternet. But there is basic version of this box that possible uses the internal ephy of the soc that only support 100Mbp In this case possibly my dtb will not work.
  6. I had same problem on X96Air. I solved by modifying the max-speed=<100> in pyh section of the dts. The downside is that only works at 100Mbps. Regards,
  7. Well, If you don't use fancy plugins and slice your models in the PC, octoprint just streams/monitor data to/from the serial port and uses a websocket to send status to the web browser. This typically loads one core with 10%-15% while printing. OpiZero has 4 cores and with armbian the frequency is scaled automatically controlling the heat and giving extra juice when needed. Even with a super cheap USB camera (no 1080p) without mjpeg chip the OPI is capable to stream video using 50% of other core. I even run a mini samba server on the OPI for editing files on the PI form the PC. I use builtin 100mb ethernet and networking is not a problem, I did not test using octoprint via WIFI. Other advantage of using SBC vs TVBox is that you can easyly prower the board from GPIO header, using a small DC-DC stepdown module($0.5) you can power the board from the printer PSU directly and avoid using a charger. If you need extra power you can find 1G RAM with better processors 64bit processor such H5/H6 with plenty of GPIOs for sensors, leds.... at good prices that are supported by armbian. If you want to give it a try please let me know Cheers,
  8. The software you are referencing is for RPI will not work on other devices without major ports. On the other hand the TV boxes typically do not have GPIOS exposed so is a poor choice for custom octoprint controller. I think it will be better off if you use a cheap SBC with armbian. I run my octo print in a $15-OpiZero 512MB with out problems. I made a mini distribution with octo print just plug an play. cheers.
  9. Hi @Sergey2k Could you please help me publishing the changes on the DTB for ethernet to work on th X96Air? Thanks,
  10. I'm able to boot from sd card using Armbian_19.11.4_Arm-64_bionic_current_5.4.1_20191228 + /boot/dtb/amlogic/meson-sm1-sei610.dtb + uboot-fix-g12. Wifi works ok but ethernet not. I did not installed it to sata or emmc memory yet. Regards,
  11. Hi @Sergey2k I managed to install current Armbian_19.11.4_Arm-64_bionic_current_5.4.1_20191228 on the X96Air applied the uboot. I'm able to boot but eth0 does not work as you mention before. I follow your advance here and it seems the it's needed to patch the dtb for ethernet. Could you please share the working dtb or explain how to patch it. I'm using /boot/dtb/amlogic/meson-sm1-sei610.dtb. Thanks!
  12. Hi, I notice the same problem in a Orange PI ZERO. SCLK is high when CS is asserted but as you say it should be LOW before CS is asserted. I have found no solution for this issue. The very strange thing is that on the OPI ZERO it happens only on the second CS line. I'm using the same RF24 code so the problem is not in the library. It should be in the spidev driver. In the Opi Zero I use the SPI1 instead the SPI0. Using spi-spidev and spi-add-cs1 overlays. If plug the radio to /dev/spidev1.0 it works fine without problems but if I change the radio to /dev/spidev1.1 the logic analyzer shows the same SCLK problem. I do not know why but there something wrong here. Try to change SPI interface or the CS you are connecting the radio. This could be workarround. Maybe @martinayotte or @zador.blood.stained hav more information on the SPIDEV implementation as I have seen in the past that they have deep knowledge on that. Regards,
  13. Hi, @glow I have not test any pygame in the zero as I use kivy that requires X windows for working on armbian so here I can't be very useful. As @A-P is interested in make also touch working a was able also to do it in the past with a Orange Pi Zero with XPT2046. This are the steps. You need to be sure that you have the module module for ADS7846 available in your build. If I remenber well its installed by default. Add to your armbianEnv.txt another std overaly it is call spi-add-cs1. This will add an adtional line for CS of the toch screen in the pin 26 that is what is compatible with your screen (TP_CS). Need to compile the dts I provided but for your screen you nee to change "PA7" to "PA1" in the ads7846_pins section of the file. The compilation is done with a DTC compiler (I think is installed by default). this way: ./dtc -@ -I dts -O dtb -o /boot/overlay-user/ads7846-touch.dtbo touch.dts # it will show some warnings. if dct is not available you can get an complie it by: #git clone -b dt-overlays8 https://github.com/pantoniou/dtc #sudo apt-get install -y flex bison #cd dtc #make Finally you need to add to you armbianEnv.txt this line: user_overlays= ads7846-touch Reboot. The dts has the possibility to tweak parameters for sensibility, dimension,etc.... This version is the default ported from raspberry Pi. Thats it!
  14. @A-P if you connect the screen to the PIZero as a Hat it sure SPI1 as SPI pins are those of this interface. SP1 CS=0. Also DC, RST/DC seems correctly mapped. The relevant part of the dmsg is this: [ 308.268459] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 308.281149] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 308.284168] m25p80 spi0.0: spi-nor spi0.0 10000kHz 8 bits mode=0x00 [ 308.284388] fbtft_device: spi_busnum_to_master(1) returned NULL [ 308.291574] fbtft_device: failed to register SPI device [ 418.056146] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 418.058972] m25p80 spi0.0: spi-nor spi0.0 10000kHz 8 bits mode=0x00 [ 418.059177] fbtft_device: spi_busnum_to_master(1) returned NULL [ 418.066383] fbtft_device: failed to register SPI device it seems the spi_busnum=1 is not activated / registered as present. This, in principle, could be accomplished by inserting this in the armbianEnv.txt overlays=spi-spidev param_spidev_spi_bus=1 As regards current location of drivers mine are here: root@orangepizero:~# ls /lib/modules/4.11.5-sun8i/kernel/drivers/staging/fbtft/ fb_agm1264k-fl.ko fb_hx8347d.ko fb_ili9163.ko fb_ili9340.ko fb_ili9486.ko fb_s6d02a1.ko fb_ssd1306.ko fb_st7735r.ko fb_tls8204.ko fb_upd161704.ko fbtft_device.ko fb_bd663474.ko fb_hx8353d.ko fb_ili9320.ko fb_ili9341.ko fb_pcd8544.ko fb_s6d1121.ko fb_ssd1331.ko fb_st7789v.ko fb_uc1611.ko fb_watterott.ko flexfb.ko fb_hx8340bn.ko fb_hx8357d.ko fb_ili9325.ko fb_ili9481.ko fb_ra8875.ko fb_ssd1289.ko fb_ssd1351.ko fb_tinylcd.ko fb_uc1701.ko fbtft.ko But I'm using 4.11 kernel version. It should not be relevant if the module system is propperly configured. Hope It can be useful