martinayotte

Members
  • Content Count

    3746
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by martinayotte

  1. OPi3 has eMMC while OPiLite2 doesn't . HDMI is working fine on my OPi3 using 5.6.0-rc3, although I don´t have "desktop" and stay at "headless". So, maybe try another HDMI monitor ...
  2. Here it is : => printenv arch=arm baudrate=115200 board=p200 board_name=p200 boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf} boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_source=sd boot_syslinux_conf=extlinux/extlinux.conf boot_targets=romusb mmc0 mmc1 mmc2 pxe dhcp bootcmd=run distro_bootcmd bootcmd_dhcp=if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00011:UNDI:003000;setenv bootp_arch 0xb;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci; bootcmd_mmc0=devnum=0; run mmc_boot bootcmd_mmc1=devnum=1; run mmc_boot bootcmd_mmc2=devnum=2; run mmc_boot bootcmd_pxe=dhcp; if pxe get; then pxe boot; fi bootcmd_romusb=if test "${boot_source}" = "usb" && test -n "${scriptaddr}"; then echo '(ROM USB boot)'; source ${scriptaddr}; fi bootdelay=2 cpu=armv8 distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ fdt_addr_r=0x08008000 fdtcontroladdr=7df63e38 fdtfile=amlogic/meson-gxbb-nanopi-k2.dtb kernel_addr_r=0x08080000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile} mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi pxefile_addr_r=0x01080000 ramdisk_addr_r=0x13000000 scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi; scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done; setenv devplist scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootaa64.efi; then echo Found EFI removable media binary efi/boot/bootaa64.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done scriptaddr=0x08000000 soc=meson stderr=serial@4c0 stdin=serial@4c0 stdout=serial@4c0 vendor=amlogic Environment size: 3591/8188 bytes => I don't have any RK image, only Armbian, so I will try this one . Still, that image looks strange to me since ROOTFS is empty ... EDIT: With the Armbian boot.scr, it try to executed it and fail (because Armbian is looking for Image), and continuing with same earlier fail : switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot.scr 3056 bytes read in 3 ms (994.1 KiB/s) ## Executing script at 08000000 26660 bytes read in 7 ms (3.6 MiB/s) Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... 26660 bytes read in 7 ms (3.6 MiB/s) MMC Device 2 not found no mmc device at slot 2
  3. Right ! I'm struggling to figure out how to make it boot, looking at "printenv" don't shows me why it try to boot from "mmc 2" where it is supposed to be 1. => fatls mmc 1 dtb/ 175 uEnv.txt 224 android_disable.sh 223 android_enable.sh 1732 ddbr-backup.sh 1710 ddbr-restore.sh 3433 install2emmc.sh 26386440 KERNEL 124035072 SYSTEM 48 KERNEL.md5 48 SYSTEM.md5 10 file(s), 1 dir(s) => ext4ls mmc 1:2 <DIR> 1024 . <DIR> 1024 .. <DIR> 12288 lost+found 0 .please_resize_me => As you can see, the second partition is empty, and during startup, it seems to wish to load something from partition 2 after successfully loaded the DTB, although kernel is on partition 1: Scanning mmc 1:1... 26660 bytes read in 6 ms (4.2 MiB/s) // <--- DTB loaded successfully MMC Device 2 not found no mmc device at slot 2
  4. It doesn't boot with SDCard alone : http://ix.io/2faw
  5. Change verbosity=7 in /boot/armbianEnv.txt and redo a capture of the serial log ...
  6. In my case, I got it working by disabling NetworkManager and used the "old school" /etc/network/interfaces.
  7. Did you try to use the same SDCard from the working one into the other one ? Yes, there is a SPINOR flash, but since SPI isn't enable, it should not interfere ... BTW, the whole thing remind me a 2 years old thread here : Do you have UART3 overlay in /boot/armbianEnv.txt ? The PA13/PA14 pins would be in-use if UART3 is enabled ...
  8. It should show something, but without newline, only at left of command prompt, it must be either "okay" or "disabled" Are both boards are identical, same revision number ? I don't understand the question ... I doubt, i says "already in use" ...
  9. As I said, formatting is completely not needed since "etcher" will overwrite using partition scheme provided by the image.
  10. PA13 is SPI1_CS ... Are you sure the SPI1 is disabled ? What "cat /proc/device-tree/soc/spi@1c69000/status" is reporting ?
  11. It seems a trouble accessing a specific GPIO, not related to SPI, but message with %d is not meanful. To get it more meanful, you need to fix it there : https://github.com/nRF24/RF24/blob/master/utility/SPIDEV/gpio.cpp#L48 It should probably be instead : throw GPIOException("can't access /sys/class/gpio/gpio%d/direction GPIO pin. check access rights", port); You can also check if the previous "export" worked by looking at "ls -l /sys/class/gpio/" to seen if the specific GPIO been exported. Maybe the GPIO is already in use, you can verify that by doing "cat /sys/kernel/debug/gpio" ...
  12. From my knowledge/understanding, it only mean that kernel has been compiled with CONFIG_SPI_SLAVE enabled, but no hardware is attached to it since neither drivers/spi/spi-sun4i.c and drivers/spi/spi-sun6i.c provide such functionalities. EDIT: you have probably seen that this /sys/class/spi_slave folder is empty ...
  13. What "cat /sys/kernel/debug/gpio" is reporting ? Which kernel are you using ? What "uname -a" shows ? BTW, "GPIO.cleanup()" is usually called when program exit, but at the beginning ...
  14. I will check as soon as I get time ...
  15. Even easier than that : decompile DTB currently present on you board, edit the resulting DTS by changing "status" node of "spi-gpio" to "okay" instead of "disabled", then recompile DTS into DTB.
  16. Check "dmesg | grep tty" because, for example, if UART1 is not enabled, then UART2 will be assigned to /dev/ttyS1 not S2 ...
  17. No, it is too complex task ... I don't understand what you mean ...
  18. As I said, kernel driver for AllWinner SoC doesn't support "slave" mode. What do you mean by testing baud rate ? If you wish to measure/verify the clock, you can take a oscilloscope...
  19. Don't do that, it can burn your H5 UART, RS232 are using inverted level of +/- 9V to 12V !!! Right ! Not only CP2102, but there are others, such CH340. Seeing your footer, in the meantime, you can use your OPiZero since it has UART1 on header.
  20. Unfortunately, although the H5 hardware is capable, Linux kernel driver doesn't support slave mode.
  21. Beware that TX output of OPiLite2 is 3.3V while your Arduino RX expect 5V, so it is maybe the reason why you don't see any output ... Better purchase a 3.3V compatible USB-TTL dongle.
  22. Most SoC are not "slave capable" but only "master" ...
  23. All those are working fine. Wifi ? Yes ! Others are not tested ... Maybe soon, since 5.6.0 is now at RC6 ...