Jump to content

Antony Abi Rached

Members
  • Posts

    43
  • Joined

  • Last visited

Posts posted by Antony Abi Rached

  1. Hello,

     

    It has been years that I am using armbian and I would like to thank all the developers that contributed to this project. It is a really amazing work.

     

    I am writing this topic to see if someone faced the same issue that I have. 

     

    I am using the nanopi neo core + minishield with the following image : Armbian_5.75_Nanopineo_Debian_stretch_next_4.19.20.

     

    I am using the SSD as my root file system. 

     

    When I boot this equipment, it works without any problem. After some time (it can be months or weeks or days), I can't access anymore the device using ssh or using the serial debugger. If I plug in an ethernet cable, the led of the port is green but it is not working. 

     

    I faced this issue on multiple nanopi that use the same configuration with different applications. 

     

    Does someone have any idea what could be the origin of this issue?

     

    Thank you in advance for your help.

     

    Regards, 

  2. I tried to use only spi-spidev but I got the same result.

     

    here is the output of dmesg | grep spi

     

    [    2.488500] sun8i-h3-pinctrl 1c20800.pinctrl: pin PA15 already requested by 1c28c00.serial; cannot claim for 1c69000.spi
    [    2.488518] sun8i-h3-pinctrl 1c20800.pinctrl: pin-15 (1c69000.spi) status -22
    [    2.488545] sun6i-spi 1c69000.spi: Error applying setting, reverse things back
    [    2.488579] sun6i-spi: probe of 1c69000.spi failed with error -22
     

    Thank you for the help.

     

    Regards,

    Antony

  3. Thank you @Igor for your reply.

    I would like to really thank you guys for the effort that you are doing with armbian.

    My intention is not to offend you on this forum. All what I tried to do is to mention the problem that I had and that way other users can see this issue and share their point of view. 

    It's been a year already that I am using armbian and I am really enjoying it. A big respect for the work that you are doing.

    For the issue that I mentioned, I tried the last image of neo core of armbian website. The name of the image is Armbian_5.83_Nanopineo_Debian_stretch_next_4.19.38.

    If I try to activate the spi using armbian-config or by changing manually /boot/armbianEnv.txt file, the spi is not working. I cant find a file related to spi in /dev. 

    Here is /boot/armbianEnv.txt file output :

     

    verbosity=1
    logo=disabled
    console=serial
    disp_mode=1920x1080p60
    overlay_prefix=sun8i-h3
    overlays=spi-add-cs1 spi-jedec-nor spi-spidev uart1 uart2 usbhost1 usbhost2
    rootdev=UUID=7bd3acd9-0796-4ea2-bcc2-89cd47ce6426
    rootfstype=ext4
    param_spidev_spi_bus=1
    usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

     

    Thank you in advance for the help.

     

    Regards,

    Antony

     

  4. Hello, 

     

    I am using nanoPi Neo Core with mini shield nanoPi NEO CORE/CORE2. 

    The OS that i am using is Armbian stretch downloaded from this link : https://www.armbian.com/nanopi-neo/

    The armbian image that I am using is : Armbian_5.65_Nanopineo_Debian_stretch_next_4.14.78

    If I try to enable SPI without doing update and upgrade, it works.

    If I do update and upgrade and then try to activate SPI, it is not working. I dont find the spi device in /dev. 

    Any idea what could be the problem?

     

    P.S: Before last week, I didn't have this problem. So I think it is related to a recent update done on this image. 

    Thanks in advance.

     

    Regards,

  5. Hello,

     

    I am using nanoPi Neo Core with mini shield nanoPi NEO CORE/CORE2. 

    The OS that i am using is Armbian stretch downloaded from this link : https://www.armbian.com/nanopi-neo/

    The armbian image that I am using is : Armbian_5.65_Nanopineo_Debian_stretch_next_4.14.78

    What I am trying to do is enable hotspot. 

    Based on what you said, if I am using a wifi USB adapter, the script will not work correctly?

    I am trying to setup the hotspot using armbian-config. I chose my default interface the eth interface. And I want to use the wifi usb adapter for hotspot.

    It should work?

    When I setup the hotspot using armbian, it takes more then 30 minutes for the script to finish. Is this normal?

     

    Thanks in advance.

  6. Hello,

     

    I am using nanoPi Neo Core with mini shield nanoPi NEO CORE/CORE2. 

    The OS that i am using is Armbian stretch downloaded from this link : https://www.armbian.com/nanopi-neo/

    The armbian image that I am using is : Armbian_5.65_Nanopineo_Debian_stretch_next_4.14.78

    What I am trying to do is enable hotspot. 

    I followed the following tutoriel that is already published on this forum : 

     

    When I try to start the hotspot using armbian-config, network manager stop working. 

    I tried to do a reboot but it didn't work. And network manager doesn't start again. the cause of this error is : NetworkManager[879]: Failed to read configuration

    P.S: I have an ethernet connection and I have a wifi adapter using a USB (https://www.friendlyarm.com/index.php?route=product/product&product_id=143).

     

    Any idea how to solve this problem?

    Thanks in advance.

     

    Regards,

    Antony

  7. @martinayotte i just tested the hardware flow control with the newest armbian neo core image that i donwloaded today from the website.

     

    Both RTS and CTS worked with this image. So i have the following results with these two images:

     

    *Armbian_5.38_Nanopineo_Debian_stretch_next_4.14.14 : 

    1) hardware flow control doesn't work normally. 

    2) mount the file system on ssd disk and boot from sd card work normally. 

     

    *Armbian_5.65_Nanopineo_Debian_stretch_next_4.14.14 : 

    1) hardware flow control work normally. 

    2) mount the file system on ssd disk and boot from sd card doesn't work normally. 

     

    Hope I helped you with the tests that I did. 

     

    Regards, 

    Antony

     

  8. Thanks for your reply @martinayotte.

    I am not using a RS485 halfduplex operation. I have two devices that are communicating using serial port (UART) and I would like to use hardware flow control because it is recommended for the communication that I am doing. The RTS and CTS in my case will help the two devices know if they are ready to send/receive data. 

     

    What I am finding strange is that when I activate RTS and CTS, the mode function of the CTS GPIO only switch to ALT5. The RTS GPIO stays as "OUTPUT mode". Shouldn't the RTS GPIO switch also to ALT5?

     

    Regards,

    Antony

  9. Hello again,

     

    I tested the hardware flow control after adding "param_uart1_rtscts=1" to /boot/armbianEnv.txt.

    The CTS of the nanopi worked normally. (The GPIO mode of the CTS switched to ALT5).

    The RTS didn't work. (The GPIO mode of the RTS didn't switch to ALT5).

    I did the serial communication test between the nanopi and a raspberrypi.

     

    Why do you thing the RTS is not working?

     

    Thanks in advance.

     

    Regards,

    Antony

  10. Hello guys,

     

    I am trying to use hardware flow control over the uart 1 of a nanopi neo core that I am using with a minishield.

    The GPIO pins of RX,TX,RTS and CTS of uart 1 based on this documentation (http://wiki.friendlyarm.com/wiki/index.php/Mini_Shield_for_NanoPi_NEO_Core/Core2) are G6,G7,G8 and G9.

    First of all I downloaded WiringNP in order to see the status of each GPIO.

    Before activating the rts cts on uart1, the figure "beforeActivatingRTSCTS" is the output of the command "gpio readall" .

    Then I added to the /boot/armbianEnv.txt the following overlay param_uart1_rtscts=1

    I rebooted the nanopi.

    After reboot, the figure "AfterActivatingRTSCTS" is the output of the command "gpio readall".

     

    As you can see, the GPIOG9 switched to ALT5 but GPIOG8 stayed the same.

    I am supposing that the ALT5 is the Alternate function for RTS CTS. Is that right?

    Why the GPIOG8 didn't change to ALT5 after activating the RTS CTS ?

    Is there something that I am doing wrong to activate these pins?

    Do I need to instruct the serial port driver to use the hardware flow control signals?

     

    Thanks in advance.

     

    Regards,

    Antony

     

    AfterActivatingRTSCTS.PNG

    BeforeActivatingRTSCTS.PNG

  11. Hello again,

     

    I did the test again.

    I executed nand-sata-install script using armian-config.

    At the end, I didn't rebbot.

    I mounted the SSD disk manually.

    I modified /mnt/nand-sata-install.g3nZk2/etc/fstab and removed the line corresponding to the EMMC storage.

    I checked that /boot/armbianEnv.txt is pointing to the SSD disk.

    I rebooted and got the following serial debug logs.

     

    I got the same problem. 

    P.S: I checked /etc/fstab before rebooting. I figured out that the EMMC storage is only mounted in /etc/fstab. 

    I am really out of ideas regarding this problem. Hope what I explained and the logs help you figure out the problem. 

     

    Regards,

    Antony

    SerialDebug.txt

  12. @martinayotte I tried to use an old image of nanopi neo core. I downloaded it around 5 months ago and the name of the image is Armbian_5.38_Nanopineo_Debian_stretch_next_4.14.14.img.

     

    When I try to use the nand-sata-install script with this machine, it works normally. I boot from SD card and my file system is on the SSD disk.

     

    Regards,

    Antony

  13. @martinayotte I made sure that my serial connection is done correctly with the nanopi and redo the reboot.

    I got this :

     

     

    U-Boot 2018.05-armbian (Sep 12 2018 - 10:40:28 +0200) Allwinner Technology

    CPU:   Allwinner H3 (SUN8I 1680)
    Model: FriendlyARM NanoPi NEO
    DRAM:  512 MiB
    MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
    Loading Environment from EXT4... ** File not found /boot/boot.env **

    ** Unable to read "/boot/boot.env" from mmc0:1 **
    Failed (-5)
    In:    serial
    Out:   serial
    Err:   serial
    Net:   phy interface0
    eth0: ethernet@1c30000
    230454 bytes read in 34 ms (6.5 MiB/s)
    Unknown command 'bmp' - try 'help'
    starting USB...
    USB0:   USB EHCI 1.00
    USB1:   USB OHCI 1.0
    scanning bus 0 for devices... EHCI timed out on TD - token=0xd8d80

     

    Regards,

    Antony

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines