@lex

Members
  • Content Count

    442
  • Joined

  • Last visited

2 Followers

About @lex

  • Rank
    Embedded member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1590 profile views
  1. I have some experiments with legacy kernel 4.4 before the BPI updated the kernel source (changes on eMMC and possibly Wifi, my board is too old to check the new features), I don't know if it has been improved or not. Recently, the mainline stable kernel 4.20 has reached a very stable condition and you can even run KODI on A64, thanks to jernejsk's work. I think the problem is on the new eMMC version. I can't help on this since i don't have this hw revision. Tip: try to build Armbian without enabling eMMC and/or Wifi and see what happens. Grab the complete boot log, i think there are others here with the new hw revision that can help.
  2. This weekend I was revising and testing the OV5640 for some A64 boards. To enable the Camera (OV5640) on NanoPi A64 for the mainline kernel you have to update the following: * DT * GPIO-I2C Here is the excerpt : Kernel config: CONFIG_I2C_GPIO=m CONFIG_VIDEO_OV5640=m CONFIG_VIDEO_SUN6I_CSI=m
  3. Hmm. maybe you mean CPU version. A64 is the old one and R18 is the new one, they are essentially the same. Maybe you mean eMMC version , the new one has a newer eMMC version and you should run with a newer Kernel version that handles this new eMMC.
  4. Maybe when you install the games it updates the libGl or libEGL. I think this would happen to all distro but you could try to freeze (somehow) the libs on Armbian which has symlink to libmali. As a suggestion, you could install symlinks and find the libs and its symlink. Try on the first install: symlinks /lib/aarch64-linux-gnu Take notes and then do it again after reboot.
  5. That's the reason. It updates to new libEGL and breaks the symlink to libmali. If for some reason the new lib is installed you have to manually re-create the symlinks, or just don't update.
  6. Another interesting thing, i have been running my kernel without any patch related to the issue and have not seen any problem on my NanoPi A64. Although i don't usually run for a long time so the issue could manifest in time. I had a comment about this on linux-sunxi list a long time ago, maybe i was just lucky. I will have a look at your PR.
  7. Do you have an RTC backup battery attached to your Pine64?
  8. I see now. Then "reset" is not working properly, i suppose. stmac did not reset. If someone can check, do a cold boot, do a reboot and do a reboot again and check eth0.
  9. @froezus I don't see your u-boot patched , it is the only ATF that should be patched?
  10. I changed the timeout value from 100 ms (stmac had 10 ms and now has 100 ms) to 200 ms to see if could help,i get stmac crashes with this value. If i issue a sudo reboot from this session (100 ms default) again the OPI One Plus reboot normally. Changing u-boot version ethernet works on reboot but not hdmi. I also patched only ATF and not u-boot and i get random results, sometimes it works some times not. I am not sure u-boot must be patched.
  11. I would like to mention that I have reported a similar issue to @froezus , although i am using a different u-boot (in fact it's his u-boot) and latest kernel to experiment with. It seems u-boot and minor .config changes plays an important role in this case. If you can grab some dmesg output, check if you have something similar to this: dmesg|grep ethernet [ 0.879244] dwmac-sun8i 5020000.ethernet: EMAC reset timeout [ 0.879786] dwmac-sun8i: probe of 5020000.ethernet failed with error -14 [ 4.388248] platform 5020000.ethernet eth0: device MAC address c6:70:90:27:15:44 [ 4.388263] platform 5020000.ethernet eth0: Could not attach to PHY [ 4.394739] platform 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) This usually occurs on the first reboot, subsequent reboots restore ethernet connection. I have tested his previous patch and latest patch he submitted and for some reason, i got different behavior on reboot.
  12. "chip found is not an target chip" usually means you have issues with i2c (twi) talking to the sensor. Looks like a hardware issue to me, if possible try with another sensor or get a second board with a new sensor.
  13. Just an update to i2c and spi. The pin node definition i2c0 and i2c1 are reversed. It works. (5.0.1) So i think it is safe to assume i2c and spi are working, just need someone with better experience with the spi LCD to find the right DT configuration for the mainline 5.0.y . Hope this help. i2cdetect -l i2c-3 i2c DesignWare HDMI I2C adapter i2c-1 i2c mv64xxx_i2c adapter I2C adapter i2c-2 i2c mv64xxx_i2c adapter I2C adapter i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- 3d -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
  14. Using this code i got an output but similar to the previous one. https://github.com/rm-hull/spidev-test ./spidev_test -D /dev/spidev0.0 spi mode: 0x0 bits per word: 8 max speed: 500000 Hz (500 KHz) RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....�..................�. PS: the TX data: uint8_t default_tx[] = { 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x40, 0x00, 0x00, 0x00, 0x00, 0x95, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xF0, 0x0D, };
  15. Can you share your DT changes? Did you use the new dma? O used this code: https://github.com/torvalds/linux/blob/master/tools/spi/spidev_test.c