Template:MCUXPRESSO U-Boot Demo: Difference between revisions
From Variscite Wiki
(Add title conditional to Zephyr wiki page) |
No edit summary |
||
| Line 2: | Line 2: | ||
| VAR-SOM-MX93=<!-- -->{{#lst:MCUXpresso_Platform_Customization|VAR-SOM-MX93_RUNNING_DEMO_SECTION}} | | VAR-SOM-MX93=<!-- -->{{#lst:MCUXpresso_Platform_Customization|VAR-SOM-MX93_RUNNING_DEMO_SECTION}} | ||
| #default=<!-- | | #default=<!-- | ||
-->{{#ifeq: {{#urlget:title}} | Zephyr | === Running a demo from U-Boot === | == Running a demo from U-Boot == }} | -->{{#ifeq: {{#urlget:title}} | Zephyr | | ||
=== Running a demo from U-Boot === | |||
---- | | |||
== Running a demo from U-Boot == | |||
}} | |||
{{#if: {{#var:SOC_HAS_SCU}} | | {{#if: {{#var:SOC_HAS_SCU}} | | ||
Revision as of 20:26, 12 February 2025
Running a demo from U-Boot
To allow Cortex-M accessing shared resources without experiencing Linux kernel conflicts, a dedicated device tree must be loaded.
To enable Cortex-M:
=> setenv use_ yes; saveenv
To disable Cortex-M:
=> setenv use_ no; saveenv
Binary demos must be loaded to the memory type used for linking.
To use TCM:
=> setenv _addr 0x7E0000; saveenv
To use DDR:
=> setenv _addr 0x7E000000; saveenv
To set the name of the Cortex-M binary
=> setenv _bin myapp.bin; saveenv
The .bin file is expected in the folder /boot of the booting media.
The U-Boot boot command will handle loading the Cortex-M firmware and start Linux for .
For testing, it is possible to run the firmware manually:
=> run loadbin && run runbin
Additional details and step by step procedure to run each of the demos is available [/blob/// online] or in the following document:
/freertos-variscite//
For Yocto Dunfell and newer, this process can be simplified using /etc/remoteproc/variscite-rproc-u-boot
Please refer to the Yocto Scripts section below for more information
Please refer to the Yocto Scripts section below for more information