Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
networking issue on a banana pi
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4  
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM
View previous topic :: View next topic  
Author Message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Wed Nov 16, 2022 12:56 am    Post subject: Reply with quote

I tried using this boot.cmd

Code:
setenv bootargs console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootwait panic=10
fatload mmc 0 40008000 uImage
bootm 40008000 


I've omitted the initrd, since I don't have one, and the line with sun7i-a20-bananapi.dtb.uimg, since I was unsure about that. When I try to boot, it seems to get a bit further, but then reports

Code:
EHCI failed to shut down host controller.
Loading Kernel Image
FDT and ATAGS support not compiled in
resetting...


The FDT message seems related to sun7i-a20-bananapi.dtb.uimg, but I'm not sure about the ATAGS. In the uboot .config file I find

Code:
# CONFIG_SUPPORT_PASSING_ATAGS is not set


So, perhaps rebuilding uboot with this enabled might solve this problem. I'm still looking for a way to generate sun7i-a20-bananapi.dtb.uimg. I think you're right, mkimage is probably the way to do it, but when I list all the image types that mkimage can generate, there isn't a clear fit

Code:

mkimage -T list

Invalid image type, supported are:
   aisimage         Davinci AIS image
   atmelimage       ATMEL ROM-Boot Image
   copro            Coprocessor Image
   filesystem       Filesystem Image
   firmware         Firmware
   firmware_ivt     Firmware with HABv4 IVT
   flat_dt          Flat Device Tree
   fpga             FPGA Image
   gpimage          TI Keystone SPL Image
   imx8image        NXP i.MX8 Boot Image
   imx8mimage       NXP i.MX8M Boot Image
   imximage         Freescale i.MX Boot Image
   invalid          Invalid Image
   kernel           Kernel Image
   kernel_noload    Kernel Image (no loading done)
   kwbimage         Kirkwood Boot Image
   lpc32xximage     LPC32XX Boot Image
   mtk_image        MediaTek BootROM loadable Image
   multi            Multi-File Image
   mxsimage         Freescale MXS Boot Image
   omapimage        TI OMAP SPL With GP CH
   pblimage         Freescale PBL Boot Image
   pmmc             TI Power Management Micro-Controller Firmware
   ramdisk          RAMDisk Image
   rkimage          Rockchip Boot Image
   rksd             Rockchip SD Boot Image
   rkspi            Rockchip SPI Boot Image
   script           Script
   socfpgaimage     Altera SoCFPGA CV/AV preloader
   socfpgaimage_v1  Altera SoCFPGA A10 preloader
   standalone       Standalone Program
   stm32image       STMicroelectronics STM32 Image
   sunxi_egon       Allwinner eGON Boot Image
   sunxi_toc0       Allwinner TOC0 Boot Image
   tee              Trusted Execution Environment Image
   ublimage         Davinci UBL image
   vybridimage      Vybrid Boot Image
   x86_setup        x86 setup.bin
   zynqimage        Xilinx Zynq Boot Image
   zynqmpbif        Xilinx ZynqMP Boot Image (bif)
   zynqmpimage      Xilinx ZynqMP Boot Image
Back to top
View user's profile Send private message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Wed Nov 16, 2022 1:11 am    Post subject: Reply with quote

Interesting, I just recompiled uboot with CONFIG_SUPPORT_PASSING_ATAGS=y, and now it's able to get as far as "Starting kernel ...". But, it hangs there.
Back to top
View user's profile Send private message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Wed Nov 16, 2022 4:29 pm    Post subject: Reply with quote

I just tried booting with the new uboot but with the old (working) kernel. The result is the same, "Staring kernel..." and then hangs. I think that this suggests that the issue is with uboot or the uboot configuration, and not with the kernel.
Back to top
View user's profile Send private message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Wed Nov 16, 2022 5:09 pm    Post subject: Reply with quote

I found a file called u-boot-dtb.img in the github folder, which sounds like it might be what we need. I tried again with a boot.cmd file that looks like

Code:
setenv bootargs console=ttyS0,115200 console=tty2 root=/dev/mmcblk0p2 rootwait panic=10
fatload mmc 0 40008000 uImage
fatload mmc 0 4a000000 u-boot-dtb.img
bootm 40008000  - 4a000000


Note the - for the address of the initrd. The example from a few posts back had that line as

Code:
bootm ${kernel_addr_r} [$ramdisk_addr_r}|-] [${fdt_addr_r}]


I didn't notice this before, but it looks like the address of the initrd is optional, but the fdt file is not. After generating a new boot.scr file, I now get a message

Code:
ERROR: uImage is not a fdt - must RESET the board to recover.
EHCI failed to shut down host controller.
Loading Kernel Image
Staring kernel ...


Okay, it looks like u-boot-dtb.img may not have been the right choice. But the message also calls it a uImage, weirdly implying that it's trying to load it as a kernel.
Back to top
View user's profile Send private message
pingtoo
Guru
Guru


Joined: 10 Sep 2021
Posts: 423
Location: Richmond Hill, Canada

PostPosted: Wed Nov 16, 2022 8:52 pm    Post subject: Reply with quote

Found a better source https://linux-sunxi.org/Manual_build_howto

Summary of what I learn from above and I think it will apply for your case, (this is about mainline Linux, no info for U-Boot)
    Command to use for building mainline linux for Banana Pi (sunxi-a20)
  • kernel manual config:
    • make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

  • Kernel:
    • ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make -j4 zImage

  • Modules:
    • ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make -j4 modules
      ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make modules_install

  • DTB:
    • ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make -j4 dtbs
      in linux build dir/arch/arm/boot/dts/
      filename: sun7i-a20-bananapi.dtb

  • boot.scr
    • mkimage -C none -A arm -T script -d boot.cmd boot.scr


  • boot.cmd for mainline kernel
    Code:
    setenv bootargs console=ttyS0,115200n8 console=tty1 root=/dev/mmcblk0p2 rootwait panic=10
    fatload mmc 0:1 0x49000000 sun7i-a20-bananapi.dtb
    fatload mmc 0:1 0x46000000 zImage
    bootz 0x46000000 - 0x49000000

  • extlinux.conf
    Code:
    TIMEOUT 3
    DEFAULT default
    MENU TITLE Boot menu

    LABEL default
       MENU LABEL Default
            LINUX /zImage
            FDT /sun7i-a20-bananapi.dtb
            APPEND root=/dev/mmcblk0p2 rootwait console=ttyS0,115200n8 console=tty1 panic=10

    LABEL exit (leave extlinux(pxe) mode and drop to use boot.scr
       MENU LABEL Local boot script (boot.scr)
            LOCALBOOT 1


  • You can drop the "ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-" from command line if you are building inside BananaPi.
  • root=dev/mmcblk0p2, if your rootfs is somewhere else please change accordingly.
  • I have not yet figure out what is the error "EHCI failed to shut down host controller."
  • .dtb file can be placed directly, it have same header as uImage so it can be use where it is expected.
Back to top
View user's profile Send private message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Wed Nov 16, 2022 10:38 pm    Post subject: Reply with quote

Okay, what about the load address for sun7i-a20-bananapi-m1-plus.dtb? In this example, it's different from the address for uImage. Running

Code:
mkimage -l sun7i-a20-bananapi-m1-plus.dtb
just returns

Code:
Image contains unit addresses @, this will break signing
FIT description: unavailable
Created:         unavailable
Can't find images parent node '/images' (FDT_ERR_NOTFOUND)


It's a binary, so opening it in a text editor doesn't reveal the address. As a guess, I tried 0x49000000. Here's the boot.cmd file

Code:
setenv bootargs console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootwait panic=10
fatload mmc 0:1 0x49000000 sun7i-a20-bananapi-m1-plus.dtb
fatload mmc 0:1 0x40008000 uImage
bootm 0x40008000 - 0x49000000


Now, the boot sequence seems to go a bit further. I get

Code:
## Flattened Device Tree blot at 49000000
Booting using the fdt blob at 0x49000000
EHCI failed to shut down host controller.
Loading Kernel Image
Loading Device Tree to 49ff6000, end 49fff684 ... OK
Starting kernel ....


And then it hangs.
Back to top
View user's profile Send private message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Wed Nov 16, 2022 10:44 pm    Post subject: Reply with quote

Wait, that setup was still using the old (working) kernel. I just tried swapping in the new kernel, and it booted! I am logged in now, and uname -a confirms that it's running the new kernel.

Do we know if 0x49000000 is universally correct for any *.dtb, or was it just a lucky guess that because it worked for sun7i-a20-bananapi.dtb it would also work for sun7i-a20-bananapi-m1-plus.dtb?

Also, I'm not sure what the forum etiquette is, but I think we should change the thread's title. The bug that originally prompted it was a failure to connect to the network (which is now working!), but the solution was almost entirely to do with the boot loader.
Back to top
View user's profile Send private message
pingtoo
Guru
Guru


Joined: 10 Sep 2021
Posts: 423
Location: Richmond Hill, Canada

PostPosted: Wed Nov 16, 2022 10:50 pm    Post subject: Reply with quote

Why sun7i-a20-bananapi-m1-plus.dtb?

I think it should be sun7i-a20-bananapi.dtb.

Do you also have the usb-uart hookup? Some message will only display on serial port, so may be there are more there.

try add setenv bootm_boot_mode=sec into boot.cmd or rebuild u-boot with CONFIG_ARMV7_LPAE=n (search for "Use LPAE page table format" in menuconfig)
Back to top
View user's profile Send private message
pingtoo
Guru
Guru


Joined: 10 Sep 2021
Posts: 423
Location: Richmond Hill, Canada

PostPosted: Wed Nov 16, 2022 10:53 pm    Post subject: Reply with quote

OK, since it is working you can ignore my previous post, they are target for old sunxi kernel.


If you are satisfy current situation, just modify title and add [solved] to title,
Back to top
View user's profile Send private message
pingtoo
Guru
Guru


Joined: 10 Sep 2021
Posts: 423
Location: Richmond Hill, Canada

PostPosted: Wed Nov 16, 2022 10:56 pm    Post subject: Reply with quote

[quote="jyoung"]Do we know if 0x49000000 is universally correct for any *.dtb, or was it just a lucky guess that because it worked for sun7i-a20-bananapi.dtb it would also work for sun7i-a20-bananapi-m1-plus.dtb?]/quote]

0x49000000 I guest it just an address far enough so the kernel will not overlap especially for zImage,
Back to top
View user's profile Send private message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Wed Nov 16, 2022 11:49 pm    Post subject: Reply with quote

I have the USB UART adapter, but I haven't tried it out yet since the new uboot was able to display. Is there a good wiki or tutorial on how to use it? From what I'm seeing, the procedure would be to connect the adapter to the appropriate pins (excluding the 5V pin), start minicom on my desktop, and then boot up the BPI, yes?
Back to top
View user's profile Send private message
pingtoo
Guru
Guru


Joined: 10 Sep 2021
Posts: 423
Location: Richmond Hill, Canada

PostPosted: Thu Nov 17, 2022 1:13 pm    Post subject: Reply with quote

jyoung wrote:
I have the USB UART adapter, but I haven't tried it out yet since the new uboot was able to display. Is there a good wiki or tutorial on how to use it? From what I'm seeing, the procedure would be to connect the adapter to the appropriate pins (excluding the 5V pin), start minicom on my desktop, and then boot up the BPI, yes?


You can follow https://bananapi.gitbook.io/bpi-m1/en/bpi-m1uartinterface
Back to top
View user's profile Send private message
jyoung
Guru
Guru


Joined: 20 Mar 2007
Posts: 368

PostPosted: Fri Nov 18, 2022 6:54 pm    Post subject: Reply with quote

If I'm reading this tutorial right minicom has to be started on the BPI, yes? But, we're looking for messages at boot time, correct? Would the boot loader broadcast through the serial port before minicom is started? Sorry for the confusion, I've never used these tools before.

Also, as of now there are no longer any signs that anything is wrong with the system. It is kind of weird that the old kernel won't load with the new boot loader. On the other hand, it is really old, and I'm not sure that we need to trouble shoot it.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 51543
Location: 56N 3W

PostPosted: Fri Nov 18, 2022 9:39 pm    Post subject: Reply with quote

jyoung,

If the kernel has serial port support, you need to tell it to put the console on whatever it calls the serial port.
It can go onto the normal HDMI console too.

I use
Code:
console=tty0 console=ttyS0,115200n8 console=ttyAMA0,115200n8
on the kernel command line.
console=tty0 is the normal console.
console=ttyS0,115200n8 console=ttyAMA0,115200n8 is the serial port to use, here there are two as the nane changes from ttyS0 to ttyAMA0. the 115200n8 is the serial part setup.

That much gets you kernel messages on the serial port but not a login prompt.
For a login prompt /etc/inittab needs
Code:
# SERIAL CONSOLES
s0:12345:respawn:/sbin/agetty -L 115200 ttyAMA0 vt100
see the comments in the file.

115200n8 in 115200 baud. No stop bit and 8 data bits.
minicom needs to be set up to match, or you wont lie what you see, if you see anything :)

Play with minicom and the USB/Serial port before you try to talk to anything else.
Connect The Tx and RX wires on the adaptor together. This is called a loopback test.

What you type into minicom will go out of the Tx wire and back in the RX wire and appear in minicom as an 'echo'
If you get two copies, you probably have 'local echo' in minicom set to on. Turn that off.
The BPI will echo everything you send it when all is well.

If you separate the Tx and Rx wires your typing will not be echoed.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
pingtoo
Guru
Guru


Joined: 10 Sep 2021
Posts: 423
Location: Richmond Hill, Canada

PostPosted: Fri Nov 18, 2022 10:04 pm    Post subject: Reply with quote

jyoung wrote:
If I'm reading this tutorial right minicom has to be started on the BPI, yes? But, we're looking for messages at boot time, correct? Would the boot loader broadcast through the serial port before minicom is started? Sorry for the confusion, I've never used these tools before.

Also, as of now there are no longer any signs that anything is wrong with the system. It is kind of weird that the old kernel won't load with the new boot loader. On the other hand, it is really old, and I'm not sure that we need to trouble shoot it.


minicom is to run on you other computer where usb end is connected, not on BPI

if you really want to use the old kernel, you can see the other post that I asked you to put in the bootm_boot_mode=sec in boot.cmd.

I think by default serial port does not have tty listen for incoming, so once past u-boot and kernel boot up into multi-user mode, you will find that minicom stop working. So please follow Neddy advise setup /etc/inittab to have agetty listen on the serial device. As for the kernel command line, it is optional, if you don't setup as suggested, then you will not see linux kernel messages on serial console until the agetty running.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM All times are GMT
Goto page Previous  1, 2, 3, 4
Page 4 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum