AM625: VxWorks boot with SDK u-boot

Koichiro Tashiro

Part Number: AM625

Hi,

My customer is evaluating AM625x and their target OS is VxWorks.
When the customer uses u-boot in TI processor SDK v.8.06, it works fine.
But with SDK v.9.00 below error is generated.
Command sequence used and an error generated are below.

=>fatload mmc 1:1 0x93000000 uVxWorks
3698844 bytes read in 96 ms (36.7 MiB/s)
=> fatload mmc 1:1 0x90000000 k3-am625-sk.dtb
52524 bytes read in 17 ms (2.9 MiB/s)
=> bootm 0x93000000 - 0x90000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Is there any reason SDK 9.00 does not work to boot VxWorks?

Thanks and regards,
Koichiro Tashiro

over 2 years ago

0 Hong Guan64 over 2 years ago

TI__Guru 68960 points

Hello Koichiro,
Will you share the "uVxWorks" file used in your testing?
Best,
-Hong

0 Koichiro Tashiro over 2 years ago in reply to Hong Guan64

TI__Mastermind 22945 points

Hi Hong,

I sent files offline.

Thanks and regards,
Koichiro Tashiro

0 Hong Guan64 over 2 years ago in reply to Koichiro Tashiro

TI__Guru 68960 points

Hello Koichiro,
I received your email.
I'll test it, and get back to you in few days.
Best,
-Hong

0 Koichiro Tashiro over 2 years ago in reply to Hong Guan64

TI__Mastermind 22945 points

Hi Hong,

Any updates for this item?

Thanks and regards,
Koichiro Tashiro

0 Hong Guan64 over 2 years ago in reply to Koichiro Tashiro

TI__Guru 68960 points

Hello Koichiro,
Loading image (i.e. VxWorks binary) by u-boot "bootm..." uses boot_get_kernel() in bootm.c with "legacy image format".
git.ti.com/gitweb
- In SDK 8.6 u-boot (2021.01), "CONFIG_LEGACY_IMAGE_FORMAT=y" => loading legacy image format binary (VxWorks binary) is ok.
- In SDK 9.0 u-boot (2023.04), "CONFIG_LEGACY_IMAGE_FORMAT" is NOT set by default to support loading secure FIT image for Linux kernel/dtb => loading legacy image format binary (i.e. VxWorks) is NOT possible with the default u-boot configurations.
git.ti.com/gitweb

User is still able to customize "bootm..." cmd to load image (i.e. VxWorks binary) by enabling "CONFIG_LEGACY_IMAGE_FORMAT=y" when building u-boot in SDK 9.0

Best,
-Hong

0 Koichiro Tashiro over 2 years ago in reply to Hong Guan64

TI__Mastermind 22945 points

Hi Hong,

Hong Guan64 said:
User is still able to customize "bootm..." cmd to load image (i.e. VxWorks binary) by enabling "CONFIG_LEGACY_IMAGE_FORMAT=y" when building u-boot in SDK 9.0

The customer enabled "CONFIG_LEGACY_IMAGE_FORMAT=y" and now the error with bootm command was solved.
But the system stops at "Starting kernel..." and VxWorks cannot launch.
So they are planning to keep using SDK v8.6 u-boot.
Do you have any concerns to use v8.6?

Thanks and regards,
Koichiro Tashiro

+1 Hong Guan64 over 2 years ago in reply to Koichiro Tashiro

TI__Guru 68960 points

Koichiro Tashiro said:
So they are planning to keep using SDK v8.6 u-boot.
Do you have any concerns to use v8.6?

Using SDK8.6 u-boot to load VxWorks would work
Best,
-Hong

0 Koichiro Tashiro over 2 years ago in reply to Hong Guan64

TI__Mastermind 22945 points

Hi Hong,

Thanks. The customer use SDK8.6 u-boot.

Thanks and regards,
Koichiro Tashiro

Processors

Processors forum

AM625: VxWorks boot with SDK u-boot