Jump to content

zeekoe

Members
  • Posts

    19
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. No dtb.back on debian it seems... Thanks for your help!
  2. Yay! For others with similar problems: downgraded kernel with armbian-config (System > Other) to 5.10.60 Restored device tree (which is probably only needed if you messed it up in the first place; armbian-config > System > Dtc) to spi@ff130000 { compatible = "rockchip,rk3288-spi\0rockchip,rk3066-spi"; clocks = <0x07 0x43 0x07 0x154>; clock-names = "spiclk\0apb_pclk"; dmas = <0x1f 0x0f 0x1f 0x10>; dma-names = "tx\0rx"; interrupts = <0x00 0x2e 0x04>; pinctrl-names = "default"; pinctrl-0 = <0x28 0x29 0x2a 0x2b 0x2c>; reg = <0x00 0xff130000 0x00 0x1000>; #address-cells = <0x01>; #size-cells = <0x00>; status = "okay"; max-freq = <0x2faf080>; phandle = <0x95>; spidev@0 { compatible = "rockchip,spi_tinker"; reg = <0x00 0x00>; spi-max-frequency = <0x2faf080>; spi-cpha = <0x01>; }; spidev@1 { compatible = "rockchip,spi_tinker"; reg = <0x01>; spi-max-frequency = <0x2faf080>; spi-cpha = <0x01>; }; }; Note that phandle is different. I know not much about device tree, but this seems to be a sequence number.
  3. Thanks for your reply. While thinking further, I can vaguely remember that this error/warning was not new. So it might as well not be related to my problem. I found this: That could be my real problem. Might be of help to others, too, that fail after upgrade. I think I messed up the device tree thingy, if I get it restored, will post here again...
  4. Hi Aligmsten, Thanks for pointing into the right direction. Is it possible that you elaborate a little bit more on how to specifically disable spidev@1? $ dmesg |grep spi [ 1.943067] rockchip-spi ff130000.spi: cs1 >= max 1 [ 1.943091] spi_master spi2: spi_device register error /spi@ff130000/spidev@1 [ 1.943133] spi_master spi2: Failed to create SPI device for /spi@ff130000/spidev@1 $ uname -a Linux <hostname> 5.15.48-rockchip #22.05.3 SMP PREEMPT Wed Jun 22 07:34:52 UTC 2022 armv7l GNU/Linux $ cat /boot/armbianEnv.txt verbosity=1 bootlogo=false overlay_prefix=rockchip overlays=spi2 spidev2 rootdev=UUID=<something> rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I tried using armbian-config > System > Dtc, commenting out the spidev@1 parts: spi@ff130000 { compatible = "rockchip,rk3288-spi\0rockchip,rk3066-spi"; clocks = <0x07 0x43 0x07 0x154>; clock-names = "spiclk\0apb_pclk"; dmas = <0x1a 0x0f 0x1a 0x10>; dma-names = "tx\0rx"; interrupts = <0x00 0x2e 0x04>; pinctrl-names = "default"; pinctrl-0 = <0x23 0x24 0x25 0x26 0x27>; reg = <0x00 0xff130000 0x00 0x1000>; #address-cells = <0x01>; #size-cells = <0x00>; status = "okay"; max-freq = <0x2faf080>; phandle = <0x92>; spidev@0 { compatible = "rockchip,spi_tinker"; reg = <0x00 0x00>; spi-max-frequency = <0x2faf080>; spi-cpha = <0x01>; }; #spidev@1 { # compatible = "rockchip,spi_tinker"; # reg = <0x01>; # spi-max-frequency = <0x2faf080>; # spi-cpha = <0x01>; #}; }; It told me the file was wrong. Then I deleted the spidev@1 part. Now I don't have the errors anymore, but no /dev/spi*. For the record: all worked perfectly before for months, with the same configuration. After a reboot (and probably an update) it stopped working. I never had spidev2.1 though, but it just skipped it silently and I worked happily with spidev2.0.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines