On Mon, Jun 23, 2025 at 7:24 AM Hina Hafeez hina.hafeez@10xengineers.ai wrote:
Hi Milosz, I am trying to test boot to the console and its loading with ymodem is just to transfer my bootloader to the board via UART.
In this case I think you should try using "deploy to flasher". Flasher is just an arbitrary script LAVA calls. As I mentioned before I'm doing a similar deployment with am64xx board from TI. Here is the device dictionary: https://lava.infra.foundries.io/scheduler/device/am64xx-evm-01/devicedict example health check job: https://lava.infra.foundries.io/scheduler/job/80877/definition
In my case it's a bit different. I'm using a pre-built u-boot image. The script in u-boot copies tested software from USB stick to emmc on the board. But the initial part is what you're trying to do. The pre-built u-boot is loaded via UART. TI uses xmodem and ymodem, but it's a minor detail. This is what the script does
stty -F $UART_PATH 115200 echo "Sending tiboot3.bin (1st round)" sb --quiet --xmodem "/usr/share/ti-flasher/tiboot3.bin" > $UART_PATH < $UART_PATH echo "Sending tiboot3.bin (2nd round)" sb --quiet --xmodem "/usr/share/ti-flasher/tiboot3.bin" > $UART_PATH < $UART_PATH echo "Sending tispl.bin" sb --quiet --ymodem "/usr/share/ti-flasher/tispl.bin" > $UART_PATH < $UART_PATH sleep 3 echo "Sending u-boot.img" sb --ymodem "/usr/share/ti-flasher/u-boot.img" > $UART_PATH < $UART_PATH
It might not be ideal from your perspective as there is a reboot between "flashing" and "booting" phases. With flasher method you should use "minimal" boot.
Ideally the script would run in "boot" phase, but I don't know how to do that.
Hope this helps.
Best Regards, Milosz