Hi Milosz, Yes, You have mentioned good point. I have changed in Job file. But i would like to add one more point .. If any one refer might useful for them. In the Job description I am calling u-boot method to boot up to linux. So that, Default base.jinja2 file calling Setting prompt string to ['Starting Kernel'] But In this device getting Booting Linux... I have changed the prompt string by using {% set uboot_final_message = "Booting Linux" %} in device-type jinja2 file. With the above modifications i am able to boot and test. Setting prompt string to ['Booting Linux'] http://10.10.0.69/scheduler/job/516#L80bootloader-commands: Wait for prompt ['Booting Linux'] (timeout 00:04:49) http://10.10.0.69/scheduler/job/516#L81run xa_boot http://10.10.0.69/scheduler/job/516#L82SF: Detected s25fl512s_256k with page size 512 Bytes, erase size 256 KiB, total 64 MiB http://10.10.0.69/scheduler/job/516#L83device 0 offset 0xc0000, size 0x8000 http://10.10.0.69/scheduler/job/516#L84SF: 32768 bytes @ 0xc0000 Read: OK http://10.10.0.69/scheduler/job/516#L85Current Mode: Read Mode (3-byte Addr) (RZ/A1 reset value) http://10.10.0.69/scheduler/job/516#L86SF: Dual SPI mode http://10.10.0.69/scheduler/job/516#L87SF: Detected s25fl512s_256k with page size 512 Bytes, erase size 256 KiB, total 64 MiB http://10.10.0.69/scheduler/job/516#L88New Mode: Quad I/O Read Mode (4-byte Addr) http://10.10.0.69/scheduler/job/516#L89Booting Linux... http://10.10.0.69/scheduler/job/516#L90end: 1.4.3 bootloader-commands (duration 00:00:00) [common] http://10.10.0.69/scheduler/job/516#L91end: 1.4 uboot-commands (duration 00:00:11)
Thanks for your kind response!!
Regards Nagendra S
On Tue, Jun 2, 2020 at 2:56 PM Milosz Wasilewski < milosz.wasilewski@linaro.org> wrote:
On Mon, 1 Jun 2020 at 18:02, Nagendra Singamsetti nag.singam91@gmail.com wrote:
Hi Team, I am using U-boot method to boot up to linux. But at the end of booting means before gets the login prompt it got
hanged at here..
[ 3.759014] Console: switching to colour dummy device 80x30[?25lfbv -
The Framebuffer Viewer/root/images/renesas_logo-800x480.jpg800 x 480[?25hWelcome to Buildroot
after 2 minutes got buildroot login: [ 90.929835] random: crng init done due to this Lava did not fetch "root" string and unable to login. And i
have seen stange string in lava while booting
[?25h .
I am able to boot manually (with out lava) with out an issue. And i did
not get [?25h string ..
How to avoid this problem .Attaching job description/device dictionary
files .
[ 2.837060] Run /sbin/init as init process�Starting logging: OKread-only
file system detected...doneStarting network: OKWed Oct 31 09:00:00 UTC 2018[ 3.759014] Console: switching to colour dummy device 80x30[?25lfbv - The Framebuffer Viewer/root/images/renesas_logo-800x480.jpg800 x 480[?25hWelcome to Buildrootbuildroot login: [ 90.929835] random: crng init done
This unprintable character is not an issue. Your real problem it the job file. You're waiting for the string with newlines which is not a great idea. This is what you have: - message: "Welcome to Buildroot buildroot login: root (auto login)"
This is what you should try: - message: "Welcome to Buildroot"
milosz
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users