-
Posts
15 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Thanks Did that and the dtc command shows UART2 being present in the devicetree, any idea how to identify it in all the /dev/tty* options ? New appeared Also if i wanna use 1-wire do i also need to add an overlay ?
-
Thanks @going can the overlay be added into a running kernal or does that also require compilation ?
-
Also to add how to get 1-wire to work ?
-
Hi I'm trying to understand how to enable Uart 2 for serial communication with a mcu on the banana pi (trying to connect a board running klipper to it). I connected the Uart of the board to CON1-P08 and CON1-P10 of the Banana PI M3 according to all i can find those pins are tx/rx for UART2. So far i figured out that the UART should be one of the /dev/ttyS* ones if i'm not mistaken, I can see /dev/ttyS to /dev/ttyS7 but am missing the /dev/ttyS1 user@bananapim3:~$ ls /dev/tty* /dev/tty /dev/tty11 /dev/tty15 /dev/tty19 /dev/tty22 /dev/tty26 /dev/tty3 /dev/tty33 /dev/tty37 /dev/tty40 /dev/tty44 /dev/tty48 /dev/tty51 /dev/tty55 /dev/tty59 /dev/tty62 /dev/tty9 /dev/ttyS2 /dev/ttyS6 /dev/tty0 /dev/tty12 /dev/tty16 /dev/tty2 /dev/tty23 /dev/tty27 /dev/tty30 /dev/tty34 /dev/tty38 /dev/tty41 /dev/tty45 /dev/tty49 /dev/tty52 /dev/tty56 /dev/tty6 /dev/tty63 /dev/ttyACM0 /dev/ttyS3 /dev/ttyS7 /dev/tty1 /dev/tty13 /dev/tty17 /dev/tty20 /dev/tty24 /dev/tty28 /dev/tty31 /dev/tty35 /dev/tty39 /dev/tty42 /dev/tty46 /dev/tty5 /dev/tty53 /dev/tty57 /dev/tty60 /dev/tty7 /dev/ttyACM1 /dev/ttyS4 /dev/ttyUSB0 /dev/tty10 /dev/tty14 /dev/tty18 /dev/tty21 /dev/tty25 /dev/tty29 /dev/tty32 /dev/tty36 /dev/tty4 /dev/tty43 /dev/tty47 /dev/tty50 /dev/tty54 /dev/tty58 /dev/tty61 /dev/tty8 /dev/ttyS0 /dev/ttyS5 I'm glad for anyhelp and any idea
-
Thanks that's what my conclusion also was, I'll search my old backup drives for an old image that still could boot from emmc. Me poking at the uboot config won't do much good. If you need someone to test something ask
-
Thanks, i looked at the scematics doesn't seem like there is a voltage select that is just for the emmc
-
Mind elaborating a bit what needs to be changed about the uboot to make booting from EMMC possible ? I've been poking in the dark for a few days now, learned a bit and really like to know what i'm missing
-
U-Boot SPL 2022.07-armbian (Jan 30 2024 - 11:01:03 +0000) DRAM: 2048 MiB Trying to boot from MMC2 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### Thanks @going, i tried your image but it didn't work for me. Can you explain the copy process a bit more ? I used this command dd if=xxx.img of=/dev/mmcblk2 bs=10M to copy it
-
Now looking at the DTS for the banana pi M3 (sun8i-a83t-bananapi-m3.dts) turns out the emmc is mmc2 not mmc1. Got no idea what mmc1 could be but it uses the wi-fi's power sequence
-
So I figured out how to test uboot.bin's with the fel mode, but so far couldn't build my own uboot for the a83t. Also i dug around in the image and it seems like the banana pi m3 images doesn't have the uboot for the a83t (might be wrong there)
-
So far no, but I'm reading up on it and plan to
-
Results of today: I found no image that would let me boot from EMMC without the micro SD, but when i edit the armbianEnv on the SD to point to the UUID of the EMMC partion with installed os it boots from the EMMC. So my conclusion is that i need to build my own U-Boot.bin to get around the poweron issue with the emmc.
-
Can't find that image anywhere and no matter what i try (even the banana pi supplyed ones) refuse to boot into emmc. When going into the U-Boot shell with a SD-Card plugged in i can get this env => env print arch=arm baudrate=115200 board=sunxi board_name=sunxi boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi boot_efi_bootmgr=if fdt addr -q ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr;fi boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf} boot_net_usb_start=usb start boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_syslinux_conf=extlinux/extlinux.conf boot_targets=fel mmc_auto usb0 pxe dhcp bootcmd=run distro_bootcmd bootcmd_dhcp=devtype=dhcp; run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00010:UNDI:003000;setenv bootp_arch 0xa;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr -q ${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_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(FEL boot)'; source ${fel_scriptaddr}; fi bootcmd_mmc0=devnum=0; run mmc_boot bootcmd_mmc1=devnum=1; run mmc_boot bootcmd_mmc_auto=if test ${mmc_bootdev} -eq 1; then run bootcmd_mmc1; run bootcmd_mmc0; elif test ${mmc_bootdev} -eq 0; then run bootcmd_mmc0; run bootcmd_mmc1; fi bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi bootcmd_usb0=devnum=0; run usb_boot bootdelay=1 bootm_size=0xa000000 console=ttyS0,115200 cpu=armv7 dfu_alt_info_ram=kernel ram 0x42000000 0x1000000;fdt ram 0x43000000 0x100000;ramdisk ram 0x43400000 0x4000000 distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ ethaddr=02:01:7e:b0:bb:78 fdt_addr_r=0x43000000 fdtcontroladdr=bbf5e620 fdtfile=sun8i-a83t-bananapi-m3.dtb fdtoverlay_addr_r=0x43300000 kernel_addr_r=0x42000000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile} loadaddr=0x42000000 loadsplash= for prefix in ${boot_prefixes}; do if test -e mmc 0 ${prefix}boot.bmp; then load mmc 0 ${splashimage} ${prefix}boot.bmp; bmp d ${splashimage}; fi; done mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi mmc_bootdev=0 partitions=name=loader1,start=8k,size=32k,uuid=${uuid_gpt_loader1};name=loader2,size=984k,uuid=${uuid_gpt_loader2};name=esp,size=128M,bootable,uuid=${uuid_gpt_esp};name=system,size=-,uuid=${uuid_gpt_system}; preboot=usb start pxefile_addr_r=0x43200000 ramdisk_addr_r=0x43400000 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}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;run boot_efi_bootmgr;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootarm.efi; then echo Found EFI removable media binary efi/boot/bootarm.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=0x43100000 serial#=32c004017eb0bb78 soc=sunxi splashimage=66000000 splashpos=m,m stderr=serial stdin=serial,usbkbd stdout=serial usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boot_part; fi uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b uuid_gpt_system=69dad710-2ce4-4e3c-b16c-21a1d49abed3 Environment size: 4905/65532 bytes Also i can access the emmc once booted @Gunjan Gupta Do you have any idea where to go from here or where to find more info on how to maybe get it booting from emmc ?
-
What other images were you trying Bahtiyar ? I'm intending to use the banana Pi for a 3d printer and EMMC booting is the last thing holding me back.
-
Hi I'm running into the same issue, this is the output i get from the serial <\r><\n> U-Boot SPL 2024.01-armbian (Feb 10 2024 - 01:33:08 +0000)<\r><\n> DRAM: 2048 MiB<\r><\n> Trying to boot from MMC2<\r><\n> Card did not respond to voltage select! : -110<\r><\n> spl: mmc init failed with error: -95<\r><\n> SPL: failed to boot from all boot devices<\r><\n> ### ERROR ### Please RESET the board ###<\r><\n> I got no idea what to search for in this case, also somehow my emmc is mmcblk2 instead of the mmcblk1 that it's refered to in every source i found so far