[tbot] tbot: board hangs if no autoload
Harald Seiler
hws at denx.de
Thu Nov 15 08:36:56 UTC 2018
Hi Stefano!
Yes, TBot waits for an autoboot prompt. You can disable this by setting
`autoboot_prompt` in your UBootMachine to the U-Boot prompt.
class MyUBoot(board.UBootMachine):
prompt = "=> "
autoboot_prompt = "=> "
I know this is more of a hack and I will add a proper way to do this in
a future release (keep an eye on the CHANGELOG, there will be a lot of
small convenience features like this in the next versions!)
--
Harald
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-62 Fax: +49-8142-66989-80 Email: hws at denx.de
On Wed, 2018-11-14 at 18:53 +0100, Stefano Babic wrote:
> Hi Harald, Heiko,
>
> I am just moving my first steps with tbot. I like that I can derive the
> boards, and setting my HomeLab and one board (mira) is very easy and
> simple now.
>
> I wasted some time because interactive_uboot hangs. After checking the
> code, I see that you expects the autoload string, that is common on most
> boards...rather not on all. In fact, my board had no "bootcmd" set, and
> tbot then hangs forever. Without bootcmd, the board goes into U-Boot
> prompt without shoowing the "autoload" string with timeout.
>
> This is the output of "interactive_board":
>
> stefano at papero:~/Projects/internal/tbot-denx$ tbot -b boards/mira.py
> interactive_board
> Warning: Failed to load /home/stefano/Projects/internal/tbot-denx/tc/pwd.py
> TBot starting ...
> ├─Calling interactive_board ...
> │ ├─POWERON (mira)
> Trying 192.168.178.37...
> Connected to raspbx.fritz.box.
> Escape character is '^]'.
>
> ser2net port 2012 device /dev/ttyUSB12 [115200 N81] (Debian GNU/Linux)
>
> �
> U-Boot SPL 2016.05-00276-g176c732-dirty (Jun 21 2016 - 20:04:29)
> Boot device 1
> Trying to boot from MMC1
> mmc_load_image_raw_sector: mmc block read error
> ** ext4fs_devread read error - block
> Failed to mount ext2 filesystem...
> spl_load_image_ext: ext4fs mount err - 0
>
> U-Boot SPL 2016.05-00276-g176c732-dirty (Jun 21 2016 - 20:04:29)
> Boot device 1
> Trying to boot from MMC1
> mmc_load_image_raw_sector: mmc block read error
> ** ext4fs_devread read error - block
> Failed to mount ext2 filesystem...
> spl_load_image_ext: ext4fs mount err - 0
>
> U-Boot SPL 2016.05-00276-g176c732-dirty (Jun 21 2016 - 20:04:29)
> Boot device 1
> Trying to boot from MMC1
> mmc_load_image_raw_sector: mmc block read error
> ** Can't read partition table on 0:0 **
> spl: no partition table found
> Trying to boot from SPI
>
>
> U-Boot 2018.09-rc1-00105-g8e00d802e4 (Aug 17 2018 - 13:30:02 +0200)
>
> CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
> CPU: Automotive temperature grade (-40C to 125C) at 31C
> Reset cause: POR
> I2C: ready
> DRAM: 1 GiB
> NAND: 1024 MiB
> MMC: FSL_SDHC: 0
> Loading Environment from SPI Flash... SF: Detected n25q128 with page
> size 256 Bytes, erase size 64 KiB, total 16 MiB
> OK
> In: serial
> Out: serial
> Err: serial
> Net: FEC [PRIME]
> =>
>
> No autoload, just the prompt. In this case, tbot refuse to go on.
>
> After setting "bootcmd" (and then I have the "autoload" string),
> everything is fine.
>
> Regards,
> Stefano
>
>
>
More information about the tbot
mailing list