MastinZgZ

  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

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

MastinZgZ's Achievements

  1. Good morning, I have made a board where I have put an RTC DS1307 to a Neo core nanopi. From what I have been able to see, the system loads some kind of RTC module called sun6i-rtc. this module "occupies" the / dev / rtc0 so when loading the DS1307 it assigns it / dev / rtc1. Can the sun6i-rtc be disabled in some way? On the other hand, if I do this command. hwclock -w -f /dev/rtc1 --verbose hwclock from util-linux 2.37.154-c2ca2 System Time: 1625751906.401974 Using the rtc interface to the clock. Last drift adjustment done at 1625751901 seconds after 1969 Last calibration done at 1625751901 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. RTC type: 'rtc-ds1307' Using delay: 0.000000 seconds missed it - 1625751906.405792 is too far past 1625751906.000000 (0.405792 > 0.001000) 1625751907.000000 is close enough to 1625751907.000000 (0.000000 < 0.002000) Set RTC to 1625751907 (1625751906 + 1; refsystime = 1625751906.000000) Setting Hardware Clock to 13:45:07 = 1625751907 seconds since 1969 ioctl(RTC_SET_TIME) was successful. Not adjusting drift factor because the --update-drift option was not used. New /etc/adjtime data: 0.000000 1625751906 0.000000 1625751906 UTC it works correctly, but if I want to read, hwclock -r -f /dev/rtc1 --verbose it gives me this error. hwclock from util-linux 2.37.154-c2ca2 System Time: 1625751969.137899 Using the rtc interface to the clock. Last drift adjustment done at 1625751906 seconds after 1969 Last calibration done at 1625751906 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(3, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc1 to change hwclock: Timed out waiting for time change. ...synchronization failed the battery is charged, the i2c works well and detects it correctly. Any ideas? Thanks and best regards. Armbianmonitor http://ix.io/3siu
  2. Good morning, I have a NanoPi Neo core where I am trying to use the usb ports (USB1, USB2 and USB3), the first thing to say is that all usbhost is active in armbian-config. The system does not recognize me anything in any of the 3, not a pendrive, or Wi-Fi or anything. If I go to armbian-config, I see that the DTB system that has loaded is that of the NanoPi air, I do not know if it can influence. USB devices receive power when connected. Any idea if I have to activate something else or modify the DTB or something? I have tried adding to armbianEnv.txt this line at the end fdtfile = sun8i-h3-nanopi-neo.dtb but nothing. Thanks and best regards!
  3. Thank you very much, I look at it to see if I get to something. Thank you!
  4. Good morning, I am trying to get a UART to RS485 converter to work on the UART2. The RX Pin is PA1, TX is PA0 and the direction Pin is PA6. How can I activate it in the system, do I have to activate something in the armbianENV.txt? I have overlays = uart2 Some help? Thanks and best regards! Lewis
  5. Armbianmonitor http://ix.io/3q6H Hello! I Have this board, y want to use hcitool If i use hcitool dev it response Devices: If i try to use scan hcitool scan Device is not available: No such device Any idea? Thanks!
  6. Good morning, I am designing a board to use a NanoPi Neo Core. By default it comes without Wifi or BlueTooth. I had thought about putting the AP6212 chip on it. Can someone tell me if it is compatible with Armbian in its latest versions? Thank you and best regards!