Jump to content

martinayotte

Members
 View Profile  See their activity

  • Posts

    3892

  • Joined

  • Last visited

 Content Type 

Everything posted by martinayotte

  1. martinayotte
    The RK3399 SoC is defaulted to 1500000 and the U-Boot too...
  2. martinayotte
    You should not place any W1 driver in /etc/modules-load.d/modules.conf ... You should rely on DT overlays : https://docs.armbian.com/User-Guide_Allwinner_overlays/ ... and more specially to H3 W1-Bus overlay parameters : https://github.com/armbian/sunxi-DT-overlays/blob/master/sun8i-h3/README.sun8i-h3-overlays#L231,L250
  3. martinayotte
    You must have wired it incorrectly by swapping TX/RX ... Even if you have done something wrong in DTB, you should see the u-boot logs followed by kernel logs with "console=serial" in /boot/armbianEnv.txt There is Mainline nightly build here : https://dl.armbian.com/nanopim4/Debian_stretch_dev_nightly.7z
  4. martinayotte
    Well, as said before, use the USB-TTL Serial, when reaching the login prompt, log into it, then do "dmesg" to see complete boot log. Of course you can try the latest mainline, which is the one I use on my T4, but maybe something else will be missing, depending of your needs...
  5. martinayotte
    Edit the following file : /etc/default/armbian-zram-config
  6. martinayotte
    Is the DS18B20 driver working fine from command line using "cat /sys/bus/w1/devices/28-000004fe1847/w1_slave" ? In the link you've provided, it is mention that you only have to add a reg_expr, but there is also a note :
  7. martinayotte
    So, it reach login prompt, you've logged in an still don't see the /dev/spidev0.0 ? What shows up doing "grep SPIDEV /boot/config-*" ? It should show : CONFIG_SPI_SPIDEV=m Which kernel are you using ?
  8. martinayotte
  9. martinayotte
    I'm talking about the Serial Debug port, a 4 pins header on the board, it is attached to UART2DBG_RX and UART2DBG_TX of the SoC, it should the serial@ff1a0000, put it back to "okay" ... Then, attach the USB-TTL on this 4 pins header, and watch the boot log and try to find an error related to the fact that boot is hanging. I don't care about this yellow led for now, it is not related to the issue ...
  10. martinayotte
    I'm not sure to understand your question ... Do you have this USB-TTL Serial attached to Serial Debug port of your M4 ? Do you run on your PC "putty" or "picocom" ? What are you seeing while it is booting ? To make sure you see complete logs, make sure to have "verbosity=7" and "console=serial" in /boot/armbianEnv.txt ! There should be an error somewhere if it doesn't reach login prompt ...
  11. martinayotte
    /usr/sbin/nand-sata-install
  12. martinayotte
    Do you have a USB-TTL Serial dongle to check logs during boot ? Where does it failed ?
  13. martinayotte
    It is not for NanoPi-M4, as I mentioned I've use NanoPC-T4 ... EDIT : I've just double checked on my T4 : SPI1 is really on spi@ff1d0000 ... So, why your M4 doesn't boot after such changes ? Maybe you did some typo errors ?
  14. martinayotte
    Did you tried all other SPIs, spi@ff1e0000, spi@ff1f0000 and spi@ff200000 ?
  15. martinayotte
    That is pretty normal if you didn't switch the branch here : https://github.com/armbian/build/blob/master/config/sources/odroidc1.conf#L22
  16. martinayotte
    Those steps are not logical since the second "dd" will overwrite the first one ...
  17. martinayotte
    I got the things working ! Although I didn't tested it with real SPI device, I've at least tested it with loopback wire between MISO/MOSI and executed spidev_test ... https://github.com/armbian/build/commit/34205e60b3efa0ef3acc293ed9e02b801f8a52c1
  18. martinayotte
    You are right ! Although the overlay have been committed, it never been tested, and Yes, there are stuff missing in Main DT to make it work ... EDIT : Looking at this task, it looks more difficult to achieve, the H6 SPI are not at the same pins than H5, I will try to figure out ... EDIT2 : Also, not the same IRQ and DMA ... Hope it will work ...
  19. martinayotte
    Don't grep with "spi", since overlay is rejected, none of the spi code will be executed. So, look at the whole "dmesg" line by line. I'm pretty sure you will see some errors looking like "pinctrl : invalid pin handle" or "pinctrl : pin already used by ..."
  20. martinayotte
    This tutorial could help : https://wiki.archlinux.org/index.php/WPA_supplicant On my side, I'm an oldtimer guy, so I'm still using old way to setup WiFi directly in /etc/network/interface ...
  21. martinayotte
    Are you doing that with "sudo" ? If "nmtui" isn't working for unknown reason, you can also try to use "wpa_cli" ...
  22. martinayotte
    This means the overlay been rejected, probably because of unavailable resource or bad node definition. "dmesg" may provide hints about this rejection ...
  23. martinayotte
    Workaround is to use "nmtui", it doesn't required any GUI, it is command line ...
  24. martinayotte
    What "blkid" is reporting if you boot a normal image ... Another workaround is to have direct device naming in /etc/fstab such as (assuming that pendrive is /dev/sda1) : /dev/sda1 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1
  25. martinayotte
    Edit the file /etc/default/locale .
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept