cdocutils.nodes document q)q}q(U nametypesq}q(Xbooting u-boot from the networkqNXloadingqNXu-boot environmentqNXFbooting tiboot3.bin, tispl.bin and u-boot.img from emmc boot partitionq NXu-boot splash screenq NX device treesq NXj721e-evm-usb-30-hostq Xwriting-to-qspi-from-u-boot-1q Xreading-from-partitionqXstopqNXadding-a-splash-screenqXbooting linux from the networkqNXnorqNX)viewing, reading and writing to partitionqNXviewing sata devicesqNXstep 1: downloading ccsqNXmultiple interfacesqNXmanual network configurationqNXbuild informationqNX available ram for image downloadqNXdra7xx supportqNXstep 3: loading symbol filesqNX%updating an sd card or emmc using dfuqNXnetwork configuration via dhcpqNXview partition contentsqNX;booting from sd/emmc from spl (single stage or falcon mode)qNXnandq NXgeneral informationq!NX%identifying partition filesystem typeq"NXwriting to spi from u-bootq#NX k3-boot-flowq$Xwriting-to-qspi-using-dfuq%Xwriting-to-qspi-from-u-bootq&Xbooting-from-qspiq'X+updating an sd card or emmc with raw writesq(NX setting-the-full-tool-chain-pathq)X'build and boot flow on 32-bit platformsq*NXufsq+NXwriting to nand via dfuq,NXlisting-nand-partitionsq-X"updating an sd card from a host pcq.NXpartitioning emmc from u-bootq/NXu-boot release notesq0NX6booting-from-qspi-from-spl-single-stage-or-falcon-modeq1Xoverviewq2NXtroubleshootingq3NXBbuild and boot flow on 64-bit platforms (based on k3 architecture)q4NXam43xx supportq5NXuboot spl debugging tipsq6NX!disabling gigabit phy advertisingq7NX"booting linux from sd card or emmcq8NXu-bootq9NXcompiling-mlo-and-u-bootq:Xerasing-partitionq;X4erasing, reading and writing to/from nand partitionsqXu-boot user's guideq?NXcompiling-r5-and-arm64-imagesq@Xsetting-the-tool-chain-pathqAX boot-flowqBXuartqCNXddr3 eccqDNXam335xqEX ospi/qspiqFNXgetting the u-boot source codeqGNX!usb device firmware upgrade (dfu)qHNXhyperbus and hyperflashqINXspiqJNX'booting kernel and filesystem from nandqKNX remoteprocqLNX nand bootqMNXviewing partitionsqNNXbooting linux from usb storageqONXddr3 ecc in keystone-iiqPNXsataqQNXbooting from spiqRNXnetwork (wired or usb client)qSNXsd, emmc or usb storageqTNXbooting-from-qspi-from-u-bootqUXwrite-file-to-partitionqVXnetworking-environmentqWXddr3 ecc handlingqXNXinitializationqYNXwriting to nor from u-bootqZNX dfu-j721eq[Xam654/j721e supportq\NXbooting from norq]NX*usb peripheral boot mode (spl-dfu support)q^NX,step 2: creating a target configuration fileq_NX$booting u-boot from the console uartq`NXcleaning-the-sourcesqaX/booting mlo and u-boot from emmc boot partitionqbNXwriting-to-partitionqcXstartingqdNuUsubstitution_defsqe}qfUparse_messagesqg]qh(cdocutils.nodes system_message qi)qj}qk(U rawsourceqlUUparentqmcdocutils.nodes section qn)qo}qp(hlUhmhn)qq}qr(hlUhmhn)qs}qt(hlUhmhn)qu}qv(hlUhmhUsourceqwcdocutils.nodes reprunicode qxX3source/linux/Foundational_Components/U-Boot.rst.incqyqz}q{bUtagnameq|Usectionq}U attributesq~}q(Udupnamesq]Uclassesq]Ubackrefsq]Uidsq]qUu-bootqaUnamesq]qh9auUlineqKUdocumentqhUchildrenq]q(cdocutils.nodes title q)q}q(hlXU-Bootqhmhuhwhzh|Utitleqh~}q(h]h]h]h]h]uhKhhh]qcdocutils.nodes Text qXU-Bootqq}q(hlhhmhubaubcdocutils.nodes comment q)q}q(hlXZconvert from page http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User%27s_GuidehmhuhwhxXQsource/linux/Foundational_Components/U-Boot/Linux_Core_U-Boot_Users_Guide.rst.incqq}qbh|Ucommentqh~}q(U xml:spaceqUpreserveqh]h]h]h]h]uhKhhh]qhXZconvert from page http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User%27s_Guideqq}q(hlUhmhubaubhshn)q}q(hlUhmhuhwhzh|h}h~}q(h]h]h]h]qUu-boot-release-notesqah]qh0auhK hhh]q(h)q}q(hlXU-Boot Release Notesqhmhhwhzh|hh~}q(h]h]h]h]h]uhK hhh]qhXU-Boot Release Notesqq}q(hlhhmhubaubhn)q}q(hlUhmhhwhzh|h}h~}q(h]h]h]h]qUbuild-informationqah]qhauhK hhh]q(h)q}q(hlXBuild Informationqhmhhwhzh|hh~}q(h]h]h]h]h]uhK hhh]qhXBuild Informationqq}q(hlhhmhubaubcsphinx.ext.ifconfig ifconfig q)q}q(hlUhmhhwhzh|Uifconfigqh~}q(UexprqXCONFIG_sdk in ('PLSDK')h]h]h]h]h]uhKhhh]qcdocutils.nodes paragraph q)q}q(hlXlPlease refer to `U-Boot Build Information `__ for details.hmhhwhzh|U paragraphqh~}q(h]h]h]h]h]uhKhhh]q(hXPlease refer to qЅq}q(hlXPlease refer to hmhubcdocutils.nodes reference q)q}q(hlXO`U-Boot Build Information `__h~}q(UnameXU-Boot Build InformationUrefuriqX0Release_Specific_PLSDK_Release_Notes.html#u-booth]h]h]h]h]uhmhh]qhXU-Boot Build Informationqمq}q(hlUhmhubah|U referencequbhX for details.q݅q}q(hlX for details.hmhubeubaubh)q}q(hlUhmhhwhzh|hh~}q(hXCONFIG_sdk in ('PSDKLA')h]h]h]h]h]uhKhhh]qh)q}q(hlX(Please refer to Yocto build for details.qhmhhwhzh|hh~}q(h]h]h]h]h]uhKhhh]qhX(Please refer to Yocto build for details.q酁q}q(hlhhmhubaubaubeubhn)q}q(hlUhmhhwhzh|h}h~}q(h]h]h]h]qU known-issuesqah]qh=auhKhhh]q(h)q}q(hlX Known Issuesqhmhhwhzh|hh~}q(h]h]h]h]h]uhKhhh]qhX Known Issuesqq}q(hlhhmhubaubh)q}q(hlUhmhhwhzh|hh~}q(hXCONFIG_sdk in ('PLSDK')h]h]h]h]h]uhKhhh]qh)q}r(hlXtPlease refer to `U-Boot Known Issues `__ for details.hmhhwhzh|hh~}r(h]h]h]h]h]uhKhhh]r(hXPlease refer to rr}r(hlXPlease refer to hmhubh)r}r(hlXW`U-Boot Known Issues `__h~}r(UnameXU-Boot Known IssueshX=Release_Specific_PLSDK_Release_Notes.html#u-boot-known-issuesh]h]h]h]h]uhmhh]r hXU-Boot Known Issuesr r }r (hlUhmjubah|hubhX for details.r r}r(hlX for details.hmhubeubaubh)r}r(hlUhmhhwhzh|hh~}r(hXCONFIG_sdk in ('PSDKLA')h]h]h]h]h]uhKhhh]rh)r}r(hlXiPlease refer to `Known Issues `__ for details.hmjhwhzh|hh~}r(h]h]h]h]h]uhK!hhh]r(hXPlease refer to rr}r(hlXPlease refer to hmjubh)r}r(hlXL`Known Issues `__h~}r(UnameX Known IssueshX9Release_Specific_PSDKLA_Release_Notes.html#issues-trackerh]h]h]h]h]uhmjh]rhX Known Issuesrr }r!(hlUhmjubah|hubhX for details.r"r#}r$(hlX for details.hmjubeubaubh)r%}r&(hlXPhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_U-Boot_Splash_ScreenhmhhwhxX\source/linux/Foundational_Components/U-Boot/Processor_SDK_Linux_U-Boot_Splash_Screen.rst.incr'r(}r)bh|hh~}r*(hhh]h]h]h]h]uhKhhh]r+hXPhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_U-Boot_Splash_Screenr,r-}r.(hlUhmj%ubaubcsphinx.addnodes highlightlang r/)r0}r1(hlUhmhhwj(h|U highlightlangr2h~}r3(UlangXcUlinenothresholdI9223372036854775807 h]h]h]h]h]uhKhhh]ubeubeubhn)r4}r5(hlUhmhuhwj(h|h}h~}r6(h]h]h]h]r7Uu-boot-splash-screenr8ah]r9h auhKhhh]r:(h)r;}r<(hlXU-Boot Splash Screenr=hmj4hwj(h|hh~}r>(h]h]h]h]h]uhKhhh]r?hXU-Boot Splash Screenr@rA}rB(hlj=hmj;ubaubcdocutils.nodes rubric rC)rD}rE(hlXAdding a splash screenrFhmj4hwj(h|UrubricrGh~}rH(h]rIUadding-a-splash-screenrJah]h]h]h]rKhauhNhhh]rLhXAdding a splash screenrMrN}rO(hljFhmjDubaubjC)rP}rQ(hlXAM335xrRhmj4hwj(h|jGh~}rS(h]rTUam335xrUah]h]h]h]rVhEauhNhhh]rWhXAM335xrXrY}rZ(hljRhmjPubaubh)r[}r\(hlX@All the code below is based on Processor Linux SDK 03.02.00..05.r]hmj4hwj(h|hh~}r^(h]h]h]h]h]uhK hhh]r_hX@All the code below is based on Processor Linux SDK 03.02.00..05.r`ra}rb(hlj]hmj[ubaubh)rc}rd(hlXThere is a frame buffer driver for am335x in the drivers/video directory called am3355x-fb.c. It makes calls to routines in board.c to set up the LCDC and frame buffer. To use it:rehmj4hwj(h|hh~}rf(h]h]h]h]h]uhKhhh]rghXThere is a frame buffer driver for am335x in the drivers/video directory called am3355x-fb.c. It makes calls to routines in board.c to set up the LCDC and frame buffer. To use it:rhri}rj(hljehmjcubaubh)rk}rl(hlXEither create a new defconfig in the configs directory or just add SPLASH to CONFIG\_SYS\_EXTRA\_OPTIONS. In this example the am335x\_evm\_defconfig is copied into a new one called am335x\_evm\_splash\_defconfig.hmj4hwj(h|hh~}rm(h]h]h]h]h]uhKhhh]rnhXEither create a new defconfig in the configs directory or just add SPLASH to CONFIG_SYS_EXTRA_OPTIONS. In this example the am335x_evm_defconfig is copied into a new one called am335x_evm_splash_defconfig.rorp}rq(hlXEither create a new defconfig in the configs directory or just add SPLASH to CONFIG\_SYS\_EXTRA\_OPTIONS. In this example the am335x\_evm\_defconfig is copied into a new one called am335x\_evm\_splash\_defconfig.hmjkubaubcdocutils.nodes literal_block rr)rs}rt(hlXCONFIG_TARGET_AM335X_EVM=y CONFIG_SPL_STACK_R_ADDR=0x82000000 CONFIG_DEFAULT_DEVICE_TREE="am335x-evm" CONFIG_SPL=y CONFIG_SPL_STACK_R=y CONFIG_SYS_EXTRA_OPTIONS="NAND,SPLASH" CONFIG_HUSH_PARSER=y CONFIG_AUTOBOOT_KEYED=yhmj4hwj(h|U literal_blockruh~}rv(UlinenosrwUlanguagerxXtexthhh]h]h]Uhighlight_argsry}h]h]uhKhhh]rzhXCONFIG_TARGET_AM335X_EVM=y CONFIG_SPL_STACK_R_ADDR=0x82000000 CONFIG_DEFAULT_DEVICE_TREE="am335x-evm" CONFIG_SPL=y CONFIG_SPL_STACK_R=y CONFIG_SYS_EXTRA_OPTIONS="NAND,SPLASH" CONFIG_HUSH_PARSER=y CONFIG_AUTOBOOT_KEYED=yr{r|}r}(hlUhmjsubaubh)r~}r(hlX_In include/configs/am335x\_evm.h, add support for the splash screen, LCDC, and gzipped bitmaps.hmj4hwj(h|hh~}r(h]h]h]h]h]uhK#hhh]rhX^In include/configs/am335x_evm.h, add support for the splash screen, LCDC, and gzipped bitmaps.rr}r(hlX_In include/configs/am335x\_evm.h, add support for the splash screen, LCDC, and gzipped bitmaps.hmj~ubaubjr)r}r(hlX[/* Splash scrren support */ #ifdef CONFIG_SPLASH #define CONFIG_AM335X_LCD #define CONFIG_LCD #define CONFIG_LCD_NOSTDOUT #define CONFIG_SYS_WHITE_ON_BLACK #define LCD_BPP LCD_COLOR16 #define CONFIG_VIDEO_BMP_GZIP #define CONFIG_SYS_VIDEO_LOGO_MAX_SIZE (1366*767*4) #define CONFIG_CMD_UNZIP #define CONFIG_CMD_BMP #define CONFIG_BMP_16BPP #endifhmj4hwj(h|juh~}r(hhh]h]h]h]h]uhM hhh]rhX[/* Splash scrren support */ #ifdef CONFIG_SPLASH #define CONFIG_AM335X_LCD #define CONFIG_LCD #define CONFIG_LCD_NOSTDOUT #define CONFIG_SYS_WHITE_ON_BLACK #define LCD_BPP LCD_COLOR16 #define CONFIG_VIDEO_BMP_GZIP #define CONFIG_SYS_VIDEO_LOGO_MAX_SIZE (1366*767*4) #define CONFIG_CMD_UNZIP #define CONFIG_CMD_BMP #define CONFIG_BMP_16BPP #endifrr}r(hlUhmjubaubh)r}r(hlXDIn arch/arm/cpu/armv7/am33xx/clock\_am33xx.c enable the LCDC clocks.rhmj4hwj(h|hh~}r(h]h]h]h]h]uhK7hhh]rhXCIn arch/arm/cpu/armv7/am33xx/clock_am33xx.c enable the LCDC clocks.rr}r(hlXDIn arch/arm/cpu/armv7/am33xx/clock\_am33xx.c enable the LCDC clocks.hmjubaubjr)r}r(hlX&cmrtc->rtcclkctrl, &cmper->usb0clkctrl, &cmper->emiffwclkctrl, &cmper->emifclkctrl, &cmper->lcdclkctrl, &cmper->lcdcclkstctrl, &cmper->epwmss2clkctrl, 0hmj4hwj(h|juh~}r(hhh]h]h]h]h]uhM hhh]rhX&cmrtc->rtcclkctrl, &cmper->usb0clkctrl, &cmper->emiffwclkctrl, &cmper->emifclkctrl, &cmper->lcdclkctrl, &cmper->lcdcclkstctrl, &cmper->epwmss2clkctrl, 0rr}r(hlUhmjubaubh)r}r(hlX@In board.c add includes for mmc, fat, lcd, and the frame buffer.rhmj4hwj(h|hh~}r(h]h]h]h]h]uhKDhhh]rhX@In board.c add includes for mmc, fat, lcd, and the frame buffer.rr}r(hljhmjubaubjr)r}r(hlX#include #include #include #include #include #include <../../../drivers/video/am335x-fb.h>hmj4hwj(h|juh~}r(hhh]h]h]h]h]uhM hhh]rhX#include #include #include #include #include #include <../../../drivers/video/am335x-fb.h>rr}r(hlUhmjubaubh)r}r(hlX|This example code is based on the AM335x Starter Kit. A GPIO controls the backlight so use GPIO\_TO\_PIN to define the GPIO.hmj4hwj(h|hh~}r(h]h]h]h]h]uhKOhhh]rhXzThis example code is based on the AM335x Starter Kit. A GPIO controls the backlight so use GPIO_TO_PIN to define the GPIO.rr}r(hlX|This example code is based on the AM335x Starter Kit. A GPIO controls the backlight so use GPIO\_TO\_PIN to define the GPIO.hmjubaubjr)r}r(hlX#define GPIO_ETH1_MODE GPIO_TO_PIN(1, 26) /* GPIO that controls backlight on EVM-SK */ #define GPIO_BACKLIGHT_EN GPIO_TO_PIN(3, 17)hmj4hwj(h|juh~}r(hhh]h]h]h]h]uhM hhh]rhX#define GPIO_ETH1_MODE GPIO_TO_PIN(1, 26) /* GPIO that controls backlight on EVM-SK */ #define GPIO_BACKLIGHT_EN GPIO_TO_PIN(3, 17)rr}r(hlUhmjubaubh)r}r(hlX4In board\_late\_init call the splash screen routine.rhmj4hwj(h|hh~}r(h]h]h]h]h]uhKYhhh]rhX2In board_late_init call the splash screen routine.rr}r(hlX4In board\_late\_init call the splash screen routine.hmjubaubjr)r}r(hlX#if !defined(CONFIG_SPL_BUILD) splash_screen(); /* try reading mac address from efuse */ mac_lo = readl(&cdev->macid0l); mac_hi = readl(&cdev->macid0h);hmj4hwj(h|juh~}r(hhh]h]h]h]h]uhM hhh]rhX#if !defined(CONFIG_SPL_BUILD) splash_screen(); /* try reading mac address from efuse */ mac_lo = readl(&cdev->macid0l); mac_hi = readl(&cdev->macid0h);rr}r(hlUhmjubaubh)r}r(hlX%The following routines enable the backlight, load the LCD timings (this example is based on Starter Kit), power on the LCD and enable it, then finally the splash screen code that registers a fat file system on mmc0. The gzipped bitmap is named splash.bmp.gz and is displayed with bmp\_display.hmj4hwj(h|hh~}r(h]h]h]h]h]uhKchhh]rhX$The following routines enable the backlight, load the LCD timings (this example is based on Starter Kit), power on the LCD and enable it, then finally the splash screen code that registers a fat file system on mmc0. The gzipped bitmap is named splash.bmp.gz and is displayed with bmp_display.rr}r(hlX%The following routines enable the backlight, load the LCD timings (this example is based on Starter Kit), power on the LCD and enable it, then finally the splash screen code that registers a fat file system on mmc0. The gzipped bitmap is named splash.bmp.gz and is displayed with bmp\_display.hmjubaubjr)r}r(hlX#if defined(CONFIG_LCD) && defined(CONFIG_AM335X_LCD) && \  !defined(CONFIG_SPL_BUILD) void lcdbacklight(int on) { gpio_request(GPIO_BACKLIGHT_EN, "backlight_en"); if (on) gpio_direction_output(GPIO_BACKLIGHT_EN, 0); else gpio_direction_output(GPIO_BACKLIGHT_EN, 1); } int load_lcdtiming(struct am335x_lcdpanel *panel) { struct am335x_lcdpanel pnltmp; pnltmp.hactive = 480; pnltmp.vactive = 272; pnltmp.bpp = 16; pnltmp.hfp = 8; pnltmp.hbp = 43; pnltmp.hsw = 4; pnltmp.vfp = 4; pnltmp.vbp = 12; pnltmp.vsw = 10; pnltmp.pxl_clk_div = 2; pnltmp.pol = 0; pnltmp.pup_delay = 1; pnltmp.pon_delay = 1; panel_info.vl_rot = 0; memcpy((void *)panel, (void *)&pnltmp, sizeof(struct am335x_lcdpanel)); return 0; } void lcdpower(int on) { lcd_enable(); } vidinfo_t panel_info = { .vl_col = 480, .vl_row = 272, .vl_bpix = 4, .priv = 0 }; void lcd_ctrl_init(void *lcdbase) { struct am335x_lcdpanel lcd_panel; memset(&lcd_panel, 0, sizeof(struct am335x_lcdpanel)); if (load_lcdtiming(&lcd_panel) != 0) return; lcd_panel.panel_power_ctrl = &lcdpower; if (am335xfb_init(&lcd_panel) != 0) printf("ERROR: failed to initialize video!"); /* Modify panel into to real resolution */ panel_info.vl_col = lcd_panel.hactive; panel_info.vl_row = lcd_panel.vactive; // lcd_set_flush_dcache(1); } void lcd_enable(void) { lcdbacklight(1); } void splash_screen(void) { struct mmc *mmc = NULL; int err; mmc = find_mmc_device(0); if (!mmc) printf("Error finding mmc device\n"); mmc_init(mmc); err = fat_register_device(&mmc->block_dev, CONFIG_SYS_MMCSD_FS_BOOT_PARTITION); if (!err) { err = file_fat_read("splash.bmp.gz", (void *)0x82000000, 0); bmp_display(0x82000000, 0, 0); } } #endifhmj4hwj(h|juh~}r(jwjxXtexthhh]h]h]jy}h]h]uhKihhh]rhX#if defined(CONFIG_LCD) && defined(CONFIG_AM335X_LCD) && \  !defined(CONFIG_SPL_BUILD) void lcdbacklight(int on) { gpio_request(GPIO_BACKLIGHT_EN, "backlight_en"); if (on) gpio_direction_output(GPIO_BACKLIGHT_EN, 0); else gpio_direction_output(GPIO_BACKLIGHT_EN, 1); } int load_lcdtiming(struct am335x_lcdpanel *panel) { struct am335x_lcdpanel pnltmp; pnltmp.hactive = 480; pnltmp.vactive = 272; pnltmp.bpp = 16; pnltmp.hfp = 8; pnltmp.hbp = 43; pnltmp.hsw = 4; pnltmp.vfp = 4; pnltmp.vbp = 12; pnltmp.vsw = 10; pnltmp.pxl_clk_div = 2; pnltmp.pol = 0; pnltmp.pup_delay = 1; pnltmp.pon_delay = 1; panel_info.vl_rot = 0; memcpy((void *)panel, (void *)&pnltmp, sizeof(struct am335x_lcdpanel)); return 0; } void lcdpower(int on) { lcd_enable(); } vidinfo_t panel_info = { .vl_col = 480, .vl_row = 272, .vl_bpix = 4, .priv = 0 }; void lcd_ctrl_init(void *lcdbase) { struct am335x_lcdpanel lcd_panel; memset(&lcd_panel, 0, sizeof(struct am335x_lcdpanel)); if (load_lcdtiming(&lcd_panel) != 0) return; lcd_panel.panel_power_ctrl = &lcdpower; if (am335xfb_init(&lcd_panel) != 0) printf("ERROR: failed to initialize video!"); /* Modify panel into to real resolution */ panel_info.vl_col = lcd_panel.hactive; panel_info.vl_row = lcd_panel.vactive; // lcd_set_flush_dcache(1); } void lcd_enable(void) { lcdbacklight(1); } void splash_screen(void) { struct mmc *mmc = NULL; int err; mmc = find_mmc_device(0); if (!mmc) printf("Error finding mmc device\n"); mmc_init(mmc); err = fat_register_device(&mmc->block_dev, CONFIG_SYS_MMCSD_FS_BOOT_PARTITION); if (!err) { err = file_fat_read("splash.bmp.gz", (void *)0x82000000, 0); bmp_display(0x82000000, 0, 0); } } #endifrr}r(hlUhmjubaubh)r}r(hlX!In mux.c define the LCDC pin mux.rhmj4hwj(h|hh~}r(h]h]h]h]h]uhKhhh]rhX!In mux.c define the LCDC pin mux.rr}r(hljhmjubaubjr)r}r(hlX#ifdef CONFIG_AM335X_LCD static struct module_pin_mux lcd_pin_mux[] = { {OFFSET(lcd_data0), (MODE(0) | PULLUDDIS)}, /* LCD-Data(0) */ {OFFSET(lcd_data1), (MODE(0) | PULLUDDIS)}, /* LCD-Data(1) */ {OFFSET(lcd_data2), (MODE(0) | PULLUDDIS)}, /* LCD-Data(2) */ {OFFSET(lcd_data3), (MODE(0) | PULLUDDIS)}, /* LCD-Data(3) */ {OFFSET(lcd_data4), (MODE(0) | PULLUDDIS)}, /* LCD-Data(4) */ {OFFSET(lcd_data5), (MODE(0) | PULLUDDIS)}, /* LCD-Data(5) */ {OFFSET(lcd_data6), (MODE(0) | PULLUDDIS)}, /* LCD-Data(6) */ {OFFSET(lcd_data7), (MODE(0) | PULLUDDIS)}, /* LCD-Data(7) */ {OFFSET(lcd_data8), (MODE(0) | PULLUDDIS)}, /* LCD-Data(8) */ {OFFSET(lcd_data9), (MODE(0) | PULLUDDIS)}, /* LCD-Data(9) */ {OFFSET(lcd_data10), (MODE(0) | PULLUDDIS)}, /* LCD-Data(10) */ {OFFSET(lcd_data11), (MODE(0) | PULLUDDIS)}, /* LCD-Data(11) */ {OFFSET(lcd_data12), (MODE(0) | PULLUDDIS)}, /* LCD-Data(12) */ {OFFSET(lcd_data13), (MODE(0) | PULLUDDIS)}, /* LCD-Data(13) */ {OFFSET(lcd_data14), (MODE(0) | PULLUDDIS)}, /* LCD-Data(14) */ {OFFSET(lcd_data15), (MODE(0) | PULLUDDIS)}, /* LCD-Data(15) */ {OFFSET(gpmc_ad8), (MODE(1) | PULLUDDIS)}, /* LCD-Data(16) */ {OFFSET(gpmc_ad9), (MODE(1) | PULLUDDIS)}, /* LCD-Data(17) */ {OFFSET(gpmc_ad10), (MODE(1) | PULLUDDIS)}, /* LCD-Data(18) */ {OFFSET(gpmc_ad11), (MODE(1) | PULLUDDIS)}, /* LCD-Data(19) */ {OFFSET(gpmc_ad12), (MODE(1) | PULLUDDIS)}, /* LCD-Data(20) */ {OFFSET(gpmc_ad13), (MODE(1) | PULLUDDIS)}, /* LCD-Data(21) */ {OFFSET(gpmc_ad14), (MODE(1) | PULLUDDIS)}, /* LCD-Data(22) */ {OFFSET(gpmc_ad15), (MODE(1) | PULLUDDIS)}, /* LCD-Data(23) */ {OFFSET(lcd_vsync), (MODE(0) | PULLUDDIS)}, /* LCD-VSync */ {OFFSET(lcd_hsync), (MODE(0) | PULLUDDIS)}, /* LCD-HSync */ {OFFSET(lcd_ac_bias_en), (MODE(0) | PULLUDDIS)},/* LCD-DE */ {OFFSET(lcd_pclk), (MODE(0) | PULLUDDIS)}, /* LCD-CLK */ /* backlight */ {OFFSET(mcasp0_ahclkr), (MODE(7) | PULLUDDIS)}, /* mcasp0_gpio */ {-1}, }; #endifhmj4hwj(h|juh~}r(hhh]h]h]h]h]uhM; hhh]rhX#ifdef CONFIG_AM335X_LCD static struct module_pin_mux lcd_pin_mux[] = { {OFFSET(lcd_data0), (MODE(0) | PULLUDDIS)}, /* LCD-Data(0) */ {OFFSET(lcd_data1), (MODE(0) | PULLUDDIS)}, /* LCD-Data(1) */ {OFFSET(lcd_data2), (MODE(0) | PULLUDDIS)}, /* LCD-Data(2) */ {OFFSET(lcd_data3), (MODE(0) | PULLUDDIS)}, /* LCD-Data(3) */ {OFFSET(lcd_data4), (MODE(0) | PULLUDDIS)}, /* LCD-Data(4) */ {OFFSET(lcd_data5), (MODE(0) | PULLUDDIS)}, /* LCD-Data(5) */ {OFFSET(lcd_data6), (MODE(0) | PULLUDDIS)}, /* LCD-Data(6) */ {OFFSET(lcd_data7), (MODE(0) | PULLUDDIS)}, /* LCD-Data(7) */ {OFFSET(lcd_data8), (MODE(0) | PULLUDDIS)}, /* LCD-Data(8) */ {OFFSET(lcd_data9), (MODE(0) | PULLUDDIS)}, /* LCD-Data(9) */ {OFFSET(lcd_data10), (MODE(0) | PULLUDDIS)}, /* LCD-Data(10) */ {OFFSET(lcd_data11), (MODE(0) | PULLUDDIS)}, /* LCD-Data(11) */ {OFFSET(lcd_data12), (MODE(0) | PULLUDDIS)}, /* LCD-Data(12) */ {OFFSET(lcd_data13), (MODE(0) | PULLUDDIS)}, /* LCD-Data(13) */ {OFFSET(lcd_data14), (MODE(0) | PULLUDDIS)}, /* LCD-Data(14) */ {OFFSET(lcd_data15), (MODE(0) | PULLUDDIS)}, /* LCD-Data(15) */ {OFFSET(gpmc_ad8), (MODE(1) | PULLUDDIS)}, /* LCD-Data(16) */ {OFFSET(gpmc_ad9), (MODE(1) | PULLUDDIS)}, /* LCD-Data(17) */ {OFFSET(gpmc_ad10), (MODE(1) | PULLUDDIS)}, /* LCD-Data(18) */ {OFFSET(gpmc_ad11), (MODE(1) | PULLUDDIS)}, /* LCD-Data(19) */ {OFFSET(gpmc_ad12), (MODE(1) | PULLUDDIS)}, /* LCD-Data(20) */ {OFFSET(gpmc_ad13), (MODE(1) | PULLUDDIS)}, /* LCD-Data(21) */ {OFFSET(gpmc_ad14), (MODE(1) | PULLUDDIS)}, /* LCD-Data(22) */ {OFFSET(gpmc_ad15), (MODE(1) | PULLUDDIS)}, /* LCD-Data(23) */ {OFFSET(lcd_vsync), (MODE(0) | PULLUDDIS)}, /* LCD-VSync */ {OFFSET(lcd_hsync), (MODE(0) | PULLUDDIS)}, /* LCD-HSync */ {OFFSET(lcd_ac_bias_en), (MODE(0) | PULLUDDIS)},/* LCD-DE */ {OFFSET(lcd_pclk), (MODE(0) | PULLUDDIS)}, /* LCD-CLK */ /* backlight */ {OFFSET(mcasp0_ahclkr), (MODE(7) | PULLUDDIS)}, /* mcasp0_gpio */ {-1}, }; #endifrr}r(hlUhmjubaubh)r}r(hlXAnd enable the LCD.rhmj4hwj(h|hh~}r(h]h]h]h]h]uhKhhh]rhXAnd enable the LCD.rr}r(hljhmjubaubjr)r}r(hlX } else if (board_is_evm_sk()) { /* Starter Kit EVM */ configure_module_pin_mux(i2c1_pin_mux); configure_module_pin_mux(gpio0_7_pin_mux); configure_module_pin_mux(rgmii1_pin_mux); configure_module_pin_mux(mmc0_pin_mux_sk_evm); #ifdef CONFIG_AM335X_LCD configure_module_pin_mux(lcd_pin_mux); #endif } else if (board_is_bone_lt()) {hmj4hwXsinternal padding after source/linux/Foundational_Components/U-Boot/Processor_SDK_Linux_U-Boot_Splash_Screen.rst.incrh|juh~}r(hhh]h]h]h]h]uhMe hhh]rhX } else if (board_is_evm_sk()) { /* Starter Kit EVM */ configure_module_pin_mux(i2c1_pin_mux); configure_module_pin_mux(gpio0_7_pin_mux); configure_module_pin_mux(rgmii1_pin_mux); configure_module_pin_mux(mmc0_pin_mux_sk_evm); #ifdef CONFIG_AM335X_LCD configure_module_pin_mux(lcd_pin_mux); #endif } else if (board_is_bone_lt()) {rr}r(hlUhmjubaubeubhn)r}r(hlUhmhuhwhzh|h}h~}r(h]h]h]h]rUtroubleshootingrah]rh3auhK(hhh]r(h)r}r(hlXTroubleshootingrhmjhwhzh|hh~}r(h]h]h]h]h]uhK(hhh]rhXTroubleshootingrr}r(hljhmjubaubcdocutils.nodes enumerated_list r)r}r(hlUhmjhwhzh|Uenumerated_listrh~}r(UsuffixrU.h]h]h]Uprefixr Uh]h]Uenumtyper Uarabicr uhK*hhh]r cdocutils.nodes list_item r )r}r(hlX+After U-boot upgrade, Kernel stops booting hmjhwhzh|U list_itemrh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlX*After U-boot upgrade, Kernel stops bootingrhmjhwhzh|hh~}r(h]h]h]h]h]uhK*h]rhX*After U-boot upgrade, Kernel stops bootingrr}r(hljhmjubaubaubaubh)r}r(hlX(Check if one of the cases below applies:rhmjhwhzh|hh~}r(h]h]h]h]h]uhK,hhh]rhX(Check if one of the cases below applies:r r!}r"(hljhmjubaubcdocutils.nodes bullet_list r#)r$}r%(hlUhmjhwhzh|U bullet_listr&h~}r'(Ubulletr(X-h]h]h]h]h]uhK.hhh]r)(j )r*}r+(hlXfNot resetting U-boot environment variables after upgrading/downgrading u-boot version From release to release, some of the u-boot environment variables may be changed. To guarantee the environment variables are correctly matching the version used, it is required to reset the u-boot environment variables When upgrading/downgrading u-boot version. When booting up a different version of u-boot, the u-boot boot process can be interruptted by hitting any key to get the u-boot prompt. Then, the following command needs to issue to reset the u-boot environment variables. | # env default -f -a | # saveenv hmj$hwhzh|jh~}r,(h]h]h]h]h]uhNhhh]r-(h)r.}r/(hlXUNot resetting U-boot environment variables after upgrading/downgrading u-boot versionr0hmj*hwhzh|hh~}r1(h]h]h]h]h]uhK.h]r2hXUNot resetting U-boot environment variables after upgrading/downgrading u-boot versionr3r4}r5(hlj0hmj.ubaubh)r6}r7(hlXFrom release to release, some of the u-boot environment variables may be changed. To guarantee the environment variables are correctly matching the version used, it is required to reset the u-boot environment variables When upgrading/downgrading u-boot version. When booting up a different version of u-boot, the u-boot boot process can be interruptted by hitting any key to get the u-boot prompt. Then, the following command needs to issue to reset the u-boot environment variables.r8hmj*hwhzh|hh~}r9(h]h]h]h]h]uhK0h]r:hXFrom release to release, some of the u-boot environment variables may be changed. To guarantee the environment variables are correctly matching the version used, it is required to reset the u-boot environment variables When upgrading/downgrading u-boot version. When booting up a different version of u-boot, the u-boot boot process can be interruptted by hitting any key to get the u-boot prompt. Then, the following command needs to issue to reset the u-boot environment variables.r;r<}r=(hlj8hmj6ubaubcdocutils.nodes block_quote r>)r?}r@(hlUh~}rA(h]h]h]h]h]uhmj*h]rBcdocutils.nodes line_block rC)rD}rE(hlUh~}rF(h]h]h]h]h]uhmj?h]rG(cdocutils.nodes line rH)rI}rJ(hlX# env default -f -arKUindentrLKhmjDhwhzh|hh~}rM(h]h]h]h]h]uhKh]rNhX# env default -f -arOrP}rQ(hljKhmjIubaubjH)rR}rS(hlX # saveenvrTjLKhmjDhwhzh|hh~}rU(h]h]h]h]h]uhKh]rVhX # saveenvrWrX}rY(hljThmjRubaubeh|U line_blockrZubah|U block_quoter[ubeubj )r\}r](hlXMix-matching U-boot and Linux kernel version There are times that users mix-match u-boot and kernel version from different SDK releases. It probably is fine in most cases, but TI recommends the u-boot and kernel are from the same SDK release. From release to release, the u-boot environemt variables may change, including load addresses, kernel image format, etc. Any of the incompatibility of these changes between u-boot and kernel will cause boot issues. Therefore, when u-boot is upgraded or downgreaded, a reset of the u-boot environment variables is requried. Please see how to reset u-boot environment variables in previous bullet. hmj$hwhzh|jh~}r^(h]h]h]h]h]uhNhhh]r_(h)r`}ra(hlX,Mix-matching U-boot and Linux kernel versionrbhmj\hwhzh|hh~}rc(h]h]h]h]h]uhK:h]rdhX,Mix-matching U-boot and Linux kernel versionrerf}rg(hljbhmj`ubaubh)rh}ri(hlXQThere are times that users mix-match u-boot and kernel version from different SDK releases. It probably is fine in most cases, but TI recommends the u-boot and kernel are from the same SDK release. From release to release, the u-boot environemt variables may change, including load addresses, kernel image format, etc. Any of the incompatibility of these changes between u-boot and kernel will cause boot issues. Therefore, when u-boot is upgraded or downgreaded, a reset of the u-boot environment variables is requried. Please see how to reset u-boot environment variables in previous bullet.rjhmj\hwhzh|hh~}rk(h]h]h]h]h]uhK`__jLKhmjhwhzh|hh~}r(h]h]h]h]h]uhKIhhh]r(hXPlease follow instructions in rr}r(hlXPlease follow instructions in hmjubh)r}r(hlXQ`U-boot User's Guide `__h~}r(UnameXU-boot User's GuidehX7Foundational_Components_U-Boot.html#u-boot-user-s-guideh]h]h]h]h]uhmjh]rhXU-boot User's Guiderr}r(hlUhmjubah|hubeubjH)r}r(hlUjLKhmjhwhzh|hh~}r(h]h]h]h]h]uhKhhh]ubeubjC)r}r(hlUhmjhwhzh|jZh~}r(h]h]h]h]h]uhKLhhh]rjH)r}r(hlX:Different boot modes ues diferent image formats. They are:rjLKhmjhwhzh|hh~}r(h]h]h]h]h]uhKLhhh]rhX:Different boot modes ues diferent image formats. They are:rr}r(hljhmjubaubaubj>)r}r(hlUhmjhwNh|j[h~}r(h]h]h]h]h]uhNhhh]rj#)r}r(hlUh~}r(j(X-h]h]h]h]h]uhmjh]r(j )r}r(hlXu-boot-spi.gphrh~}r(h]h]h]h]h]uhmjh]rh)r}r(hljhmjhwhzh|hh~}r(h]h]h]h]h]uhKNh]rhXu-boot-spi.gphrr}r(hljhmjubaubah|jubj )r}r(hlXrootfs-image.ubirh~}r(h]h]h]h]h]uhmjh]rh)r}r(hljhmjhwhzh|hh~}r(h]h]h]h]h]uhKOh]rhXrootfs-image.ubirr}r(hljhmjubaubah|jubj )r}r(hlX u-boot.binrh~}r(h]h]h]h]h]uhmjh]rh)r}r(hljhmjhwhzh|hh~}r(h]h]h]h]h]uhKPh]rhX u-boot.binrr}r(hljhmjubaubah|jubj )r}r(hlXMLO h~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXMLOrhmjhwhzh|hh~}r(h]h]h]h]h]uhKQh]rhXMLOrr}r(hljhmjubaubah|jubeh|j&ubaubh)r}r(hlUhmjhwhzh|hh~}r(hXCONFIG_sdk in ('PLSDK')h]h]h]h]h]uhKShhh]rh)r}r(hlXFor Keystone-2 platforms, U-boot can also be brought up using CCS. The step-by-step instruction on booting up u-boot with one of the boot modes or using CCS are documented in /board-support/u-boot-/board/ti/ks2_evm/README file.rhmjhwhzh|hh~}r(h]h]h]h]h]uhKUhhh]rhXFor Keystone-2 platforms, U-boot can also be brought up using CCS. The step-by-step instruction on booting up u-boot with one of the boot modes or using CCS are documented in /board-support/u-boot-/board/ti/ks2_evm/README file.rr}r(hljhmjubaubaubeubeubhwhh|h}h~}r(h]h]h]h]rUu-boot-user-s-guiderah]rh?auhKhhh]r(h)r}r(hlXU-Boot User's Guiderhmhshwhh|hh~}r(h]h]h]h]h]uhKhhh]rhXU-Boot User's Guiderr}r(hljhmjubaubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUoverviewrah]rh2auhKhhh]r (h)r }r (hlXOverviewr hmjhwhh|hh~}r (h]h]h]h]h]uhKhhh]rhXOverviewrr}r(hlj hmj ubaubh)r}r(hlX\This document covers the general use of Linux Core Release of U-Boot on following platforms:rhmjhwhh|hh~}r(h]h]h]h]h]uhK hhh]rhX\This document covers the general use of Linux Core Release of U-Boot on following platforms:rr}r(hljhmjubaubh)r}r(hlX**32-bit platforms**rhmjhwhh|hh~}r(h]h]h]h]h]uhK hhh]rcdocutils.nodes strong r)r }r!(hljh~}r"(h]h]h]h]h]uhmjh]r#hX32-bit platformsr$r%}r&(hlUhmj ubah|Ustrongr'ubaubj>)r(}r)(hlUhmjhwNh|j[h~}r*(h]h]h]h]h]uhNhhh]r+j#)r,}r-(hlUh~}r.(j(X-h]h]h]h]h]uhmj(h]r/(j )r0}r1(hlX6`AM335x GP EVM `__r2h~}r3(h]h]h]h]h]uhmj,h]r4h)r5}r6(hlj2hmj0hwhh|hh~}r7(h]h]h]h]h]uhKh]r8h)r9}r:(hlj2h~}r;(UnameX AM335x GP EVMhX"http://www.ti.com/tool/tmdxevm3358h]h]h]h]h]uhmj5h]r<hX AM335x GP EVMr=r>}r?(hlUhmj9ubah|hubaubah|jubj )r@}rA(hlX5`AM335x EVM-SK `__rBh~}rC(h]h]h]h]h]uhmj,h]rDh)rE}rF(hljBhmj@hwhh|hh~}rG(h]h]h]h]h]uhKh]rHh)rI}rJ(hljBh~}rK(UnameX AM335x EVM-SKhX!http://www.ti.com/tool/tmdssk3358h]h]h]h]h]uhmjEh]rLhX AM335x EVM-SKrMrN}rO(hlUhmjIubah|hubaubah|jubj )rP}rQ(hlX3`AM335x ICE `__rRh~}rS(h]h]h]h]h]uhmj,h]rTh)rU}rV(hljRhmjPhwhh|hh~}rW(h]h]h]h]h]uhKh]rXh)rY}rZ(hljRh~}r[(UnameX AM335x ICEhX"http://www.ti.com/tool/tmdsice3359h]h]h]h]h]uhmjUh]r\hX AM335x ICEr]r^}r_(hlUhmjYubah|hubaubah|jubj )r`}ra(hlX2`BeagleBone White `__rbh~}rc(h]h]h]h]h]uhmj,h]rdh)re}rf(hljbhmj`hwhh|hh~}rg(h]h]h]h]h]uhKh]rhh)ri}rj(hljbh~}rk(UnameXBeagleBone WhitehXhttp://beagleboard.org/boneh]h]h]h]h]uhmjeh]rlhXBeagleBone Whitermrn}ro(hlUhmjiubah|hubaubah|jubj )rp}rq(hlX4`BeagleBone Black `__rrh~}rs(h]h]h]h]h]uhmj,h]rth)ru}rv(hljrhmjphwhh|hh~}rw(h]h]h]h]h]uhKh]rxh)ry}rz(hljrh~}r{(UnameXBeagleBone BlackhXhttps://beagleboard.org/blackh]h]h]h]h]uhmjuh]r|hXBeagleBone Blackr}r~}r(hlUhmjyubah|hubaubah|jubj )r}r(hlX2`DRA76x EVM `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX DRA76x EVMhX!http://www.ti.com/tool/J6PEVM577Ph]h]h]h]h]uhmjh]rhX DRA76x EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX1`DRA74x EVM `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX DRA74x EVMhX http://www.ti.com/tool/j6evm5777h]h]h]h]h]uhmjh]rhX DRA74x EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX1`DRA72x EVM `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX DRA72x EVMhX http://www.ti.com/tool/dra72xevmh]h]h]h]h]uhmjh]rhX DRA72x EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX1`DRA71x EVM `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX DRA71x EVMhX http://www.ti.com/product/DRA718h]h]h]h]h]uhmjh]rhX DRA71x EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX6`AM437x GP EVM `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX AM437x GP EVMhX"http://www.ti.com/tool/tmdsevm437xh]h]h]h]h]uhmjh]rhX AM437x GP EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlXAM43xx ePOS EVMrh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rhXAM43xx ePOS EVMrr}r(hljhmjubaubah|jubj )r}r(hlX5`AM437x EVM-SK `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX AM437x EVM-SKhX!http://www.ti.com/tool/tmdxsk437xh]h]h]h]h]uhmjh]rhX AM437x EVM-SKrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX3`AM437x IDK `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX AM437x IDKhX"http://www.ti.com/tool/TMDSIDK437Xh]h]h]h]h]uhmjh]rhX AM437x IDKrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX2`AM574x IDK `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX AM574x IDKhX!http://www.ti.com/tool/TMDSIDK574h]h]h]h]h]uhmjh]rhX AM574x IDKr r }r (hlUhmjubah|hubaubah|jubj )r }r (hlX6`AM572x GP EVM `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmj hwhh|hh~}r(h]h]h]h]h]uhKh]rh)r}r(hljh~}r(UnameX AM572x GP EVMhX"http://www.ti.com/tool/tmdsevm572xh]h]h]h]h]uhmjh]rhX AM572x GP EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX3`AM572x IDK `__rh~}r(h]h]h]h]h]uhmj,h]r h)r!}r"(hljhmjhwhh|hh~}r#(h]h]h]h]h]uhKh]r$h)r%}r&(hljh~}r'(UnameX AM572x IDKhX"http://www.ti.com/tool/TMDXIDK5728h]h]h]h]h]uhmj!h]r(hX AM572x IDKr)r*}r+(hlUhmj%ubah|hubaubah|jubj )r,}r-(hlX3`AM571x IDK `__r.h~}r/(h]h]h]h]h]uhmj,h]r0h)r1}r2(hlj.hmj,hwhh|hh~}r3(h]h]h]h]h]uhKh]r4h)r5}r6(hlj.h~}r7(UnameX AM571x IDKhX"http://www.ti.com/tool/tmdxidk5718h]h]h]h]h]uhmj1h]r8hX AM571x IDKr9r:}r;(hlUhmj5ubah|hubaubah|jubj )r<}r=(hlX.`66AK2H EVM `__r>h~}r?(h]h]h]h]h]uhmj,h]r@h)rA}rB(hlj>hmj<hwhh|hh~}rC(h]h]h]h]h]uhKh]rDh)rE}rF(hlj>h~}rG(UnameX 66AK2H EVMhXhttp://www.ti.com/tool/EVMK2Hh]h]h]h]h]uhmjAh]rHhX 66AK2H EVMrIrJ}rK(hlUhmjEubah|hubaubah|jubj )rL}rM(hlXK2K EVMrNh~}rO(h]h]h]h]h]uhmj,h]rPh)rQ}rR(hljNhmjLhwhh|hh~}rS(h]h]h]h]h]uhK h]rThXK2K EVMrUrV}rW(hljNhmjQubaubah|jubj )rX}rY(hlX.`K2Ex EVM `__rZh~}r[(h]h]h]h]h]uhmj,h]r\h)r]}r^(hljZhmjXhwhh|hh~}r_(h]h]h]h]h]uhK!h]r`h)ra}rb(hljZh~}rc(UnameXK2Ex EVMhXhttp://www.ti.com/tool/xevmk2exh]h]h]h]h]uhmj]h]rdhXK2Ex EVMrerf}rg(hlUhmjaubah|hubaubah|jubj )rh}ri(hlX-`K2L EVM `__rjh~}rk(h]h]h]h]h]uhmj,h]rlh)rm}rn(hljjhmjhhwhh|hh~}ro(h]h]h]h]h]uhK"h]rph)rq}rr(hljjh~}rs(UnameXK2L EVMhXhttp://www.ti.com/tool/xevmk2lxh]h]h]h]h]uhmjmh]rthXK2L EVMrurv}rw(hlUhmjqubah|hubaubah|jubj )rx}ry(hlX.`K2G GP EVM `__rzh~}r{(h]h]h]h]h]uhmj,h]r|h)r}}r~(hljzhmjxhwhh|hh~}r(h]h]h]h]h]uhK#h]rh)r}r(hljzh~}r(UnameX K2G GP EVMhXhttp://www.ti.com/tool/evmk2gh]h]h]h]h]uhmj}h]rhX K2G GP EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX/`K2G ICE EVM `__rh~}r(h]h]h]h]h]uhmj,h]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhK$h]rh)r}r(hljh~}r(UnameX K2G ICE EVMhXhttp://www.ti.com/tool/k2giceh]h]h]h]h]uhmjh]rhX K2G ICE EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX9`OMAP-L138 LCDK `__ h~}r(h]h]h]h]h]uhmj,h]rh)r}r(hlX8`OMAP-L138 LCDK `__rhmjhwhh|hh~}r(h]h]h]h]h]uhK%h]rh)r}r(hljh~}r(UnameXOMAP-L138 LCDKhX#http://www.ti.com/product/omap-l138h]h]h]h]h]uhmjh]rhXOMAP-L138 LCDKrr}r(hlUhmjubah|hubaubah|jubeh|j&ubaubh)r}r(hlX**64-bit platforms**rhmjhwhh|hh~}r(h]h]h]h]h]uhK'hhh]rj)r}r(hljh~}r(h]h]h]h]h]uhmjh]rhX64-bit platformsrr}r(hlUhmjubah|j'ubaubj>)r}r(hlUhmjhwNh|j[h~}r(h]h]h]h]h]uhNhhh]rj#)r}r(hlUh~}r(j(X-h]h]h]h]h]uhmjh]r(j )r}r(hlX3`AM65x EVM `__rh~}r(h]h]h]h]h]uhmjh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhK)h]rh)r}r(hljh~}r(UnameX AM65x EVMhX#http://www.ti.com/tool/TMDX654GPEVMh]h]h]h]h]uhmjh]rhX AM65x EVMrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX4`AM65x IDK `__rh~}r(h]h]h]h]h]uhmjh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhK*h]rh)r}r(hljh~}r(UnameX AM65x IDKhX$http://www.ti.com/tool/TMDX654IDKEVMh]h]h]h]h]uhmjh]rhX AM65x IDKrr}r(hlUhmjubah|hubaubah|jubj )r}r(hlX J721E EVM h~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX J721E EVMrhmjhwhh|hh~}r(h]h]h]h]h]uhK+h]rhX J721E EVMrr}r(hljhmjubaubah|jubeh|j&ubaubeubhqhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUusb-device-firmware-upgrade-dfurah]rhHauhM9hhh]r(h)r}r(hlX!USB Device Firmware Upgrade (DFU)rhmjhwhh|hh~}r(h]h]h]h]h]uhM9hhh]rhX!USB Device Firmware Upgrade (DFU)rr}r(hljhmjubaubh)r}r(hlXWhen working with USB Device Firmware Upgrade (DFU), regardless of the medium to be written to and of the board being used, there are some general things to keep in mind. First of all, you will need to get a copy of the **dfu-util** program installed on your host. If your distribution does not provide this package you will need to build it from source. Second, the examples that follow assume a single board is plugged into the host PC. If you have more than one device plugged in you will need to use the options that **dfu-util** provides for specifying a single device to work with. Finally, to program via DFU for a given storage device see the section for the storage device you are working with.hmjhwhh|hh~}r(h]h]h]h]h]uhM;hhh]r(hXWhen working with USB Device Firmware Upgrade (DFU), regardless of the medium to be written to and of the board being used, there are some general things to keep in mind. First of all, you will need to get a copy of the rr}r(hlXWhen working with USB Device Firmware Upgrade (DFU), regardless of the medium to be written to and of the board being used, there are some general things to keep in mind. First of all, you will need to get a copy of the hmjubj)r}r(hlX **dfu-util**h~}r(h]h]h]h]h]uhmjh]rhXdfu-utilrr}r(hlUhmjubah|j'ubhX! program installed on your host. If your distribution does not provide this package you will need to build it from source. Second, the examples that follow assume a single board is plugged into the host PC. If you have more than one device plugged in you will need to use the options that rr}r(hlX! program installed on your host. If your distribution does not provide this package you will need to build it from source. Second, the examples that follow assume a single board is plugged into the host PC. If you have more than one device plugged in you will need to use the options that hmjubj)r}r (hlX **dfu-util**h~}r (h]h]h]h]h]uhmjh]r hXdfu-utilr r }r(hlUhmjubah|j'ubhX provides for specifying a single device to work with. Finally, to program via DFU for a given storage device see the section for the storage device you are working with.rr}r(hlX provides for specifying a single device to work with. Finally, to program via DFU for a given storage device see the section for the storage device you are working with.hmjubeubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rU(usb-peripheral-boot-mode-spl-dfu-supportrah]rh^auhMHhhh]r(h)r}r(hlX*USB Peripheral boot mode (SPL-DFU support)rhmjhwhh|hh~}r(h]h]h]h]h]uhMHhhh]rhX*USB Peripheral boot mode (SPL-DFU support)rr}r (hljhmjubaubh)r!}r"(hlXThe USB Peripheral boot mode is used to boot using USB interface using SPL-DFU feature. Steps outlined here can be used on platform that support USB Peripheral boot mode.r#hmjhwhh|hh~}r$(h]h]h]h]h]uhMIhhh]r%hXThe USB Peripheral boot mode is used to boot using USB interface using SPL-DFU feature. Steps outlined here can be used on platform that support USB Peripheral boot mode.r&r'}r((hlj#hmj!ubaubj)r)}r*(hlUhmjhwhh|jh~}r+(jU.h]h]h]j Uh]h]j j uhMMhhh]r,(j )r-}r.(hlXCEnable the SPL-DFU feature in u-boot and build MLO/u-boot binaries.r/hmj)hwhh|jh~}r0(h]h]h]h]h]uhNhhh]r1h)r2}r3(hlj/hmj-hwhh|hh~}r4(h]h]h]h]h]uhMMh]r5hXCEnable the SPL-DFU feature in u-boot and build MLO/u-boot binaries.r6r7}r8(hlj/hmj2ubaubaubj )r9}r:(hlX<Load the MLO and u-boot.img using the dfu-util from host PC.r;hmj)hwhh|jh~}r<(h]h]h]h]h]uhNhhh]r=h)r>}r?(hlj;hmj9hwhh|hh~}r@(h]h]h]h]h]uhMNh]rAhX<Load the MLO and u-boot.img using the dfu-util from host PC.rBrC}rD(hlj;hmj>ubaubaubj )rE}rF(hlXOnce the u-boot is up, use DFU command from u-boot to flash the binary images from Host PC (using dfu-utils tool) to the eMMC, or QSPI to fresh/factory boards. hmj)hwhh|jh~}rG(h]h]h]h]h]uhNhhh]rHh)rI}rJ(hlXOnce the u-boot is up, use DFU command from u-boot to flash the binary images from Host PC (using dfu-utils tool) to the eMMC, or QSPI to fresh/factory boards.rKhmjEhwhh|hh~}rL(h]h]h]h]h]uhMOh]rMhXOnce the u-boot is up, use DFU command from u-boot to flash the binary images from Host PC (using dfu-utils tool) to the eMMC, or QSPI to fresh/factory boards.rNrO}rP(hljKhmjIubaubaubeubj#)rQ}rR(hlUhmjhwhh|j&h~}rS(j(X-h]h]h]h]h]uhMShhh]rT(j )rU}rV(hlX.Example provided here is for dra7xx platform. hmjQhwhh|jh~}rW(h]h]h]h]h]uhNhhh]rXh)rY}rZ(hlX-Example provided here is for dra7xx platform.r[hmjUhwhh|hh~}r\(h]h]h]h]h]uhMSh]r]hX-Example provided here is for dra7xx platform.r^r_}r`(hlj[hmjYubaubaubj )ra}rb(hlXNUse default "dra7xx\_evm\_defconfig" to build spl/u-boot-spl.bin, u-boot.img. hmjQhwhh|jh~}rc(h]h]h]h]h]uhNhhh]rdh)re}rf(hlXMUse default "dra7xx\_evm\_defconfig" to build spl/u-boot-spl.bin, u-boot.img.hmjahwhh|hh~}rg(h]h]h]h]h]uhMUh]rhhXKUse default "dra7xx_evm_defconfig" to build spl/u-boot-spl.bin, u-boot.img.rirj}rk(hlXMUse default "dra7xx\_evm\_defconfig" to build spl/u-boot-spl.bin, u-boot.img.hmjeubaubaubeubjr)rl}rm(hlX7host$ make dra7xx_evm_defconfig host$ make menuconfig select SPL/DFU support menuconfig->SPL/TPL---> .. [*] Support booting from RAM [*] Support USB Gadget drivers [ ] Support USB Ethernet drivers [*] Support DFU (Device Firmware Upgrade) DFU device selection (RAM device) -->hmjhwhh|juh~}rn(hhh]h]h]h]h]uhMehhh]rohX7host$ make dra7xx_evm_defconfig host$ make menuconfig select SPL/DFU support menuconfig->SPL/TPL---> .. [*] Support booting from RAM [*] Support USB Gadget drivers [ ] Support USB Ethernet drivers [*] Support DFU (Device Firmware Upgrade) DFU device selection (RAM device) -->rprq}rr(hlUhmjlubaubjr)rs}rt(hlXwUnselect CONFIG_HUSH_PARSER menuconfig--->Command Line interface [*] Support U-boot commands [ ] Use hush shellhmjhwhh|juh~}ru(hhh]h]h]h]h]uhMshhh]rvhXwUnselect CONFIG_HUSH_PARSER menuconfig--->Command Line interface [*] Support U-boot commands [ ] Use hush shellrwrx}ry(hlUhmjsubaubj#)rz}r{(hlUhmjhwhh|j&h~}r|(j(X-h]h]h]h]h]uhMnhhh]r}j )r~}r(hlX(Build spl/u-boot-spl.bin and u-boot.img hmjzhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlX'Build spl/u-boot-spl.bin and u-boot.imgrhmj~hwhh|hh~}r(h]h]h]h]h]uhMnh]rhX'Build spl/u-boot-spl.bin and u-boot.imgrr}r(hljhmjubaubaubaubjr)r}r(hlX host$ makehmjhwhh|juh~}r(hhh]h]h]h]h]uhM}hhh]rhX host$ makerr}r(hlUhmjubaubh)r}r(hlUhmjhwhh|hh~}r(hX(CONFIG_part_family in ('General_family')h]h]h]h]h]uhMthhh]r(j#)r}r(hlUhmjhwhh|j&h~}r(j(X-h]h]h]h]h]uhMvhhh]rj )r}r(hlX3Set SYSBOOT SW2 switch to USB Peripheral boot mode hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlX2Set SYSBOOT SW2 switch to USB Peripheral boot moderhmjhwhh|hh~}r(h]h]h]h]h]uhMvh]rhX2Set SYSBOOT SW2 switch to USB Peripheral boot moderr}r(hljhmjubaubaubaubjr)r}r(hlX=SW2[7..0] = 00010000 (refer to TRM for various booting order)hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX=SW2[7..0] = 00010000 (refer to TRM for various booting order)rr}r(hlUhmjubaubj#)r}r(hlUhmjhwhh|j&h~}r(j(X-h]h]h]h]h]uhM|hhh]r(j )r}r(hlXIConnect EVM Superspeed port (USB1 port) to PC (Ubuntu) through USB cable.hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXIConnect EVM Superspeed port (USB1 port) to PC (Ubuntu) through USB cable.rhmjhwhh|hh~}r(h]h]h]h]h]uhM|h]rhXIConnect EVM Superspeed port (USB1 port) to PC (Ubuntu) through USB cable.rr}r(hljhmjubaubaubj )r}r(hlXFrom Ubuntu (or the host) PC, fetch and build usbboot application. usbboot pre-built binaries for particular distributions may be available in `Processor SDK `__ already. Here are the steps to build usbboot application. hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXFrom Ubuntu (or the host) PC, fetch and build usbboot application. usbboot pre-built binaries for particular distributions may be available in `Processor SDK `__ already. Here are the steps to build usbboot application.hmjhwhh|hh~}r(h]h]h]h]h]uhM~h]r(hXFrom Ubuntu (or the host) PC, fetch and build usbboot application. usbboot pre-built binaries for particular distributions may be available in rr}r(hlXFrom Ubuntu (or the host) PC, fetch and build usbboot application. usbboot pre-built binaries for particular distributions may be available in hmjubh)r}r(hlX`Processor SDK `__h~}r(UnameX Processor SDKhX index.htmlh]h]h]h]h]uhmjh]rhX Processor SDKrr}r(hlUhmjubah|hubhX: already. Here are the steps to build usbboot application.rr}r(hlX: already. Here are the steps to build usbboot application.hmjubeubaubeubjr)r}r(hlXhost$ git clone git://git.omapzoom.org/repo/omapboot.git host$ cd omapboot host$ checkout 609ac271d9f89b51c133fd829dc77e8af4e7b67e host$ make -C host/toolshmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXhost$ git clone git://git.omapzoom.org/repo/omapboot.git host$ cd omapboot host$ checkout 609ac271d9f89b51c133fd829dc77e8af4e7b67e host$ make -C host/toolsrr}r(hlUhmjubaubh)r}r(hlX=This results in host side tool called ``usbboot-stand-alone``hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hX&This results in host side tool called rr}r(hlX&This results in host side tool called hmjubcdocutils.nodes literal r)r}r(hlX``usbboot-stand-alone``h~}r(h]h]h]h]h]uhmjh]rhXusbboot-stand-alonerr}r(hlUhmjubah|Uliteralrubeubh)r}r(hlXSFor loading spl/u-boot-spl.bin to EVM, issue the command below and reset the board.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXSFor loading spl/u-boot-spl.bin to EVM, issue the command below and reset the board.rr}r(hljhmjubaubjr)r}r(hlX4host$ sudo usbboot-stand-alone -S spl/u-boot-spl.binhmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX4host$ sudo usbboot-stand-alone -S spl/u-boot-spl.binrr}r(hlUhmjubaubj#)r}r(hlUhmjhwhh|j&h~}r(j(X-h]h]h]h]h]uhMhhh]rj )r}r(hlXLoad the u-boot.img to RAM. hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXLoad the u-boot.img to RAM.rhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXLoad the u-boot.img to RAM.rr}r(hljhmjubaubaubaubjr)r}r(hlXhost$ sudo dfu-util -lhmjhwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hXhost$ sudo dfu-util -lr r }r (hlUhmjubaubjr)r}r(hlXFound DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=0, name="kernel" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=1, name="fdt" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=2, name="ramdisk"hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXFound DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=0, name="kernel" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=1, name="fdt" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=2, name="ramdisk"rr}r(hlUhmjubaubjr)r}r(hlX4host$ sudo dfu-util c 1 -i 0 -a 0 -D "u-boot.img" -Rhmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX4host$ sudo dfu-util c 1 -i 0 -a 0 -D "u-boot.img" -Rrr}r(hlUhmjubaubj#)r}r(hlUhmjhwhh|j&h~}r(j(X-h]h]h]h]h]uhMhhh]rj )r }r!(hlX#Now EVM will boot to u-boot prompt.r"hmjhwhh|jh~}r#(h]h]h]h]h]uhNhhh]r$h)r%}r&(hlj"hmj hwhh|hh~}r'(h]h]h]h]h]uhMh]r(hX#Now EVM will boot to u-boot prompt.r)r*}r+(hlj"hmj%ubaubaubaubeubh)r,}r-(hlUhmjhwhh|hh~}r.(hX#CONFIG_part_family in ('J7_family')h]h]h]h]h]uhMhhh]r/(jC)r0}r1(hlX9USB Peripheral boot mode on J721E EVM (SPL-DFU boot mode)r2hmj,hwhh|jGh~}r3(h]r4U dfu-j721er5ah]h]h]h]r6h[auhNhhh]r7hX9USB Peripheral boot mode on J721E EVM (SPL-DFU boot mode)r8r9}r:(hlj2hmj0ubaubj#)r;}r<(hlUhmj,hwhh|j&h~}r=(j(X-h]h]h]h]h]uhMhhh]r>(j )r?}r@(hlX{Set SYSBOOT switches to USB Peripheral boot mode (Refer to **Initialization** chapter of J721E TRM for boot switch details)rAhmj;hwhh|jh~}rB(h]h]h]h]h]uhNhhh]rCh)rD}rE(hljAhmj?hwhh|hh~}rF(h]h]h]h]h]uhMh]rG(hX;Set SYSBOOT switches to USB Peripheral boot mode (Refer to rHrI}rJ(hlX;Set SYSBOOT switches to USB Peripheral boot mode (Refer to hmjDubj)rK}rL(hlX**Initialization**h~}rM(h]h]h]h]h]uhmjDh]rNhXInitializationrOrP}rQ(hlUhmjKubah|j'ubhX. chapter of J721E TRM for boot switch details)rRrS}rT(hlX. chapter of J721E TRM for boot switch details)hmjDubeubaubj )rU}rV(hlX8Make sure USB0 port in UFP/DRP mode: SW3[3:4] = 01 or 1xrWhmj;hwhh|jh~}rX(h]h]h]h]h]uhNhhh]rYh)rZ}r[(hljWhmjUhwhh|hh~}r\(h]h]h]h]h]uhMh]r]hX8Make sure USB0 port in UFP/DRP mode: SW3[3:4] = 01 or 1xr^r_}r`(hljWhmjZubaubaubj )ra}rb(hlX<Connect EVM's TypeC port (USB0 port) to PC through USB cablerchmj;hwhh|jh~}rd(h]h]h]h]h]uhNhhh]reh)rf}rg(hljchmjahwhh|hh~}rh(h]h]h]h]h]uhMh]rihX<Connect EVM's TypeC port (USB0 port) to PC through USB cablerjrk}rl(hljchmjfubaubaubj )rm}rn(hlXPower on the board hmj;hwhh|jh~}ro(h]h]h]h]h]uhNhhh]rph)rq}rr(hlXPower on the boardrshmjmhwhh|hh~}rt(h]h]h]h]h]uhMh]ruhXPower on the boardrvrw}rx(hljshmjqubaubaubeubh)ry}rz(hlX On host side:r{hmj,hwhh|hh~}r|(h]h]h]h]h]uhMhhh]r}hX On host side:r~r}r(hlj{hmjyubaubjr)r}r(hlXhost$ sudo dfu-util -lhmj,hwhh|juh~}r(jwjxXtexthhh]h]h]jy}h]h]uhMhhh]rhXhost$ sudo dfu-util -lrr}r(hlUhmjubaubh)r}r(hlX*This will show the following DFU entities:rhmj,hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX*This will show the following DFU entities:rr}r(hljhmjubaubjr)r}r(hlXFound DFU: [0451:6163] ver=0200, devnum=50, cfg=1, intf=0, path="3-2", alt=1, name="SocId", serial="01.00.00.00" Found DFU: [0451:6163] ver=0200, devnum=50, cfg=1, intf=0, path="3-2", alt=0, name="bootloader", serial="01.00.00.00"hmj,hwhh|juh~}r(jwjxXtexthhh]h]h]jy}h]h]uhMhhh]rhXFound DFU: [0451:6163] ver=0200, devnum=50, cfg=1, intf=0, path="3-2", alt=1, name="SocId", serial="01.00.00.00" Found DFU: [0451:6163] ver=0200, devnum=50, cfg=1, intf=0, path="3-2", alt=0, name="bootloader", serial="01.00.00.00"rr}r(hlUhmjubaubh)r}r(hlXTSend boot images in this order: tiboot3.bin -> sysfw.itb -> tispl.bin -> u-boot.img.rhmj,hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXTSend boot images in this order: tiboot3.bin -> sysfw.itb -> tispl.bin -> u-boot.img.rr}r(hljhmjubaubjr)r}r(hlXPhost$ sudo dfu-util -R -a bootloader -D tiboot3.bin host$ sudo dfu-util -l Found DFU: [0451:6163] ver=0224, devnum=51, cfg=1, intf=0, path="3-2", alt=0, name="sysfw.itb", serial="UNKNOWN" host$ sudo dfu-util -R -a sysfw.itb -D sysfw.itb host$ sudo dfu-util -l Found DFU: [0451:6163] ver=0224, devnum=52, cfg=1, intf=0, path="3-2", alt=1, name="u-boot.img", serial="UNKNOWN" Found DFU: [0451:6163] ver=0224, devnum=52, cfg=1, intf=0, path="3-2", alt=0, name="tispl.bin", serial="UNKNOWN" host$ sudo dfu-util -R -a tispl.bin -D tispl.bin host$ sudo dfu-util -R -a u-boot.img -D u-boot.imghmj,hwhh|juh~}r(jwjxXtexthhh]h]h]jy}h]h]uhMhhh]rhXPhost$ sudo dfu-util -R -a bootloader -D tiboot3.bin host$ sudo dfu-util -l Found DFU: [0451:6163] ver=0224, devnum=51, cfg=1, intf=0, path="3-2", alt=0, name="sysfw.itb", serial="UNKNOWN" host$ sudo dfu-util -R -a sysfw.itb -D sysfw.itb host$ sudo dfu-util -l Found DFU: [0451:6163] ver=0224, devnum=52, cfg=1, intf=0, path="3-2", alt=1, name="u-boot.img", serial="UNKNOWN" Found DFU: [0451:6163] ver=0224, devnum=52, cfg=1, intf=0, path="3-2", alt=0, name="tispl.bin", serial="UNKNOWN" host$ sudo dfu-util -R -a tispl.bin -D tispl.bin host$ sudo dfu-util -R -a u-boot.img -D u-boot.imgrr}r(hlUhmjubaubh)r}r(hlX:At this point, the board should boot to the U-Boot prompt.rhmj,hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX:At this point, the board should boot to the U-Boot prompt.rr}r(hljhmjubaubcdocutils.nodes note r)r}r(hlX>This mode is not supported on J721E Rev E2 and earlier boards.rhmj,hwhh|Unoterh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX>This mode is not supported on J721E Rev E2 and earlier boards.rr}r(hljhmjubaubaubeubeubeubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUnetwork-wired-or-usb-clientrah]rhSauhMhhh]r(h)r}r(hlXNetwork (Wired or USB Client)rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXNetwork (Wired or USB Client)rr}r(hljhmjubaubh)r}r(hlXThis section documents how to configure the network and use it to load files and then boot the Linux Kernel using a root filesystem mounted over NFS. At this time, no special builds of U-Boot are required to perform these operations on the supported hardware.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXThis section documents how to configure the network and use it to load files and then boot the Linux Kernel using a root filesystem mounted over NFS. At this time, no special builds of U-Boot are required to perform these operations on the supported hardware.rr}r(hljhmjubaubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rUbooting-u-boot-from-the-networkrah]rhauhMhhh]r(h)r}r(hlXBooting U-Boot from the networkrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXBooting U-Boot from the networkrr}r(hljhmjubaubh)r}r(hlXIn some cases we support loading SPL and U-Boot over the network because of ROM support. In some cases, a special build of U-Boot may be required. In addition, the DHCP server is needed to reply to the target with the file to fetch via tftp. In order to facilitate this, the **vendor-class-identifier** DHCP field is filled out by the ROM and the values are listed in the table below. Finally, you will need to use the **spl/u-boot-spl.bin** and **u-boot.img** files to boot.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXIn some cases we support loading SPL and U-Boot over the network because of ROM support. In some cases, a special build of U-Boot may be required. In addition, the DHCP server is needed to reply to the target with the file to fetch via tftp. In order to facilitate this, the rr}r(hlXIn some cases we support loading SPL and U-Boot over the network because of ROM support. In some cases, a special build of U-Boot may be required. In addition, the DHCP server is needed to reply to the target with the file to fetch via tftp. In order to facilitate this, the hmjubj)r}r(hlX**vendor-class-identifier**h~}r(h]h]h]h]h]uhmjh]rhXvendor-class-identifierrr}r(hlUhmjubah|j'ubhXu DHCP field is filled out by the ROM and the values are listed in the table below. Finally, you will need to use the rr}r(hlXu DHCP field is filled out by the ROM and the values are listed in the table below. Finally, you will need to use the hmjubj)r}r(hlX**spl/u-boot-spl.bin**h~}r(h]h]h]h]h]uhmjh]rhXspl/u-boot-spl.binrr}r(hlUhmjubah|j'ubhX and rr}r(hlX and hmjubj)r}r(hlX**u-boot.img**h~}r(h]h]h]h]h]uhmjh]rhX u-boot.imgrr}r(hlUhmjubah|j'ubhX files to boot.rr}r(hlX files to boot.hmjubeubj)r}r(hlXMBooting U-Boot/SPL from network is supported only on the following platforms.r hmjhwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXMBooting U-Boot/SPL from network is supported only on the following platforms.rr}r(hlj hmj ubaubaubcdocutils.nodes table r)r}r(hlUhmjhwhh|Utablerh~}r(h]h]h]h]h]uhNhhh]rcdocutils.nodes tgroup r)r}r(hlUh~}r(h]h]h]h]h]UcolsKuhmjh]r(cdocutils.nodes colspec r)r}r (hlUh~}r!(h]h]h]h]h]UcolwidthK#uhmjh]h|Ucolspecr"ubj)r#}r$(hlUh~}r%(h]h]h]h]h]UcolwidthKuhmjh]h|j"ubj)r&}r'(hlUh~}r((h]h]h]h]h]UcolwidthK&uhmjh]h|j"ubj)r)}r*(hlUh~}r+(h]h]h]h]h]UcolwidthK6uhmjh]h|j"ubj)r,}r-(hlUh~}r.(h]h]h]h]h]UcolwidthK%uhmjh]h|j"ubcdocutils.nodes thead r/)r0}r1(hlUh~}r2(h]h]h]h]h]uhmjh]r3cdocutils.nodes row r4)r5}r6(hlUh~}r7(h]h]h]h]h]uhmj0h]r8(cdocutils.nodes entry r9)r:}r;(hlUh~}r<(h]h]h]h]h]uhmj5h]r=h)r>}r?(hlXBoardr@hmj:hwhh|hh~}rA(h]h]h]h]h]uhMh]rBhXBoardrCrD}rE(hlj@hmj>ubaubah|UentryrFubj9)rG}rH(hlUh~}rI(h]h]h]h]h]uhmj5h]rJh)rK}rL(hlX make targetrMhmjGhwhh|hh~}rN(h]h]h]h]h]uhMh]rOhX make targetrPrQ}rR(hljMhmjKubaubah|jFubj9)rS}rT(hlUh~}rU(h]h]h]h]h]uhmj5h]rVh)rW}rX(hlXSupported interfacesrYhmjShwhh|hh~}rZ(h]h]h]h]h]uhMh]r[hXSupported interfacesr\r]}r^(hljYhmjWubaubah|jFubj9)r_}r`(hlUh~}ra(h]h]h]h]h]uhmj5h]rbh)rc}rd(hlX!ROM vendor-class-identifier valuerehmj_hwhh|hh~}rf(h]h]h]h]h]uhMh]rghX!ROM vendor-class-identifier valuerhri}rj(hljehmjcubaubah|jFubj9)rk}rl(hlUh~}rm(h]h]h]h]h]uhmj5h]rnh)ro}rp(hlX!SPL vendor-class-identifier valuerqhmjkhwhh|hh~}rr(h]h]h]h]h]uhMh]rshX!SPL vendor-class-identifier valuertru}rv(hljqhmjoubaubah|jFubeh|Urowrwubah|Utheadrxubcdocutils.nodes tbody ry)rz}r{(hlUh~}r|(h]h]h]h]h]uhmjh]r}(j4)r~}r(hlUh~}r(h]h]h]h]h]uhmjzh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmj~h]rh)r}r(hlX AM335x GP EVMrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX AM335x GP EVMrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmj~h]rh)r}r(hlX am335x\_evmhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX am335x_evmrr}r(hlX am335x\_evmhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmj~h]rh)r}r(hlX CPSW ethernetrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX CPSW ethernetrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmj~h]rh)r}r(hlX2DM814x ROM (PG1.0) or AM335x ROM (PG2.0 and later)rhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX2DM814x ROM (PG1.0) or AM335x ROM (PG2.0 and later)rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmj~h]rh)r}r(hlXAM335x U-Boot SPLrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXAM335x U-Boot SPLrr}r(hljhmjubaubah|jFubeh|jwubj4)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXAM335x GP EVM (PG2.0 and later)rhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXAM335x GP EVM (PG2.0 and later)rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX am335x\_evmhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX am335x_evmrr}r(hlX am335x\_evmhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXSPL and U-Boot via USB RNDISrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXSPL and U-Boot via USB RNDISrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX AM335x ROMrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX AM335x ROMrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXAM335x U-Boot SPLrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXAM335x U-Boot SPLrr}r(hljhmjubaubah|jFubeh|jwubj4)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXAM335x GP EVM (PG1.0)rhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXAM335x GP EVM (PG1.0)r r }r (hljhmjubaubah|jFubj9)r }r (hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX am335x\_evmhmj hwhh|hh~}r(h]h]h]h]h]uhMh]rhX am335x_evmrr}r(hlX am335x\_evmhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX"SPL via UART, U-Boot via USB RNDISrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX"SPL via UART, U-Boot via USB RNDISr r!}r"(hljhmjubaubah|jFubj9)r#}r$(hlUh~}r%(h]h]h]h]h]uhmjh]r&h)r'}r((hlXN/Ar)hmj#hwhh|hh~}r*(h]h]h]h]h]uhMh]r+hXN/Ar,r-}r.(hlj)hmj'ubaubah|jFubj9)r/}r0(hlUh~}r1(h]h]h]h]h]uhmjh]r2h)r3}r4(hlXAM335x U-Boot SPLr5hmj/hwhh|hh~}r6(h]h]h]h]h]uhMh]r7hXAM335x U-Boot SPLr8r9}r:(hlj5hmj3ubaubah|jFubeh|jwubj4)r;}r<(hlUh~}r=(h]h]h]h]h]uhmjzh]r>(j9)r?}r@(hlUh~}rA(h]h]h]h]h]uhmj;h]rBh)rC}rD(hlX AM43xx EVMrEhmj?hwhh|hh~}rF(h]h]h]h]h]uhMh]rGhX AM43xx EVMrHrI}rJ(hljEhmjCubaubah|jFubj9)rK}rL(hlUh~}rM(h]h]h]h]h]uhmj;h]rNh)rO}rP(hlX am43xx\_evmhmjKhwhh|hh~}rQ(h]h]h]h]h]uhMh]rRhX am43xx_evmrSrT}rU(hlX am43xx\_evmhmjOubaubah|jFubj9)rV}rW(hlUh~}rX(h]h]h]h]h]uhmj;h]rYh)rZ}r[(hlX CPSW ethernetr\hmjVhwhh|hh~}r](h]h]h]h]h]uhMh]r^hX CPSW ethernetr_r`}ra(hlj\hmjZubaubah|jFubj9)rb}rc(hlUh~}rd(h]h]h]h]h]uhmj;h]reh)rf}rg(hlX AM43xx ROMrhhmjbhwhh|hh~}ri(h]h]h]h]h]uhMh]rjhX AM43xx ROMrkrl}rm(hljhhmjfubaubah|jFubj9)rn}ro(hlUh~}rp(h]h]h]h]h]uhmj;h]rqh)rr}rs(hlXAM43xx U-Boot SPLrthmjnhwhh|hh~}ru(h]h]h]h]h]uhMh]rvhXAM43xx U-Boot SPLrwrx}ry(hljthmjrubaubah|jFubeh|jwubj4)rz}r{(hlUh~}r|(h]h]h]h]h]uhmjzh]r}(j9)r~}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlXAM43xx EVM (PG1.2 and later)rhmj~hwhh|hh~}r(h]h]h]h]h]uhMh]rhXAM43xx EVM (PG1.2 and later)rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlX am43xx\_evmhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX am43xx_evmrr}r(hlX am43xx\_evmhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlXSPL and U-Boot via USB RNDISrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXSPL and U-Boot via USB RNDISrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlX AM43xx ROMrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX AM43xx ROMrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlXAM43xx U-Boot SPLrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXAM43xx U-Boot SPLrr}r(hljhmjubaubah|jFubeh|jwubeh|Utbodyrubeh|Utgrouprubaubh)r}r(hlX>If using ISC dhcpd an example host entry would look like this:rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX>If using ISC dhcpd an example host entry would look like this:rr}r(hljhmjubaubjr)r}r(hlXhost am335x_evm { hardware ethernet de:ad:be:ee:ee:ef; # Check for PG1.0, typically CPSW if substring (option vendor-class-identifier, 0, 10) = "DM814x ROM" { filename "u-boot-spl.bin"; # Check for PG2.0, CPSW or USB RNDIS } elsif substring (option vendor-class-identifier, 0, 10) = "AM335x ROM" { filename "u-boot-spl.bin"; } elsif substring (option vendor-class-identifier, 0, 17) = "AM335x U-Boot SPL" { filename "u-boot.img"; } else { filename "zImage-am335x-evm.bin"; } }hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXhost am335x_evm { hardware ethernet de:ad:be:ee:ee:ef; # Check for PG1.0, typically CPSW if substring (option vendor-class-identifier, 0, 10) = "DM814x ROM" { filename "u-boot-spl.bin"; # Check for PG2.0, CPSW or USB RNDIS } elsif substring (option vendor-class-identifier, 0, 10) = "AM335x ROM" { filename "u-boot-spl.bin"; } elsif substring (option vendor-class-identifier, 0, 17) = "AM335x U-Boot SPL" { filename "u-boot.img"; } else { filename "zImage-am335x-evm.bin"; } }rr}r(hlUhmjubaubh)r}r(hlXNote that in a factory type setting, the substring tests can be done inside of the subnet declaration to set the default filename value for the subnet, and overriden (if needed) in a host entry.rhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXNote that in a factory type setting, the substring tests can be done inside of the subnet declaration to set the default filename value for the subnet, and overriden (if needed) in a host entry.rr}r(hljhmjubaubh)r}r(hlXIf you have removed NetworkManager from your system (which is not the default in most distributions) you need to configure your /etc/network/interfaces file thusly:rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXIf you have removed NetworkManager from your system (which is not the default in most distributions) you need to configure your /etc/network/interfaces file thusly:rr}r(hljhmjubaubjr)r}r(hlXallow-hotplug usb0 iface usb0 inet static address 192.168.1.1 netmask 255.255.255.0 post-up service isc-dhcp-server reloadhmjhwhh|juh~}r(hhh]h]h]h]h]uhM!hhh]rhXallow-hotplug usb0 iface usb0 inet static address 192.168.1.1 netmask 255.255.255.0 post-up service isc-dhcp-server reloadrr}r(hlUhmjubaubh)r}r(hlXIf you are using NetworkManager you need to create two files. First, as root create /etc/NetworkManager/system-connections/AM335x USB RNDIS (and use \\ to escape the space) with the following content:hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXIf you are using NetworkManager you need to create two files. First, as root create /etc/NetworkManager/system-connections/AM335x USB RNDIS (and use \ to escape the space) with the following content:rr}r(hlXIf you are using NetworkManager you need to create two files. First, as root create /etc/NetworkManager/system-connections/AM335x USB RNDIS (and use \\ to escape the space) with the following content:hmjubaubjr)r}r(hlX[802-3-ethernet] duplex=full mac-address=AA:BB:CC:11:22:33 [connection] id=AM335X USB RNDIS uuid=INSERT THE CONTENTS OF 'uuidgen' HERE type=802-3-ethernet [ipv6] method=ignore [ipv4] method=manual addresses1=192.168.1.1;16;hmjhwhh|juh~}r(hhh]h]h]h]h]uhM.hhh]rhX[802-3-ethernet] duplex=full mac-address=AA:BB:CC:11:22:33 [connection] id=AM335X USB RNDIS uuid=INSERT THE CONTENTS OF 'uuidgen' HERE type=802-3-ethernet [ipv6] method=ignore [ipv4] method=manual addresses1=192.168.1.1;16;rr}r(hlUhmjubaubh)r}r(hlXoSeccond as root, and ensuring execute permissions, create /etc/NetworkManager/dispatcher.d/99am335x-dhcp-serverrhmjhwhh|hh~}r(h]h]h]h]h]uhM3hhh]rhXoSeccond as root, and ensuring execute permissions, create /etc/NetworkManager/dispatcher.d/99am335x-dhcp-serverrr}r(hljhmjubaubjr)r}r(hlXu#!/bin/sh IF=$1 STATUS=$2 if [ "$IF" = "usb0" ] && [ "$STATUS" = "up" ]; then service isc-dhcp-server reload fihmjhwhh|juh~}r(hhh]h]h]h]h]uhMChhh]rhXu#!/bin/sh IF=$1 STATUS=$2 if [ "$IF" = "usb0" ] && [ "$STATUS" = "up" ]; then service isc-dhcp-server reload firr}r(hlUhmjubaubh)r}r(hlXA walk through of these steps can be seen at `Ubuntu 12.04 Set Up to Network Boot an AM335x Based Platform `__.hmjhwhh|hh~}r (h]h]h]h]h]uhMAhhh]r (hX-A walk through of these steps can be seen at r r }r (hlX-A walk through of these steps can be seen at hmjubh)r }r (hlX`Ubuntu 12.04 Set Up to Network Boot an AM335x Based Platform `__h~}r (UnameX<Ubuntu 12.04 Set Up to Network Boot an AM335x Based PlatformhXdhttp://processors.wiki.ti.com/index.php/Ubuntu_12.04_Set_Up_to_Network_Boot_an_AM335x_Based_Platformh]h]h]h]h]uhmjh]r hX<Ubuntu 12.04 Set Up to Network Boot an AM335x Based Platformr r }r (hlUhmj ubah|hubhX.r }r (hlX.hmjubeubjC)r }r (hlUhmjhwhh|jZh~}r (h]h]h]h]h]uhMEhhh]r jH)r }r (hlUjLKhmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]ubaubeubhn)r }r (hlUhmjhwhh|h}h~}r (h]h]h]h]r Umultiple-interfacesr ah]r hauhMHhhh]r (h)r }r (hlXMultiple Interfacesr hmj hwhh|hh~}r (h]h]h]h]h]uhMHhhh]r hXMultiple Interfacesr! r" }r# (hlj hmj ubaubh)r$ }r% (hlX On some boards, for example when we have both a wired interface and USB RNDIS gadget ethernet, it can be desirable to change from the default U-Boot behavior of cycling over each interface it knows to telling U-Boot to use a single interface. For example, on start you may see lines like:r& hmj hwhh|hh~}r' (h]h]h]h]h]uhMJhhh]r( hX On some boards, for example when we have both a wired interface and USB RNDIS gadget ethernet, it can be desirable to change from the default U-Boot behavior of cycling over each interface it knows to telling U-Boot to use a single interface. For example, on start you may see lines like:r) r* }r+ (hlj& hmj$ ubaubjr)r, }r- (hlXNet: cpsw, usb_etherhmj hwhh|juh~}r. (hhh]h]h]h]h]uhM]hhh]r/ hXNet: cpsw, usb_etherr0 r1 }r2 (hlUhmj, ubaubh)r3 }r4 (hlXJSo to ensure that we use **usb\_ether** first issue the following command:hmj hwhh|hh~}r5 (h]h]h]h]h]uhMThhh]r6 (hXSo to ensure that we use r7 r8 }r9 (hlXSo to ensure that we use hmj3 ubj)r: }r; (hlX**usb\_ether**h~}r< (h]h]h]h]h]uhmj3 h]r= hX usb_etherr> r? }r@ (hlUhmj: ubah|j'ubhX# first issue the following command:rA rB }rC (hlX# first issue the following command:hmj3 ubeubjr)rD }rE (hlX U-Boot # setenv ethact usb_etherhmj hwhh|juh~}rF (hhh]h]h]h]h]uhMdhhh]rG hX U-Boot # setenv ethact usb_etherrH rI }rJ (hlUhmjD ubaubeubhn)rK }rL (hlUhmjhwhh|h}h~}rM (h]h]h]h]rN Unetwork-configuration-via-dhcprO ah]rP hauhM\hhh]rQ (h)rR }rS (hlXNetwork configuration via DHCPrT hmjK hwhh|hh~}rU (h]h]h]h]h]uhM\hhh]rV hXNetwork configuration via DHCPrW rX }rY (hljT hmjR ubaubh)rZ }r[ (hlX>To configure the network via DHCP, use the following commands:r\ hmjK hwhh|hh~}r] (h]h]h]h]h]uhM^hhh]r^ hX>To configure the network via DHCP, use the following commands:r_ r` }ra (hlj\ hmjZ ubaubjr)rb }rc (hlX)U-Boot # setenv autoload no U-Boot # dhcphmjK hwhh|juh~}rd (hhh]h]h]h]h]uhMmhhh]re hX)U-Boot # setenv autoload no U-Boot # dhcprf rg }rh (hlUhmjb ubaubh)ri }rj (hlXdAnd ensure that a DHCP server is configured to serve addresses for the network you are connected to.rk hmjK hwhh|hh~}rl (h]h]h]h]h]uhMehhh]rm hXdAnd ensure that a DHCP server is configured to serve addresses for the network you are connected to.rn ro }rp (hljk hmji ubaubeubhn)rq }rr (hlUhmjhwhh|h}h~}rs (h]h]h]h]rt Umanual-network-configurationru ah]rv hauhMihhh]rw (h)rx }ry (hlXManual network configurationrz hmjq hwhh|hh~}r{ (h]h]h]h]h]uhMihhh]r| hXManual network configurationr} r~ }r (hljz hmjx ubaubh)r }r (hlX_To configure the network manually, the **ipaddr**, **serverip**, **gatewayip** and **netmask**:hmjq hwhh|hh~}r (h]h]h]h]h]uhMkhhh]r (hX'To configure the network manually, the r r }r (hlX'To configure the network manually, the hmj ubj)r }r (hlX **ipaddr**h~}r (h]h]h]h]h]uhmj h]r hXipaddrr r }r (hlUhmj ubah|j'ubhX, r r }r (hlX, hmj ubj)r }r (hlX **serverip**h~}r (h]h]h]h]h]uhmj h]r hXserveripr r }r (hlUhmj ubah|j'ubhX, r r }r (hlX, hmj ubj)r }r (hlX **gatewayip**h~}r (h]h]h]h]h]uhmj h]r hX gatewayipr r }r (hlUhmj ubah|j'ubhX and r r }r (hlX and hmj ubj)r }r (hlX **netmask**h~}r (h]h]h]h]h]uhmj h]r hXnetmaskr r }r (hlUhmj ubah|j'ubhX:r }r (hlX:hmj ubeubjr)r }r (hlXU-Boot # setenv ipaddr 192.168.1.2 U-Boot # setenv serverip 192.168.1.1 U-Boot # setenv gatewayip 192.168.1.1 U-Boot # setenv netmask 255.255.255.0hmjq hwhh|juh~}r (hhh]h]h]h]h]uhM{hhh]r hXU-Boot # setenv ipaddr 192.168.1.2 U-Boot # setenv serverip 192.168.1.1 U-Boot # setenv gatewayip 192.168.1.1 U-Boot # setenv netmask 255.255.255.0r r }r (hlUhmj ubaubeubhn)r }r (hlUhmjhwhh|h}h~}r (h]h]h]h]r U!disabling-gigabit-phy-advertisingr ah]r h7auhMvhhh]r (h)r }r (hlX!Disabling Gigabit Phy Advertisingr hmj hwhh|hh~}r (h]h]h]h]h]uhMvhhh]r hX!Disabling Gigabit Phy Advertisingr r }r (hlj hmj ubaubh)r }r (hlXSOn some boards like DRA72x Rev B or earlier, there is an issue like ethernet doesn't connect to 1Gbps switch. This issue is due to the use of an old ti phy with history of bad behaviour, due to this several J6 EVMs have been marked 100M only. So here is the U-Boot command to disable phy's 1Gbps support and connect as 100Mbps max capable.r hmj hwhh|hh~}r (h]h]h]h]h]uhMwhhh]r hXSOn some boards like DRA72x Rev B or earlier, there is an issue like ethernet doesn't connect to 1Gbps switch. This issue is due to the use of an old ti phy with history of bad behaviour, due to this several J6 EVMs have been marked 100M only. So here is the U-Boot command to disable phy's 1Gbps support and connect as 100Mbps max capable.r r }r (hlj hmj ubaubjr)r }r (hlX=> mii modify 0x3 0x9 0x0 0x300 /* Disable Gigabit advertising */ => mii modify 0x3 0x0 0x0 0x1000 /* Disable Auto Negotiation */ => mii modify 0x3 0x0 0x1000 0x1000 /* Enable Auto Negotiation */hmj hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hX=> mii modify 0x3 0x9 0x0 0x300 /* Disable Gigabit advertising */ => mii modify 0x3 0x0 0x0 0x1000 /* Disable Auto Negotiation */ => mii modify 0x3 0x0 0x1000 0x1000 /* Enable Auto Negotiation */r r }r (hlUhmj ubaubeubhn)r }r (hlUhmjhwhh|h}h~}r (h]h]h]h]r Ubooting-linux-from-the-networkr ah]r hauhMhhh]r (h)r }r (hlXBooting Linux from the networkr hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXBooting Linux from the networkr r }r (hlj hmj ubaubh)r }r (hlXWithin the default environment for each board that supports networking there is a boot command called **netboot** in AM EVMs and **boot=net** in KS2 EVMs that will automatically load the kernel and boot. For the exact details of each use **printenv** on the **netboot** variable and then in turn **printenv** other sub-sections of the command. The most important variables in AM57x/DRA7x are **rootpath** and **nfsopts**, and **tftp\_root** and **nfs\_root** in K2H/K/E/L/G.hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r (hXfWithin the default environment for each board that supports networking there is a boot command called r r }r (hlXfWithin the default environment for each board that supports networking there is a boot command called hmj ubj)r }r (hlX **netboot**h~}r (h]h]h]h]h]uhmj h]r hXnetbootr r }r (hlUhmj ubah|j'ubhX in AM EVMs and r r }r (hlX in AM EVMs and hmj ubj)r }r (hlX **boot=net**h~}r (h]h]h]h]h]uhmj h]r hXboot=netr r }r (hlUhmj ubah|j'ubhXa in KS2 EVMs that will automatically load the kernel and boot. For the exact details of each use r r }r (hlXa in KS2 EVMs that will automatically load the kernel and boot. For the exact details of each use hmj ubj)r }r (hlX **printenv**h~}r (h]h]h]h]h]uhmj h]r hXprintenvr r }r (hlUhmj ubah|j'ubhX on the r r }r (hlX on the hmj ubj)r }r (hlX **netboot**h~}r (h]h]h]h]h]uhmj h]r hXnetbootr r }r (hlUhmj ubah|j'ubhX variable and then in turn r r }r (hlX variable and then in turn hmj ubj)r }r (hlX **printenv**h~}r (h]h]h]h]h]uhmj h]r hXprintenvr r }r (hlUhmj ubah|j'ubhXT other sub-sections of the command. The most important variables in AM57x/DRA7x are r r }r (hlXT other sub-sections of the command. The most important variables in AM57x/DRA7x are hmj ubj)r }r (hlX **rootpath**h~}r (h]h]h]h]h]uhmj h]r hXrootpathr r }r! (hlUhmj ubah|j'ubhX and r" r# }r$ (hlX and hmj ubj)r% }r& (hlX **nfsopts**h~}r' (h]h]h]h]h]uhmj h]r( hXnfsoptsr) r* }r+ (hlUhmj% ubah|j'ubhX, and r, r- }r. (hlX, and hmj ubj)r/ }r0 (hlX**tftp\_root**h~}r1 (h]h]h]h]h]uhmj h]r2 hX tftp_rootr3 r4 }r5 (hlUhmj/ ubah|j'ubhX and r6 r7 }r8 (hlX and hmj ubj)r9 }r: (hlX **nfs\_root**h~}r; (h]h]h]h]h]uhmj h]r< hXnfs_rootr= r> }r? (hlUhmj9 ubah|j'ubhX in K2H/K/E/L/G.r@ rA }rB (hlX in K2H/K/E/L/G.hmj ubeubh)rC }rD (hlXOn AM65x GP and IDK boards, Linux kernel can be booted over PRU-ICSSG Ethernet port as well. In the release u-boot image, only first port (MII port 0) of ICSSG0, ICSSG1 and ICSSG2 are enabled. To use second port (MII port 1), user needs to edit the DTS file to enable second port instead of first port and rebuild u-boot images using the updated DTS file. First port is marked as Eth0 on base board (ICSSG2), Eth0 (ICSSG0) and Eth2 (ICSSG1) on IDK Application board. User needs to load and run pru/rtu firmware on ICSSG using env script as shown below before doing network operations such as dhcp, tftp over ICSSG ports. The firmware is loaded from the rootfs/lib/firmware/ti-pruss/ folder for this purpose. For more information on using rproc/RemoteProc in Uboot, see section `here `__. A sample U-Boot env script for AM65x EVM/IDK is shown below for ICSSG0, ICSSG1 and ICSSG2. User needs to customize the serverip and bootdir env variable to that of the tftp server used in the setup.hmj hwhh|hh~}rE (h]h]h]h]h]uhMhhh]rF (hX On AM65x GP and IDK boards, Linux kernel can be booted over PRU-ICSSG Ethernet port as well. In the release u-boot image, only first port (MII port 0) of ICSSG0, ICSSG1 and ICSSG2 are enabled. To use second port (MII port 1), user needs to edit the DTS file to enable second port instead of first port and rebuild u-boot images using the updated DTS file. First port is marked as Eth0 on base board (ICSSG2), Eth0 (ICSSG0) and Eth2 (ICSSG1) on IDK Application board. User needs to load and run pru/rtu firmware on ICSSG using env script as shown below before doing network operations such as dhcp, tftp over ICSSG ports. The firmware is loaded from the rootfs/lib/firmware/ti-pruss/ folder for this purpose. For more information on using rproc/RemoteProc in Uboot, see section rG rH }rI (hlX On AM65x GP and IDK boards, Linux kernel can be booted over PRU-ICSSG Ethernet port as well. In the release u-boot image, only first port (MII port 0) of ICSSG0, ICSSG1 and ICSSG2 are enabled. To use second port (MII port 1), user needs to edit the DTS file to enable second port instead of first port and rebuild u-boot images using the updated DTS file. First port is marked as Eth0 on base board (ICSSG2), Eth0 (ICSSG0) and Eth2 (ICSSG1) on IDK Application board. User needs to load and run pru/rtu firmware on ICSSG using env script as shown below before doing network operations such as dhcp, tftp over ICSSG ports. The firmware is loaded from the rootfs/lib/firmware/ti-pruss/ folder for this purpose. For more information on using rproc/RemoteProc in Uboot, see section hmjC ubh)rJ }rK (hlX9`here `__h~}rL (UnameXherehX.Foundational_Components_U-Boot.html#remoteproch]h]h]h]h]uhmjC h]rM hXhererN rO }rP (hlUhmjJ ubah|hubhX. A sample U-Boot env script for AM65x EVM/IDK is shown below for ICSSG0, ICSSG1 and ICSSG2. User needs to customize the serverip and bootdir env variable to that of the tftp server used in the setup.rQ rR }rS (hlX. A sample U-Boot env script for AM65x EVM/IDK is shown below for ICSSG0, ICSSG1 and ICSSG2. User needs to customize the serverip and bootdir env variable to that of the tftp server used in the setup.hmjC ubeubj)rT }rU (hlXCurrently only 100Mbps and 1Gbps Full Duplex (FD) links are supported for ICSSG ports. Linux Kernel boot with NFS rootfs over PRUETH Ethernet interface has not been validated.rV hmj hwhh|jh~}rW (h]h]h]h]h]uhNhhh]rX h)rY }rZ (hljV hmjT hwhh|hh~}r[ (h]h]h]h]h]uhMh]r\ hXCurrently only 100Mbps and 1Gbps Full Duplex (FD) links are supported for ICSSG ports. Linux Kernel boot with NFS rootfs over PRUETH Ethernet interface has not been validated.r] r^ }r_ (hljV hmjY ubaubaubh)r` }ra (hlX ICSSG0 port 0rb hmj hwhh|hh~}rc (h]h]h]h]h]uhMhhh]rd hX ICSSG0 port 0re rf }rg (hljb hmj` ubaubjr)rh }ri (hlXsetenv start_icssg0 'rproc start 2; rproc start 3' setenv stop_icssg0 'rproc stop 2; rproc stop 3' setenv firmware_dir '/lib/firmware/ti-pruss' setenv get_fdt_net 'run start_icssg0; tftp ${fdtaddr} ${serverip}:${bootdir}/${name_fdt}; run stop_icssg0' setenv get_kern_net 'run start_icssg0; tftp ${loadaddr} ${serverip}:${bootdir}/${name_kern}; run stop_icssg0' setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x0fffff;for overlay in $overlay_files;do; run start_icssg0; \ tftp ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr}; run stop_icssg0; done;' setenv get_firmware_mmc 'load mmc ${bootpart} ${loadaddr} ${firmware_dir}/${firmware_file}' setenv serverip 158.218.113.14 setenv bootdir 06.02.00.58-am6 setenv name_fdt k3-am654-base-board.dtb setenv name_kern Image-am65xx-evm.bin setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' setenv init_icssg0 'setenv ethact pruss0_eth; setenv autoload no; rproc init; setenv loadaddr 0x80000000; \ setenv firmware_file 'am65x-pru0-prueth-fw.elf'; run get_firmware_mmc; rproc load 2 0x80000000 13040; rproc start 2; \ setenv loadaddr 0x89000000; setenv firmware_file am65x-rtu0-prueth-fw.elf; run get_firmware_mmc; rproc load 3 0x89000000 5676; \ rproc start 3; dhcp; run stop_icssg0;' setenv bootcmd 'run init_mmc; run init_icssg0; run get_kern_net; run get_fdt_net ; run get_overlay_net ; run run_kern' saveenv boothmj hwhh|juh~}rj (hhh]h]h]h]h]uhMhhh]rk hXsetenv start_icssg0 'rproc start 2; rproc start 3' setenv stop_icssg0 'rproc stop 2; rproc stop 3' setenv firmware_dir '/lib/firmware/ti-pruss' setenv get_fdt_net 'run start_icssg0; tftp ${fdtaddr} ${serverip}:${bootdir}/${name_fdt}; run stop_icssg0' setenv get_kern_net 'run start_icssg0; tftp ${loadaddr} ${serverip}:${bootdir}/${name_kern}; run stop_icssg0' setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x0fffff;for overlay in $overlay_files;do; run start_icssg0; \ tftp ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr}; run stop_icssg0; done;' setenv get_firmware_mmc 'load mmc ${bootpart} ${loadaddr} ${firmware_dir}/${firmware_file}' setenv serverip 158.218.113.14 setenv bootdir 06.02.00.58-am6 setenv name_fdt k3-am654-base-board.dtb setenv name_kern Image-am65xx-evm.bin setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' setenv init_icssg0 'setenv ethact pruss0_eth; setenv autoload no; rproc init; setenv loadaddr 0x80000000; \ setenv firmware_file 'am65x-pru0-prueth-fw.elf'; run get_firmware_mmc; rproc load 2 0x80000000 13040; rproc start 2; \ setenv loadaddr 0x89000000; setenv firmware_file am65x-rtu0-prueth-fw.elf; run get_firmware_mmc; rproc load 3 0x89000000 5676; \ rproc start 3; dhcp; run stop_icssg0;' setenv bootcmd 'run init_mmc; run init_icssg0; run get_kern_net; run get_fdt_net ; run get_overlay_net ; run run_kern' saveenv bootrl rm }rn (hlUhmjh ubaubh)ro }rp (hlX ICSSG1 port 0rq hmj hwhh|hh~}rr (h]h]h]h]h]uhMhhh]rs hX ICSSG1 port 0rt ru }rv (hljq hmjo ubaubjr)rw }rx (hlXsetenv start_icssg1 'rproc start 6; rproc start 7' setenv stop_icssg1 'rproc stop 6; rproc stop 7' setenv firmware_dir '/lib/firmware/ti-pruss' setenv get_fdt_net 'run start_icssg1; tftp ${fdtaddr} ${serverip}:${bootdir}/${name_fdt}; run stop_icssg1' setenv get_kern_net 'run start_icssg1; tftp ${loadaddr} ${serverip}:${bootdir}/${name_kern}; run stop_icssg1' setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x0fffff;for overlay in $overlay_files;do; run start_icssg1; \ tftp ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr}; run stop_icssg1; done;' setenv get_firmware_mmc 'load mmc ${bootpart} ${loadaddr} ${firmware_dir}/${firmware_file}' setenv serverip 158.218.113.14 setenv bootdir 06.02.00.58-am6 setenv name_fdt k3-am654-base-board.dtb setenv name_kern Image-am65xx-evm.bin setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' setenv init_icssg1 'setenv ethact pruss1_eth; setenv autoload no; rproc init; setenv loadaddr 0x80000000; \ setenv firmware_file 'am65x-pru0-prueth-fw.elf'; run get_firmware_mmc; rproc load 6 0x80000000 13040; rproc start 6; \ setenv loadaddr 0x89000000; setenv firmware_file am65x-rtu0-prueth-fw.elf; run get_firmware_mmc; rproc load 7 0x89000000 5676; \ rproc start 7; dhcp; run stop_icssg1;' setenv bootcmd 'run init_mmc; run init_icssg1; run get_kern_net; run get_fdt_net ; run get_overlay_net ; run run_kern' saveenv boothmj hwhh|juh~}ry (hhh]h]h]h]h]uhMhhh]rz hXsetenv start_icssg1 'rproc start 6; rproc start 7' setenv stop_icssg1 'rproc stop 6; rproc stop 7' setenv firmware_dir '/lib/firmware/ti-pruss' setenv get_fdt_net 'run start_icssg1; tftp ${fdtaddr} ${serverip}:${bootdir}/${name_fdt}; run stop_icssg1' setenv get_kern_net 'run start_icssg1; tftp ${loadaddr} ${serverip}:${bootdir}/${name_kern}; run stop_icssg1' setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x0fffff;for overlay in $overlay_files;do; run start_icssg1; \ tftp ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr}; run stop_icssg1; done;' setenv get_firmware_mmc 'load mmc ${bootpart} ${loadaddr} ${firmware_dir}/${firmware_file}' setenv serverip 158.218.113.14 setenv bootdir 06.02.00.58-am6 setenv name_fdt k3-am654-base-board.dtb setenv name_kern Image-am65xx-evm.bin setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' setenv init_icssg1 'setenv ethact pruss1_eth; setenv autoload no; rproc init; setenv loadaddr 0x80000000; \ setenv firmware_file 'am65x-pru0-prueth-fw.elf'; run get_firmware_mmc; rproc load 6 0x80000000 13040; rproc start 6; \ setenv loadaddr 0x89000000; setenv firmware_file am65x-rtu0-prueth-fw.elf; run get_firmware_mmc; rproc load 7 0x89000000 5676; \ rproc start 7; dhcp; run stop_icssg1;' setenv bootcmd 'run init_mmc; run init_icssg1; run get_kern_net; run get_fdt_net ; run get_overlay_net ; run run_kern' saveenv bootr{ r| }r} (hlUhmjw ubaubh)r~ }r (hlX ICSSG2 port 0r hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hX ICSSG2 port 0r r }r (hlj hmj~ ubaubjr)r }r (hlXsetenv start_icssg2 'rproc start 10; rproc start 11' setenv stop_icssg2 'rproc stop 10; rproc stop 11' setenv firmware_dir '/lib/firmware/ti-pruss' setenv get_fdt_net 'run start_icssg2; tftp ${fdtaddr} ${serverip}:${bootdir}/${name_fdt}; run stop_icssg2' setenv get_kern_net 'run start_icssg2; tftp ${loadaddr} ${serverip}:${bootdir}/${name_kern}; run stop_icssg2' setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x0fffff;for overlay in $overlay_files;do; run start_icssg2; \ tftp ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr}; run stop_icssg2; done;' setenv get_firmware_mmc 'load mmc ${bootpart} ${loadaddr} ${firmware_dir}/${firmware_file}' setenv serverip 158.218.113.14 setenv bootdir 06.02.00.58-am6 setenv name_fdt k3-am654-base-board.dtb setenv name_kern Image-am65xx-evm.bin setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' setenv init_icssg2 'setenv ethact pruss2_eth; setenv autoload no; rproc init; setenv loadaddr 0x80000000; \ setenv firmware_file 'am65x-pru0-prueth-fw.elf'; run get_firmware_mmc; rproc load 10 0x80000000 13040; rproc start 10; \ setenv loadaddr 0x89000000; setenv firmware_file am65x-rtu0-prueth-fw.elf; run get_firmware_mmc; rproc load 11 0x89000000 5676; \ rproc start 11; dhcp; run stop_icssg2;' setenv bootcmd 'run init_mmc; run init_icssg2; run get_kern_net; run get_fdt_net ; run get_overlay_net ; run run_kern' saveenv boothmj hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hXsetenv start_icssg2 'rproc start 10; rproc start 11' setenv stop_icssg2 'rproc stop 10; rproc stop 11' setenv firmware_dir '/lib/firmware/ti-pruss' setenv get_fdt_net 'run start_icssg2; tftp ${fdtaddr} ${serverip}:${bootdir}/${name_fdt}; run stop_icssg2' setenv get_kern_net 'run start_icssg2; tftp ${loadaddr} ${serverip}:${bootdir}/${name_kern}; run stop_icssg2' setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x0fffff;for overlay in $overlay_files;do; run start_icssg2; \ tftp ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr}; run stop_icssg2; done;' setenv get_firmware_mmc 'load mmc ${bootpart} ${loadaddr} ${firmware_dir}/${firmware_file}' setenv serverip 158.218.113.14 setenv bootdir 06.02.00.58-am6 setenv name_fdt k3-am654-base-board.dtb setenv name_kern Image-am65xx-evm.bin setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' setenv init_icssg2 'setenv ethact pruss2_eth; setenv autoload no; rproc init; setenv loadaddr 0x80000000; \ setenv firmware_file 'am65x-pru0-prueth-fw.elf'; run get_firmware_mmc; rproc load 10 0x80000000 13040; rproc start 10; \ setenv loadaddr 0x89000000; setenv firmware_file am65x-rtu0-prueth-fw.elf; run get_firmware_mmc; rproc load 11 0x89000000 5676; \ rproc start 11; dhcp; run stop_icssg2;' setenv bootcmd 'run init_mmc; run init_icssg2; run get_kern_net; run get_fdt_net ; run get_overlay_net ; run run_kern' saveenv bootr r }r (hlUhmj ubaubj)r }r (hlXETo boot over second port (MII port 1) of ICSSG2, user needs to edit arch/arm/dts/k3-am654-base-board-u-boot.dtsi in the U-Boot source tree. See DTS file for instruction. For example, user needs to comment pruss2_emac0 DT node and uncomment pruss2_emac1 node. Similarly to enable second port for ICSSG0 and ICSSG1, user needs to edit arch/arm/dts/k3-am654-idk.dtso and enable pruss0_emac1 and pruss1_emac1 nodes respectives. After this rebuild u-boot images and use it. Port 1 is marked as by Eth1 on on base board (ICSSG2), Eth1 (ICSSG0) and Eth3 (ICSSG1) on IDK Application board.r hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhMh]r hXETo boot over second port (MII port 1) of ICSSG2, user needs to edit arch/arm/dts/k3-am654-base-board-u-boot.dtsi in the U-Boot source tree. See DTS file for instruction. For example, user needs to comment pruss2_emac0 DT node and uncomment pruss2_emac1 node. Similarly to enable second port for ICSSG0 and ICSSG1, user needs to edit arch/arm/dts/k3-am654-idk.dtso and enable pruss0_emac1 and pruss1_emac1 nodes respectives. After this rebuild u-boot images and use it. Port 1 is marked as by Eth1 on on base board (ICSSG2), Eth1 (ICSSG0) and Eth3 (ICSSG1) on IDK Application board.r r }r (hlj hmj ubaubaubjC)r }r (hlUhmj hwhh|jZh~}r (h]h]h]h]h]uhMhhh]r jH)r }r (hlUjLKhmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]ubaubeubeubhn)r }r (hlUhmhshwhh|h}h~}r (h]h]h]h]r Unandr ah]r h auhMhhh]r (h)r }r (hlXNANDr hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXNANDr r }r (hlj hmj ubaubh)r }r (hlUhmj hwhh|hh~}r (hX#CONFIG_part_family in ('J7_family')h]h]h]h]h]uhMhhh]r j)r }r (hlX(NAND is not supported on J721E platform.r hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhMh]r hX(NAND is not supported on J721E platform.r r }r (hlj hmj ubaubaubaubh)r }r (hlXThis section documents how to write files to the NAND device and use it to load and then boot the Linux Kernel using a root filesystem also found on NAND.r hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXThis section documents how to write files to the NAND device and use it to load and then boot the Linux Kernel using a root filesystem also found on NAND.r r }r (hlj hmj ubaubhn)r }r (hlUhmj hwhh|h}h~}r (h]h]h]h]r U3erasing-reading-and-writing-to-from-nand-partitionsr ah]r h, # parts = 10 #: name size offset mask_flags 0: NAND.SPL 0x00020000 0x00000000 0 1: NAND.SPL.backup1 0x00020000 0x00020000 0 2: NAND.SPL.backup2 0x00020000 0x00040000 0 3: NAND.SPL.backup3 0x00020000 0x00060000 0 4: NAND.u-boot-spl-os 0x00040000 0x00080000 0 5: NAND.u-boot 0x00100000 0x000c0000 0 6: NAND.u-boot-env 0x00020000 0x001c0000 0 7: NAND.u-boot-env.backup10x00020000 0x001e0000 0 8: NAND.kernel 0x00800000 0x00200000 0 9: NAND.file-system 0x0f600000 0x00a00000 0hmj hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hXdevice nand0 , # parts = 10 #: name size offset mask_flags 0: NAND.SPL 0x00020000 0x00000000 0 1: NAND.SPL.backup1 0x00020000 0x00020000 0 2: NAND.SPL.backup2 0x00020000 0x00040000 0 3: NAND.SPL.backup3 0x00020000 0x00060000 0 4: NAND.u-boot-spl-os 0x00040000 0x00080000 0 5: NAND.u-boot 0x00100000 0x000c0000 0 6: NAND.u-boot-env 0x00020000 0x001c0000 0 7: NAND.u-boot-env.backup10x00020000 0x001e0000 0 8: NAND.kernel 0x00800000 0x00200000 0 9: NAND.file-system 0x0f600000 0x00a00000 0r r }r (hlUhmj ubaubh)r }r (hlXNote: In later sections the symbol should be replaced with the partition name seen when executing the mtdparts command.r hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXNote: In later sections the symbol should be replaced with the partition name seen when executing the mtdparts command.r r }r (hlj hmj ubaubjC)r }r (hlXErasing Partitionr hmj hwhh|jGh~}r (h]r Uerasing-partitionr ah]h]h]h]r h;auhNhhh]r hXErasing Partitionr r }r (hlj hmj ubaubjr)r }r (hlX nand erase.part hmj hwhh|juh~}r (hhh]h]h]h]h]uhM+hhh]r hX nand erase.part r r }r (hlUhmj ubaubjC)r }r (hlXWriting to Partitionr hmj hwhh|jGh~}r (h]r Uwriting-to-partitionr ah]h]h]h]r hcauhNhhh]r hXWriting to Partitionr! r" }r# (hlj hmj ubaubh)r$ }r% (hlXaWhen writing to NAND partition the file to be written must have previously been copied to memory.r& hmj hwhh|hh~}r' (h]h]h]h]h]uhM%hhh]r( hXaWhen writing to NAND partition the file to be written must have previously been copied to memory.r) r* }r+ (hlj& hmj$ ubaubjr)r, }r- (hlX5nand write hmj hwhh|juh~}r. (hhh]h]h]h]h]uhM5hhh]r/ hX5nand write r0 r1 }r2 (hlUhmj, ubaubh)r3 }r4 (hlXThe symbol refers to the location in memory that a file was read into DDR memory. The symbol represents the amount of bytes (in hex) of the file to write into the NAND partition. Note: When reading a file into DDR, U-boot by default sets the value of environment variable "filesize" to the number of bytes (in hex) that was read via the last read/load command.r5 hmj hwhh|hh~}r6 (h]h]h]h]h]uhM,hhh]r7 hXThe symbol refers to the location in memory that a file was read into DDR memory. The symbol represents the amount of bytes (in hex) of the file to write into the NAND partition. Note: When reading a file into DDR, U-boot by default sets the value of environment variable "filesize" to the number of bytes (in hex) that was read via the last read/load command.r8 r9 }r: (hlj5 hmj3 ubaubjC)r; }r< (hlUhmj hwhh|jZh~}r= (h]h]h]h]h]uhM3hhh]r> (jH)r? }r@ (hlUjLKhmj; hwhh|hh~}rA (h]h]h]h]h]uhKhhh]ubjH)rB }rC (hlXAs an example below shows the process of writing a kernel (zImage) into the NAND's kernel partition. The zImage to be written is loaded from the SD card's rootfs (2nd) partition. Loading zImage from MMC to DDR memoryrD jLKhmj; hwhh|hh~}rE (h]h]h]h]h]uhM7hhh]rF hXAs an example below shows the process of writing a kernel (zImage) into the NAND's kernel partition. The zImage to be written is loaded from the SD card's rootfs (2nd) partition. Loading zImage from MMC to DDR memoryrG rH }rI (hljD hmjB ubaubeubjr)rJ }rK (hlXU-Boot # mmc dev 0; U-Boot # setenv devnum 0 U-Boot # setenv devtype mmc U-Boot # mmc rescan U-Boot # load ${devtype} 1:2 ${loadaddr} /boot/zImagehmj hwhh|juh~}rL (hhh]h]h]h]h]uhMFhhh]rM hXU-Boot # mmc dev 0; U-Boot # setenv devnum 0 U-Boot # setenv devtype mmc U-Boot # mmc rescan U-Boot # load ${devtype} 1:2 ${loadaddr} /boot/zImagerN rO }rP (hlUhmjJ ubaubh)rQ }rR (hlXNNow that zImage is loaded into memory time to write it into the NAND partitionrS hmj hwhh|hh~}rT (h]h]h]h]h]uhMAhhh]rU hXNNow that zImage is loaded into memory time to write it into the NAND partitionrV rW }rX (hljS hmjQ ubaubjr)rY }rZ (hlX\U-Boot # nand erase.part NAND.kernel U-Boot # nand write ${loadaddr} NAND.kernel ${filesize}hmj hwhh|juh~}r[ (hhh]h]h]h]h]uhMQhhh]r\ hX\U-Boot # nand erase.part NAND.kernel U-Boot # nand write ${loadaddr} NAND.kernel ${filesize}r] r^ }r_ (hlUhmjY ubaubjC)r` }ra (hlXReading from Partitionrb hmj hwhh|jGh~}rc (h]rd Ureading-from-partitionre ah]h]h]h]rf hauhNhhh]rg hXReading from Partitionrh ri }rj (hljb hmj` ubaubjr)rk }rl (hlX(nand read hmj hwhh|juh~}rm (hhh]h]h]h]h]uhMYhhh]rn hX(nand read ro rp }rq (hlUhmjk ubaubh)rr }rs (hlXThe symbol should be replaced with the location in DDR that you want the contents of the NAND partition to be copied to. The symbol contains the NAND partition name you want to read from.rt hmj hwhh|hh~}ru (h]h]h]h]h]uhMPhhh]rv hXThe symbol should be replaced with the location in DDR that you want the contents of the NAND partition to be copied to. The symbol contains the NAND partition name you want to read from.rw rx }ry (hljt hmjr ubaubjC)rz }r{ (hlUhmj hwhh|jZh~}r| (h]h]h]h]h]uhMUhhh]r} jH)r~ }r (hlUjLKhmjz hwhh|hh~}r (h]h]h]h]h]uhKhhh]ubaubeubhn)r }r (hlUhmj hwhh|h}h~}r (h]h]h]h]r Uwriting-to-nand-via-dfur ah]r h,auhMXhhh]r (h)r }r (hlXWriting to NAND via DFUr hmj hwhh|hh~}r (h]h]h]h]h]uhMXhhh]r hXWriting to NAND via DFUr r }r (hlj hmj ubaubh)r }r (hlX]Currently in boards that support using DFU, the default build supports writing to NAND, so no custom build is required. To see the list of available places to write to (in DFU terms, altsettings) use the **mtdparts** command to list the known MTD partitions and **printenv dfu\_alt\_settings** to see how they are mapped and exposed to **dfu-util**.hmj hwhh|hh~}r (h]h]h]h]h]uhMZhhh]r (hXCurrently in boards that support using DFU, the default build supports writing to NAND, so no custom build is required. To see the list of available places to write to (in DFU terms, altsettings) use the r r }r (hlXCurrently in boards that support using DFU, the default build supports writing to NAND, so no custom build is required. To see the list of available places to write to (in DFU terms, altsettings) use the hmj ubj)r }r (hlX **mtdparts**h~}r (h]h]h]h]h]uhmj h]r hXmtdpartsr r }r (hlUhmj ubah|j'ubhX. command to list the known MTD partitions and r r }r (hlX. command to list the known MTD partitions and hmj ubj)r }r (hlX**printenv dfu\_alt\_settings**h~}r (h]h]h]h]h]uhmj h]r hXprintenv dfu_alt_settingsr r }r (hlUhmj ubah|j'ubhX+ to see how they are mapped and exposed to r r }r (hlX+ to see how they are mapped and exposed to hmj ubj)r }r (hlX **dfu-util**h~}r (h]h]h]h]h]uhmj h]r hXdfu-utilr r }r (hlUhmj ubah|j'ubhX.r }r (hlX.hmj ubeubjr)r }r (hlXWU-Boot # mtdparts device nand0 , # parts = 8 #: name size offset mask_flags 0: NAND.SPL 0x00020000 0x00000000 0 1: NAND.SPL.backup1 0x00020000 0x00020000 0 2: NAND.SPL.backup2 0x00020000 0x00040000 0 3: NAND.SPL.backup3 0x00020000 0x00060000 0 4: NAND.u-boot 0x001e0000 0x00080000 0 5: NAND.u-boot-env 0x00020000 0x00260000 0 6: NAND.kernel 0x00500000 0x00280000 0 7: NAND.file-system 0x0f880000 0x00780000 0 active partition: nand0,0 - (SPL) 0x00080000 @ 0x00000000 U-Boot # printenv dfu_alt_info_nand dfu_alt_info=NAND.SPL part 0 1;NAND.SPL.backup1 part 0 2;NAND.SPL.backup2 part 0 3;NAND.SPL.backup3 part 0 4;NAND.u-boot part 0 5;NAND.kernel part 0 7;NAND.file-system part 0 8hmj hwhh|juh~}r (hhh]h]h]h]h]uhMnhhh]r hXWU-Boot # mtdparts device nand0 , # parts = 8 #: name size offset mask_flags 0: NAND.SPL 0x00020000 0x00000000 0 1: NAND.SPL.backup1 0x00020000 0x00020000 0 2: NAND.SPL.backup2 0x00020000 0x00040000 0 3: NAND.SPL.backup3 0x00020000 0x00060000 0 4: NAND.u-boot 0x001e0000 0x00080000 0 5: NAND.u-boot-env 0x00020000 0x00260000 0 6: NAND.kernel 0x00500000 0x00280000 0 7: NAND.file-system 0x0f880000 0x00780000 0 active partition: nand0,0 - (SPL) 0x00080000 @ 0x00000000 U-Boot # printenv dfu_alt_info_nand dfu_alt_info=NAND.SPL part 0 1;NAND.SPL.backup1 part 0 2;NAND.SPL.backup2 part 0 3;NAND.SPL.backup3 part 0 4;NAND.u-boot part 0 5;NAND.kernel part 0 7;NAND.file-system part 0 8r r }r (hlUhmj ubaubh)r }r (hlXBThis means that you can tell dfu-util to write anything to any of:r hmj hwhh|hh~}r (h]h]h]h]h]uhMthhh]r hXBThis means that you can tell dfu-util to write anything to any of:r r }r (hlj hmj ubaubj#)r }r (hlUhmj hwhh|j&h~}r (j(X-h]h]h]h]h]uhMvhhh]r (j )r }r (hlXNAND.SPLr hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhMvh]r hXNAND.SPLr r }r (hlj hmj ubaubaubj )r }r (hlXNAND.SPL.backup1r hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhMwh]r hXNAND.SPL.backup1r r }r (hlj hmj ubaubaubj )r }r (hlXNAND.SPL.backup2r hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhMxh]r hXNAND.SPL.backup2r r }r (hlj hmj ubaubaubj )r }r (hlXNAND.SPL.backup3r hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhMyh]r hXNAND.SPL.backup3r r }r (hlj hmj ubaubaubj )r }r (hlX NAND.u-bootr hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhMzh]r hX NAND.u-bootr r }r (hlj hmj ubaubaubj )r }r (hlX NAND.kernelr hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlj hmj hwhh|hh~}r (h]h]h]h]h]uhM{h]r hX NAND.kernelr r }r (hlj hmj ubaubaubj )r }r (hlXNAND.file-system hmj hwhh|jh~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlXNAND.file-systemr hmj hwhh|hh~}r (h]h]h]h]h]uhM|h]r hXNAND.file-systemr r }r (hlj hmj ubaubaubeubh)r }r (hlX{Before writing you must erase at least the area to be written to. Then to start DFU on the target on the first NAND device:r hmj hwhh|hh~}r (h]h]h]h]h]uhM~hhh]r hX{Before writing you must erase at least the area to be written to. Then to start DFU on the target on the first NAND device:r r! }r" (hlj hmj ubaubjr)r# }r$ (hlX`U-Boot # nand erase.chip U-Boot # setenv dfu_alt_info ${dfu_alt_info_nand} U-Boot # dfu 0 nand 0hmj hwhh|juh~}r% (hhh]h]h]h]h]uhMhhh]r& hX`U-Boot # nand erase.chip U-Boot # setenv dfu_alt_info ${dfu_alt_info_nand} U-Boot # dfu 0 nand 0r' r( }r) (hlUhmj# ubaubh)r* }r+ (hlX@Then on the host PC to write **MLO** to the first SPL partition:r, hmj hwhh|hh~}r- (h]h]h]h]h]uhMhhh]r. (hXThen on the host PC to write r/ r0 }r1 (hlXThen on the host PC to write hmj* ubj)r2 }r3 (hlX**MLO**h~}r4 (h]h]h]h]h]uhmj* h]r5 hXMLOr6 r7 }r8 (hlUhmj2 ubah|j'ubhX to the first SPL partition:r9 r: }r; (hlX to the first SPL partition:hmj* ubeubjr)r< }r= (hlX"$ sudo dfu-util -D MLO -a NAND.SPLhmj hwhh|juh~}r> (hhh]h]h]h]h]uhMhhh]r? hX"$ sudo dfu-util -D MLO -a NAND.SPLr@ rA }rB (hlUhmj< ubaubeubhn)rC }rD (hlUhmj hwhh|h}h~}rE (h]h]h]h]rF U nand-bootrG ah]rH hMauhMhhh]rI (h)rJ }rK (hlX NAND BootrL hmjC hwhh|hh~}rM (h]h]h]h]h]uhMhhh]rN hX NAND BootrO rP }rQ (hljL hmjJ ubaubh)rR }rS (hlXIf you want to load and run U-Boot from NAND the first step is insuring that the appropriate U-boot files are loaded in the correct partition. For AM335x, AM437x, DRA7x devices this means writing the file MLO to the NAND's SPL partition. For OMAP-L138 device, write the .ais image to the NAND's partition. For all devices this requires writing u-boot.img to the NAND's U-Boot partition.rT hmjC hwhh|hh~}rU (h]h]h]h]h]uhMhhh]rV hXIf you want to load and run U-Boot from NAND the first step is insuring that the appropriate U-boot files are loaded in the correct partition. For AM335x, AM437x, DRA7x devices this means writing the file MLO to the NAND's SPL partition. For OMAP-L138 device, write the .ais image to the NAND's partition. For all devices this requires writing u-boot.img to the NAND's U-Boot partition.rW rX }rY (hljT hmjR ubaubj)rZ }r[ (hlXvThe NAND partition of OMAP-L138 is different from other devices, please use the following commands to program the NANDhmjC hwhh|jh~}r\ (h]h]h]h]h]uhNhhh]r] h)r^ }r_ (hlXvThe NAND partition of OMAP-L138 is different from other devices, please use the following commands to program the NANDr` hmjZ hwhh|hh~}ra (h]h]h]h]h]uhMh]rb hXvThe NAND partition of OMAP-L138 is different from other devices, please use the following commands to program the NANDrc rd }re (hlj` hmj^ ubaubaubjr)rf }rg (hlX_=> setenv ipaddr => setenv serverip => tftp ${loadaddr} ${serverip}:u-boot-omapl138-lcdk.ais => print filesize => nand erase 0x20000 => nand write ${loadaddr} 0x20000 * hex_len is next sector boundary of the filesize. The sector size is 0x10000. set dip switch to NAND boot and power cycle the EVMhmjC hwhh|juh~}rh (hhh]h]h]h]h]uhMhhh]ri hX_=> setenv ipaddr => setenv serverip => tftp ${loadaddr} ${serverip}:u-boot-omapl138-lcdk.ais => print filesize => nand erase 0x20000 => nand write ${loadaddr} 0x20000 * hex_len is next sector boundary of the filesize. The sector size is 0x10000. set dip switch to NAND boot and power cycle the EVMrj rk }rl (hlUhmjf ubaubh)rm }rn (hlXOnce the file(s) have been written to NAND the board should then be powered off. Next evm's boot switches need to be configured for NAND booting. To understand the appropriate boot switches settings please see the evm's hardware setup guide.ro hmjC hwhh|hh~}rp (h]h]h]h]h]uhMhhh]rq hXOnce the file(s) have been written to NAND the board should then be powered off. Next evm's boot switches need to be configured for NAND booting. To understand the appropriate boot switches settings please see the evm's hardware setup guide.rr rs }rt (hljo hmjm ubaubjC)ru }rv (hlUhmjC hwhh|jZh~}rw (h]h]h]h]h]uhMhhh]rx jH)ry }rz (hlUjLKhmju hwhh|hh~}r{ (h]h]h]h]h]uhKhhh]ubaubeubhn)r| }r} (hlUhmj hwhh|h}h~}r~ (h]h]h]h]r U'booting-kernel-and-filesystem-from-nandr ah]r hKauhMhhh]r (h)r }r (hlX'Booting Kernel and Filesystem from NANDr hmj| hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hX'Booting Kernel and Filesystem from NANDr r }r (hlj hmj ubaubh)r }r (hlXAIf a user wants to use NAND as their primary storage then the NAND flash must have individual partitions for all the critical software needed to boot the kernel. At a minimum this includes kernel, dtb, file system. Some SoCs require additional files and firmware which also need to be stored in different NAND partitions.r hmj| hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXAIf a user wants to use NAND as their primary storage then the NAND flash must have individual partitions for all the critical software needed to boot the kernel. At a minimum this includes kernel, dtb, file system. Some SoCs require additional files and firmware which also need to be stored in different NAND partitions.r r }r (hlj hmj ubaubh)r }r (hlXTSimilar to booting the kernel from any interface the user must insure that all required files needed for booting are loaded in DDR memory. The only exception is the filesystem which will be loaded by the kernel via the bootargs parameters. Bootargs contains information passed to the kernel including where and how to mount the file system.r hmj| hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXTSimilar to booting the kernel from any interface the user must insure that all required files needed for booting are loaded in DDR memory. The only exception is the filesystem which will be loaded by the kernel via the bootargs parameters. Bootargs contains information passed to the kernel including where and how to mount the file system.r r }r (hlj hmj ubaubh)r }r (hlXRThe below contains example bootargs used by DRA7x evm for using a ubifs filesystemr hmj| hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXRThe below contains example bootargs used by DRA7x evm for using a ubifs filesystemr r }r (hlj hmj ubaubjr)r }r (hlX{setenv bootargs console=${console} ${optargs} root=ubi0:rootfs rw ubi.mtd=NAND.file-system,2048 rootfstype=ubifs rootwait=1hmj| hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hX{setenv bootargs console=${console} ${optargs} root=ubi0:rootfs rw ubi.mtd=NAND.file-system,2048 rootfstype=ubifs rootwait=1r r }r (hlUhmj ubaubh)r }r (hlX@In the above example bootargs, "rootfs" stands for the value specified by in the "vol\_name" parameter defined in the ubinize.cfg file. In ubi.mtd "NAND.file-system" and "2048" represents the name of the partition that contains the ubifs and page size. Rootfstype simply tells the kernel what type of file system to use.hmj| hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hX?In the above example bootargs, "rootfs" stands for the value specified by in the "vol_name" parameter defined in the ubinize.cfg file. In ubi.mtd "NAND.file-system" and "2048" represents the name of the partition that contains the ubifs and page size. Rootfstype simply tells the kernel what type of file system to use.r r }r (hlX@In the above example bootargs, "rootfs" stands for the value specified by in the "vol\_name" parameter defined in the ubinize.cfg file. In ubi.mtd "NAND.file-system" and "2048" represents the name of the partition that contains the ubifs and page size. Rootfstype simply tells the kernel what type of file system to use.hmj ubaubh)r }r (hlXBy default for our evms properly loading, setting bootargs and booting the kernel is handled by running "run nandboot" in U-boot. Information on creating a UBIFS can be found `here `__.hmj| hwhh|hh~}r (h]h]h]h]h]uhMhhh]r (hXBy default for our evms properly loading, setting bootargs and booting the kernel is handled by running "run nandboot" in U-boot. Information on creating a UBIFS can be found r r }r (hlXBy default for our evms properly loading, setting bootargs and booting the kernel is handled by running "run nandboot" in U-boot. Information on creating a UBIFS can be found hmj ubh)r }r (hlXc`here `__h~}r (UnameXherehXXFoundational_Components/Kernel/Kernel_Drivers/Storage/NAND.html#building-ubi-file-systemh]h]h]h]h]uhmj h]r hXherer r }r (hlUhmj ubah|hubhX.r }r (hlX.hmj ubeubjC)r }r (hlUhmj| hwhh|jZh~}r (h]h]h]h]h]uhMhhh]r jH)r }r (hlUjLKhmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]ubaubeubeubhn)r }r (hlUhmhshwhh|h}h~}r (h]h]h]h]r Usd-emmc-or-usb-storager ah]r hTauhMhhh]r (h)r }r (hlXSD, eMMC or USB Storager hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXSD, eMMC or USB Storager r }r (hlj hmj ubaubh)r }r (hlXxThe commands for using SD cards, eMMC flash and USB mass storage devices (hard drives, flash drives, card readers, etc) are all very similar. The biggest difference is that on some hardware we may not be able to run U-Boot out of ROM from the storage device as it is unsupported. Once U-Boot is running however, any of these may be used for the kernel and the root filesystem.r hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXxThe commands for using SD cards, eMMC flash and USB mass storage devices (hard drives, flash drives, card readers, etc) are all very similar. The biggest difference is that on some hardware we may not be able to run U-Boot out of ROM from the storage device as it is unsupported. Once U-Boot is running however, any of these may be used for the kernel and the root filesystem.r r }r (hlj hmj ubaubhn)r }r (hlUhmj hwhh|h}h~}r (h]h]h]h]r Upartitioning-emmc-from-u-bootr ah]r h/auhMhhh]r (h)r }r (hlXPartitioning eMMC from U-Bootr hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXPartitioning eMMC from U-Bootr r }r (hlj hmj ubaubh)r }r (hlXThe eMMC device typically ships without any partition table. We make use of the GPT support in U-Boot to write a GPT partition table to eMMC. In this case we need to use the **uuidgen** program on the host to create the UUIDs used for the disk and each partition.hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r (hXThe eMMC device typically ships without any partition table. We make use of the GPT support in U-Boot to write a GPT partition table to eMMC. In this case we need to use the r r }r (hlXThe eMMC device typically ships without any partition table. We make use of the GPT support in U-Boot to write a GPT partition table to eMMC. In this case we need to use the hmj ubj)r }r (hlX **uuidgen**h~}r (h]h]h]h]h]uhmj h]r hXuuidgenr r }r (hlUhmj ubah|j'ubhXN program on the host to create the UUIDs used for the disk and each partition.r r }r (hlXN program on the host to create the UUIDs used for the disk and each partition.hmj ubeubjr)r }r (hlX6$ uuidgen ...first uuid... $ uuidgen ...second uuid...hmj hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hX6$ uuidgen ...first uuid... $ uuidgen ...second uuid...r r }r (hlUhmj ubaubjr)r }r (hlXU-Boot # printenv partitions uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_gpt_rootfs} U-Boot # setenv uuid_gpt_disk ...first uuid... U-Boot # setenv uuid_gpt_rootfs ...second uuid... U-Boot # gpt write mmc 1 ${partitions}hmj hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hXU-Boot # printenv partitions uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_gpt_rootfs} U-Boot # setenv uuid_gpt_disk ...first uuid... U-Boot # setenv uuid_gpt_rootfs ...second uuid... U-Boot # gpt write mmc 1 ${partitions}r r }r (hlUhmj ubaubh)r }r (hlX:A reset is required for the partition table to be visible.r hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hX:A reset is required for the partition table to be visible.r r }r (hlj hmj ubaubeubhn)r }r (hlUhmj hwhh|h}h~}r (h]h]h]h]r U"updating-an-sd-card-from-a-host-pcr ah]r h.auhMhhh]r (h)r }r (hlX"Updating an SD card from a host PCr hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r hX"Updating an SD card from a host PCr! r" }r# (hlj hmj ubaubh)r$ }r% (hlXThis section assume that you have created an SD card following the instructions on `Processor SDK Linux Create SD Card Script `__ or have made a compatible layout by hand. In this case, you will need to copy the all the boot images (**MLO** and **u-boot.img** for 32-bit platforms, **tiboot3.bin**, **sysfw.itb**, **tispl.bin**, **u-boot.img** for K3 based platforms) files to the *boot* partition. At this point, the card is now bootable in the SD card slot. We default to using **/boot/${bootfile}** on the *rootfs* partition and the device tree file loaded from **/boot** with the same name as in the kernel.hmj hwhh|hh~}r& (h]h]h]h]h]uhMhhh]r' (hXSThis section assume that you have created an SD card following the instructions on r( r) }r* (hlXSThis section assume that you have created an SD card following the instructions on hmj$ ubh)r+ }r, (hlXg`Processor SDK Linux Create SD Card Script `__h~}r- (UnameX)Processor SDK Linux Create SD Card ScripthX7Overview/Processor_SDK_Linux_create_SD_card_script.htmlh]h]h]h]h]uhmj$ h]r. hX)Processor SDK Linux Create SD Card Scriptr/ r0 }r1 (hlUhmj+ ubah|hubhXh or have made a compatible layout by hand. In this case, you will need to copy the all the boot images (r2 r3 }r4 (hlXh or have made a compatible layout by hand. In this case, you will need to copy the all the boot images (hmj$ ubj)r5 }r6 (hlX**MLO**h~}r7 (h]h]h]h]h]uhmj$ h]r8 hXMLOr9 r: }r; (hlUhmj5 ubah|j'ubhX and r< r= }r> (hlX and hmj$ ubj)r? }r@ (hlX**u-boot.img**h~}rA (h]h]h]h]h]uhmj$ h]rB hX u-boot.imgrC rD }rE (hlUhmj? ubah|j'ubhX for 32-bit platforms, rF rG }rH (hlX for 32-bit platforms, hmj$ ubj)rI }rJ (hlX**tiboot3.bin**h~}rK (h]h]h]h]h]uhmj$ h]rL hX tiboot3.binrM rN }rO (hlUhmjI ubah|j'ubhX, rP rQ }rR (hlX, hmj$ ubj)rS }rT (hlX **sysfw.itb**h~}rU (h]h]h]h]h]uhmj$ h]rV hX sysfw.itbrW rX }rY (hlUhmjS ubah|j'ubhX, rZ r[ }r\ (hlX, hmj$ ubj)r] }r^ (hlX **tispl.bin**h~}r_ (h]h]h]h]h]uhmj$ h]r` hX tispl.binra rb }rc (hlUhmj] ubah|j'ubhX, rd re }rf (hlX, hmj$ ubj)rg }rh (hlX**u-boot.img**h~}ri (h]h]h]h]h]uhmj$ h]rj hX u-boot.imgrk rl }rm (hlUhmjg ubah|j'ubhX& for K3 based platforms) files to the rn ro }rp (hlX& for K3 based platforms) files to the hmj$ ubcdocutils.nodes emphasis rq )rr }rs (hlX*boot*h~}rt (h]h]h]h]h]uhmj$ h]ru hXbootrv rw }rx (hlUhmjr ubah|Uemphasisry ubhX] partition. At this point, the card is now bootable in the SD card slot. We default to using rz r{ }r| (hlX] partition. At this point, the card is now bootable in the SD card slot. We default to using hmj$ ubj)r} }r~ (hlX**/boot/${bootfile}**h~}r (h]h]h]h]h]uhmj$ h]r hX/boot/${bootfile}r r }r (hlUhmj} ubah|j'ubhX on the r r }r (hlX on the hmj$ ubjq )r }r (hlX*rootfs*h~}r (h]h]h]h]h]uhmj$ h]r hXrootfsr r }r (hlUhmj ubah|jy ubhX0 partition and the device tree file loaded from r r }r (hlX0 partition and the device tree file loaded from hmj$ ubj)r }r (hlX **/boot**h~}r (h]h]h]h]h]uhmj$ h]r hX/bootr r }r (hlUhmj ubah|j'ubhX% with the same name as in the kernel.r r }r (hlX% with the same name as in the kernel.hmj$ ubeubh)r }r (hlXHowever, if you are using OMAP-L138 based board (like the LCDK), then you need to write the generated ``u-boot.ais`` image to the SD card using ``dd`` command.hmj hwhh|hh~}r (h]h]h]h]h]uhMhhh]r (hXfHowever, if you are using OMAP-L138 based board (like the LCDK), then you need to write the generated r r }r (hlXfHowever, if you are using OMAP-L138 based board (like the LCDK), then you need to write the generated hmj ubj)r }r (hlX``u-boot.ais``h~}r (h]h]h]h]h]uhmj h]r hX u-boot.aisr r }r (hlUhmj ubah|jubhX image to the SD card using r r }r (hlX image to the SD card using hmj ubj)r }r (hlX``dd``h~}r (h]h]h]h]h]uhmj h]r hXddr r }r (hlUhmj ubah|jubhX command.r r }r (hlX command.hmj ubeubjr)r }r (hlX@$ sudo dd if=u-boot.ais of=/dev/sd seek=117 bs=512 conv=fsynchmj hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hX@$ sudo dd if=u-boot.ais of=/dev/sd seek=117 bs=512 conv=fsyncr r }r (hlUhmj ubaubeubhn)r }r (hlUhmj hwhh|h}h~}r (h]h]h]h]r U%updating-an-sd-card-or-emmc-using-dfur ah]r hauhM hhh]r (h)r }r (hlX%Updating an SD card or eMMC using DFUr hmj hwhh|hh~}r (h]h]h]h]h]uhM hhh]r hX%Updating an SD card or eMMC using DFUr r }r (hlj hmj ubaubh)r }r (hlXTo see the list of available places to write to (in DFU terms, altsettings) use the **mmc part** command to list the partitions on the MMC device and **printenv dfu\_alt\_settings\_mmc** or **dfu\_alt\_settings\_emmc** to see how they are mapped and exposed to **dfu-util**.hmj hwhh|hh~}r (h]h]h]h]h]uhM hhh]r (hXTTo see the list of available places to write to (in DFU terms, altsettings) use the r r }r (hlXTTo see the list of available places to write to (in DFU terms, altsettings) use the hmj ubj)r }r (hlX **mmc part**h~}r (h]h]h]h]h]uhmj h]r hXmmc partr r }r (hlUhmj ubah|j'ubhX6 command to list the partitions on the MMC device and r r }r (hlX6 command to list the partitions on the MMC device and hmj ubj)r }r (hlX$**printenv dfu\_alt\_settings\_mmc**h~}r (h]h]h]h]h]uhmj h]r hXprintenv dfu_alt_settings_mmcr r }r (hlUhmj ubah|j'ubhX or r r }r (hlX or hmj ubj)r }r (hlX**dfu\_alt\_settings\_emmc**h~}r (h]h]h]h]h]uhmj h]r hXdfu_alt_settings_emmcr r }r (hlUhmj ubah|j'ubhX+ to see how they are mapped and exposed to r r }r (hlX+ to see how they are mapped and exposed to hmj ubj)r }r (hlX **dfu-util**h~}r (h]h]h]h]h]uhmj h]r hXdfu-utilr r }r (hlUhmj ubah|j'ubhX.r }r (hlX.hmj ubeubjr)r }r (hlXU-Boot# mmc part Partition Map for MMC device 0 -- Partition Type: DOS Partition Start Sector Num Sectors Type 1 63 144522 c Boot 2 160650 1847475 83 3 2024190 1815345 83 U-Boot# printenv dfu_alt_info_mmc dfu_alt_info=boot part 0 1;rootfs part 0 2;MLO fat 0 1;u-boot.img fat 0 1;uEnv.txt fat 0 1"hmj hwhh|juh~}r (hhh]h]h]h]h]uhMhhh]r hXU-Boot# mmc part Partition Map for MMC device 0 -- Partition Type: DOS Partition Start Sector Num Sectors Type 1 63 144522 c Boot 2 160650 1847475 83 3 2024190 1815345 83 U-Boot# printenv dfu_alt_info_mmc dfu_alt_info=boot part 0 1;rootfs part 0 2;MLO fat 0 1;u-boot.img fat 0 1;uEnv.txt fat 0 1"r r }r(hlUhmj ubaubh)r}r(hlXBThis means that you can tell dfu-util to write anything to any of:rhmj hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXBThis means that you can tell dfu-util to write anything to any of:rr}r(hljhmjubaubj#)r }r (hlUhmj hwhh|j&h~}r (j(X-h]h]h]h]h]uhM!hhh]r (j )r }r(hlXbootrhmj hwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmj hwhh|hh~}r(h]h]h]h]h]uhM!h]rhXbootrr}r(hljhmjubaubaubj )r}r(hlXrootfsrhmj hwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r (h]h]h]h]h]uhM"h]r!hXrootfsr"r#}r$(hljhmjubaubaubj )r%}r&(hlXMLOr'hmj hwhh|jh~}r((h]h]h]h]h]uhNhhh]r)h)r*}r+(hlj'hmj%hwhh|hh~}r,(h]h]h]h]h]uhM#h]r-hXMLOr.r/}r0(hlj'hmj*ubaubaubj )r1}r2(hlX u-boot.imgr3hmj hwhh|jh~}r4(h]h]h]h]h]uhNhhh]r5h)r6}r7(hlj3hmj1hwhh|hh~}r8(h]h]h]h]h]uhM$h]r9hX u-boot.imgr:r;}r<(hlj3hmj6ubaubaubj )r=}r>(hlX uEnv.txt hmj hwhh|jh~}r?(h]h]h]h]h]uhNhhh]r@h)rA}rB(hlXuEnv.txtrChmj=hwhh|hh~}rD(h]h]h]h]h]uhM%h]rEhXuEnv.txtrFrG}rH(hljChmjAubaubaubeubh)rI}rJ(hlXbAnd that the **MLO**, **u-boot.img** and **uEnv.txt** files are to be written to a FAT filesystem.hmj hwhh|hh~}rK(h]h]h]h]h]uhM'hhh]rL(hX And that the rMrN}rO(hlX And that the hmjIubj)rP}rQ(hlX**MLO**h~}rR(h]h]h]h]h]uhmjIh]rShXMLOrTrU}rV(hlUhmjPubah|j'ubhX, rWrX}rY(hlX, hmjIubj)rZ}r[(hlX**u-boot.img**h~}r\(h]h]h]h]h]uhmjIh]r]hX u-boot.imgr^r_}r`(hlUhmjZubah|j'ubhX and rarb}rc(hlX and hmjIubj)rd}re(hlX **uEnv.txt**h~}rf(h]h]h]h]h]uhmjIh]rghXuEnv.txtrhri}rj(hlUhmjdubah|j'ubhX- files are to be written to a FAT filesystem.rkrl}rm(hlX- files are to be written to a FAT filesystem.hmjIubeubh)rn}ro(hlX3To start DFU on the target on the first MMC device:rphmj hwhh|hh~}rq(h]h]h]h]h]uhM*hhh]rrhX3To start DFU on the target on the first MMC device:rsrt}ru(hljphmjnubaubjr)rv}rw(hlXEU-Boot # setenv dfu_alt_info ${dfu_alt_info_mmc} U-Boot # dfu 0 mmc 0hmj hwhh|juh~}rx(hhh]h]h]h]h]uhM9hhh]ryhXEU-Boot # setenv dfu_alt_info ${dfu_alt_info_mmc} U-Boot # dfu 0 mmc 0rzr{}r|(hlUhmjvubaubh)r}}r~(hlX}On boards like AM57x GP EVM or BeagleBoard x15, where the second USB instance is used as USB client, the dfu command becomes:rhmj hwhh|hh~}r(h]h]h]h]h]uhM1hhh]rhX}On boards like AM57x GP EVM or BeagleBoard x15, where the second USB instance is used as USB client, the dfu command becomes:rr}r(hljhmj}ubaubjr)r}r(hlXU-Boot # dfu 1 mmc 0hmj hwhh|juh~}r(hhh]h]h]h]h]uhMAhhh]rhXU-Boot # dfu 1 mmc 0rr}r(hlUhmjubaubh)r}r(hlXCThen on the host PC to write **MLO** to an existing boot partition:rhmj hwhh|hh~}r(h]h]h]h]h]uhM8hhh]r(hXThen on the host PC to write rr}r(hlXThen on the host PC to write hmjubj)r}r(hlX**MLO**h~}r(h]h]h]h]h]uhmjh]rhXMLOrr}r(hlUhmjubah|j'ubhX to an existing boot partition:rr}r(hlX to an existing boot partition:hmjubeubjr)r}r(hlX$ sudo dfu-util -D MLO -a MLOhmj hwhh|juh~}r(hhh]h]h]h]h]uhMGhhh]rhX$ sudo dfu-util -D MLO -a MLOrr}r(hlUhmjubaubh)r}r(hlXtOn the host PC to overwrite the current boot partition contents with a new created on the host FAT filesystem image:rhmj hwhh|hh~}r(h]h]h]h]h]uhM>hhh]rhXtOn the host PC to overwrite the current boot partition contents with a new created on the host FAT filesystem image:rr}r(hljhmjubaubjr)r}r(hlX"$ sudo dfu-util -D fat.img -a boothmj hwhh|juh~}r(hhh]h]h]h]h]uhMNhhh]rhX"$ sudo dfu-util -D fat.img -a bootrr}r(hlUhmjubaubeubhn)r}r(hlUhmj hwhh|h}h~}r(h]h]h]h]rU+updating-an-sd-card-or-emmc-with-raw-writesrah]rh(auhMFhhh]r(h)r}r(hlX+Updating an SD card or eMMC with RAW writesrhmjhwhh|hh~}r(h]h]h]h]h]uhMFhhh]rhX+Updating an SD card or eMMC with RAW writesrr}r(hljhmjubaubh)r}r(hlXIn some cases it is desirable to write **MLO** and **u-boot.img** as raw images to the MMC device rather than in a filesystem. eMMC requires this, for example. In that case, the following is how to program these files and not overwrite the partition table on the device. We assume that the files exist on a SD card. In addition you may wish to write a filesystem image to the device, so an example is also provided.hmjhwhh|hh~}r(h]h]h]h]h]uhMHhhh]r(hX'In some cases it is desirable to write rr}r(hlX'In some cases it is desirable to write hmjubj)r}r(hlX**MLO**h~}r(h]h]h]h]h]uhmjh]rhXMLOrr}r(hlUhmjubah|j'ubhX and rr}r(hlX and hmjubj)r}r(hlX**u-boot.img**h~}r(h]h]h]h]h]uhmjh]rhX u-boot.imgrr}r(hlUhmjubah|j'ubhX^ as raw images to the MMC device rather than in a filesystem. eMMC requires this, for example. In that case, the following is how to program these files and not overwrite the partition table on the device. We assume that the files exist on a SD card. In addition you may wish to write a filesystem image to the device, so an example is also provided.rr}r(hlX^ as raw images to the MMC device rather than in a filesystem. eMMC requires this, for example. In that case, the following is how to program these files and not overwrite the partition table on the device. We assume that the files exist on a SD card. In addition you may wish to write a filesystem image to the device, so an example is also provided.hmjubeubjr)r}r(hlXU-Boot # mmc dev 0 U-Boot # mmc rescan U-Boot # mmc dev 1 U-Boot # fatload mmc 0 ${loadaddr} MLO U-Boot # mmc write ${loadaddr} 0x100 0x100 U-Boot # mmc write ${loadaddr} 0x200 0x100 U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # mmc write ${loadaddr} 0x300 0x400 U-Boot # fatload mmc 0 ${loadaddr} rootfs.ext4 U-Boot # mmc write ${loadaddr} 0x1000 ...rootfs.ext4 size in bytes divided by 512, in hex...hmjhwhh|juh~}r(hhh]h]h]h]h]uhM\hhh]rhXU-Boot # mmc dev 0 U-Boot # mmc rescan U-Boot # mmc dev 1 U-Boot # fatload mmc 0 ${loadaddr} MLO U-Boot # mmc write ${loadaddr} 0x100 0x100 U-Boot # mmc write ${loadaddr} 0x200 0x100 U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # mmc write ${loadaddr} 0x300 0x400 U-Boot # fatload mmc 0 ${loadaddr} rootfs.ext4 U-Boot # mmc write ${loadaddr} 0x1000 ...rootfs.ext4 size in bytes divided by 512, in hex...rr}r(hlUhmjubaubeubhn)r}r(hlUhmj hwhh|h}h~}r(h]h]h]h]rU"booting-linux-from-sd-card-or-emmcrah]rh8auhM]hhh]r(h)r}r(hlX"Booting Linux from SD card or eMMCrhmjhwhh|hh~}r(h]h]h]h]h]uhM]hhh]rhX"Booting Linux from SD card or eMMCrr}r(hljhmjubaubh)r}r(hlXWithin the default environment for each board that supports SD/MMC there is a boot command called **mmcboot** that will set the boot arguments correctly and start the kernel. In this case however, you must first run **loaduimagefat** or **loaduimage** to first load the kernel into memory. For the exact details of each use **printenv** on the **mmcboot**, **loaduimagefat** and **loaduimage** variables and then in turn **printenv** other sub-sections of the command. The most important variables here are **mmcroot** and **mmcrootfstype**.hmjhwhh|hh~}r(h]h]h]h]h]uhM_hhh]r(hXbWithin the default environment for each board that supports SD/MMC there is a boot command called rr}r(hlXbWithin the default environment for each board that supports SD/MMC there is a boot command called hmjubj)r}r(hlX **mmcboot**h~}r(h]h]h]h]h]uhmjh]rhXmmcbootrr}r(hlUhmjubah|j'ubhXk that will set the boot arguments correctly and start the kernel. In this case however, you must first run rr}r(hlXk that will set the boot arguments correctly and start the kernel. In this case however, you must first run hmjubj)r}r(hlX**loaduimagefat**h~}r(h]h]h]h]h]uhmjh]rhX loaduimagefatr r }r (hlUhmjubah|j'ubhX or r r }r(hlX or hmjubj)r}r(hlX**loaduimage**h~}r(h]h]h]h]h]uhmjh]rhX loaduimagerr}r(hlUhmjubah|j'ubhXI to first load the kernel into memory. For the exact details of each use rr}r(hlXI to first load the kernel into memory. For the exact details of each use hmjubj)r}r(hlX **printenv**h~}r(h]h]h]h]h]uhmjh]rhXprintenvrr}r(hlUhmjubah|j'ubhX on the r r!}r"(hlX on the hmjubj)r#}r$(hlX **mmcboot**h~}r%(h]h]h]h]h]uhmjh]r&hXmmcbootr'r(}r)(hlUhmj#ubah|j'ubhX, r*r+}r,(hlX, hmjubj)r-}r.(hlX**loaduimagefat**h~}r/(h]h]h]h]h]uhmjh]r0hX loaduimagefatr1r2}r3(hlUhmj-ubah|j'ubhX and r4r5}r6(hlX and hmjubj)r7}r8(hlX**loaduimage**h~}r9(h]h]h]h]h]uhmjh]r:hX loaduimager;r<}r=(hlUhmj7ubah|j'ubhX variables and then in turn r>r?}r@(hlX variables and then in turn hmjubj)rA}rB(hlX **printenv**h~}rC(h]h]h]h]h]uhmjh]rDhXprintenvrErF}rG(hlUhmjAubah|j'ubhXJ other sub-sections of the command. The most important variables here are rHrI}rJ(hlXJ other sub-sections of the command. The most important variables here are hmjubj)rK}rL(hlX **mmcroot**h~}rM(h]h]h]h]h]uhmjh]rNhXmmcrootrOrP}rQ(hlUhmjKubah|j'ubhX and rRrS}rT(hlX and hmjubj)rU}rV(hlX**mmcrootfstype**h~}rW(h]h]h]h]h]uhmjh]rXhX mmcrootfstyperYrZ}r[(hlUhmjUubah|j'ubhX.r\}r](hlX.hmjubeubeubhn)r^}r_(hlUhmj hwhh|h}h~}r`(h]h]h]h]raU/booting-mlo-and-u-boot-from-emmc-boot-partitionrbah]rchbauhMihhh]rd(h)re}rf(hlX/Booting MLO and u-boot from eMMC boot partitionrghmj^hwhh|hh~}rh(h]h]h]h]h]uhMihhh]rihX/Booting MLO and u-boot from eMMC boot partitionrjrk}rl(hljghmjeubaubj>)rm}rn(hlUhmj^hwNh|j[h~}ro(h]h]h]h]h]uhNhhh]rpcdocutils.nodes field_list rq)rr}rs(hlUh~}rt(h]h]h]h]h]uhmjmh]rucdocutils.nodes field rv)rw}rx(hlUhmjrhwhh|Ufieldryh~}rz(h]h]h]h]h]uhMjh]r{(cdocutils.nodes field_name r|)r}}r~(hlXnamerh~}r(h]h]h]h]h]uhmjwh]rhXnamerr}r(hljhmj}ubah|U field_namerubcdocutils.nodes field_body r)r}r(hlX0booting-mlo-and-u-boot-from-emmc-boot-partition h~}r(h]h]h]h]h]uhmjwh]rh)r}r(hlX/booting-mlo-and-u-boot-from-emmc-boot-partitionrhmjhwhh|hh~}r(h]h]h]h]h]uhMjh]rhX/booting-mlo-and-u-boot-from-emmc-boot-partitionrr}r(hljhmjubaubah|U field_bodyrubeubah|U field_listrubaubh)r}r(hlXThe dra7xx and am57xx processors support booting from the eMMC boot partition. The following commands load the boot images from network and write them into the boot0 partition.rhmj^hwhh|hh~}r(h]h]h]h]h]uhMlhhh]rhXThe dra7xx and am57xx processors support booting from the eMMC boot partition. The following commands load the boot images from network and write them into the boot0 partition.rr}r(hljhmjubaubjr)r}r(hlXU-boot # setenv autoload no U-boot # dhcp U-boot # mmc dev 1 1 U-boot # tftp ${loadaddr} dra7xx/MLO U-boot # mmc write ${loadaddr} 0x0 0x300 U-boot # tftp ${loadaddr} dra7xx/u-boot.img U-boot # mmc write ${loadaddr} 0x300 0x400hmj^hwhh|juh~}r(hhh]h]h]h]h]uhM{hhh]rhXU-boot # setenv autoload no U-boot # dhcp U-boot # mmc dev 1 1 U-boot # tftp ${loadaddr} dra7xx/MLO U-boot # mmc write ${loadaddr} 0x0 0x300 U-boot # tftp ${loadaddr} dra7xx/u-boot.img U-boot # mmc write ${loadaddr} 0x300 0x400rr}r(hlUhmjubaubh)r}r(hlXWe also need to configure the eMMC using the bootbus and partconf commands. The bootbus command sets the eMMC into dual data rate mode with a bus width of 8 to match with the bus configuration supported by the Boot ROM. The partconf command gives access to the boot0 partition during boot operation. Note that these configurations are limited to boot operation and the eMMC can be set to its highest speed mode once boot operation is complete. All these are non-volatile configurations that need to be done **once per eMMC/board** .rhmj^hwhh|hh~}r(h]h]h]h]h]uhMxhhh]r(hXWe also need to configure the eMMC using the bootbus and partconf commands. The bootbus command sets the eMMC into dual data rate mode with a bus width of 8 to match with the bus configuration supported by the Boot ROM. The partconf command gives access to the boot0 partition during boot operation. Note that these configurations are limited to boot operation and the eMMC can be set to its highest speed mode once boot operation is complete. All these are non-volatile configurations that need to be done rr}r(hlXWe also need to configure the eMMC using the bootbus and partconf commands. The bootbus command sets the eMMC into dual data rate mode with a bus width of 8 to match with the bus configuration supported by the Boot ROM. The partconf command gives access to the boot0 partition during boot operation. Note that these configurations are limited to boot operation and the eMMC can be set to its highest speed mode once boot operation is complete. All these are non-volatile configurations that need to be done hmjubj)r}r(hlX**once per eMMC/board**h~}r(h]h]h]h]h]uhmjh]rhXonce per eMMC/boardrr}r(hlUhmjubah|j'ubhX .rr}r(hlX .hmjubeubjr)r}r(hlXXU-boot # mmc bootbus 1 2 0 2 U-boot # mmc partconf 1 1 1 0 U-boot # mmc rst-function 1 1hmj^hwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXXU-boot # mmc bootbus 1 2 0 2 U-boot # mmc partconf 1 1 1 0 U-boot # mmc rst-function 1 1rr}r(hlUhmjubaubjC)r}r(hlUhmj^hwhh|jZh~}r(h]h]h]h]h]uhMhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubhn)r}r(hlUhmj hwhh|h}h~}r(h]h]h]h]rUEbooting-tiboot3-bin-tispl-bin-and-u-boot-img-from-emmc-boot-partitionrah]rh auhMhhh]r(h)r}r(hlXFBooting tiboot3.bin, tispl.bin and u-boot.img from eMMC boot partitionrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXFBooting tiboot3.bin, tispl.bin and u-boot.img from eMMC boot partitionrr}r(hljhmjubaubh)r}r(hlXThe K3 based processors support booting from the eMMC boot partition. The following commands can be used to download tiboot3.bin, tispl.bin and u-boot.img from an SD card and write them to the eMMC boot0 partition at respective addresses.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXThe K3 based processors support booting from the eMMC boot partition. The following commands can be used to download tiboot3.bin, tispl.bin and u-boot.img from an SD card and write them to the eMMC boot0 partition at respective addresses.rr}r(hljhmjubaubjr)r}r(hlXC=> mmc dev 0 1 => fatload mmc 1 ${loadaddr} tiboot3.bin => mmc write ${loadaddr} 0x0 0x400 => fatload mmc 1 ${loadaddr} tispl.bin => mmc write ${loadaddr} 0x400 0x1000 => fatload mmc 1 ${loadaddr} u-boot.img => mmc write ${loadaddr} 0x1400 0x2000 => fatload mmc 1 ${loadaddr} sysfw.itb => mmc write ${loadaddr} 0x3600 0x800hmjhwhh|juh~}r(jwjxXconsolehhh]h]h]jy}h]h]uhMhhh]rhXC=> mmc dev 0 1 => fatload mmc 1 ${loadaddr} tiboot3.bin => mmc write ${loadaddr} 0x0 0x400 => fatload mmc 1 ${loadaddr} tispl.bin => mmc write ${loadaddr} 0x400 0x1000 => fatload mmc 1 ${loadaddr} u-boot.img => mmc write ${loadaddr} 0x1400 0x2000 => fatload mmc 1 ${loadaddr} sysfw.itb => mmc write ${loadaddr} 0x3600 0x800rr}r(hlUhmjubaubh)r}r(hlXeTo give the ROM access to the boot partition, the following commands must be used for the first time:rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXeTo give the ROM access to the boot partition, the following commands must be used for the first time:rr}r(hljhmjubaubjr)r}r(hlX.=> mmc partconf 0 1 1 1 => mmc bootbus 0 2 0 0hmjhwhh|juh~}r(jwjxXconsolehhh]h]h]jy}h]h]uhMhhh]rhX.=> mmc partconf 0 1 1 1 => mmc bootbus 0 2 0 0rr}r(hlUhmjubaubjC)r}r(hlUhmjhwhh|jZh~}r(h]h]h]h]h]uhMhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubhn)r}r(hlUhmj hwhh|h}h~}r(h]h]h]h]rUbooting-linux-from-usb-storagerah]rhOauhMhhh]r(h)r}r(hlXBooting Linux from USB storagerhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXBooting Linux from USB storagerr}r(hljhmjubaubj>)r}r(hlUhmjhwNh|j[h~}r (h]h]h]h]h]uhNhhh]r jq)r }r (hlUh~}r (h]h]h]h]h]uhmjh]rjv)r}r(hlUhmj hwhh|jyh~}r(h]h]h]h]h]uhMh]r(j|)r}r(hlXnamerh~}r(h]h]h]h]h]uhmjh]rhXnamerr}r(hljhmjubah|jubj)r}r(hlXbooting-linux-from-usb-storage h~}r(h]h]h]h]h]uhmjh]rh)r}r (hlXbooting-linux-from-usb-storager!hmjhwhh|hh~}r"(h]h]h]h]h]uhMh]r#hXbooting-linux-from-usb-storager$r%}r&(hlj!hmjubaubah|jubeubah|jubaubh)r'}r((hlXTo load the Linux Kernel and rootfs from USB rather than SD/MMC card on AMx/DRA7x EVMs, if we assume that the USB device is partitioned the same way as an SD/MMC card is, we can utilize the **mmcboot** command to boot. To do this, perform the following steps:hmjhwhh|hh~}r)(h]h]h]h]h]uhMhhh]r*(hXTo load the Linux Kernel and rootfs from USB rather than SD/MMC card on AMx/DRA7x EVMs, if we assume that the USB device is partitioned the same way as an SD/MMC card is, we can utilize the r+r,}r-(hlXTo load the Linux Kernel and rootfs from USB rather than SD/MMC card on AMx/DRA7x EVMs, if we assume that the USB device is partitioned the same way as an SD/MMC card is, we can utilize the hmj'ubj)r.}r/(hlX **mmcboot**h~}r0(h]h]h]h]h]uhmj'h]r1hXmmcbootr2r3}r4(hlUhmj.ubah|j'ubhX: command to boot. To do this, perform the following steps:r5r6}r7(hlX: command to boot. To do this, perform the following steps:hmj'ubeubjr)r8}r9(hlXeU-Boot # usb start U-Boot # setenv mmcroot /dev/sda2 ro U-Boot # run mmcargs U-Boot # run bootcmd_usbhmjhwhh|juh~}r:(hhh]h]h]h]h]uhMhhh]r;hXeU-Boot # usb start U-Boot # setenv mmcroot /dev/sda2 ro U-Boot # run mmcargs U-Boot # run bootcmd_usbr<r=}r>(hlUhmj8ubaubh)r?}r@(hlXsOn K2H/K/E/L EVMs, the USB drivers in Kernel needs to be built-in (default modules). The configuration changes are:rAhmjhwhh|hh~}rB(h]h]h]h]h]uhMhhh]rChXsOn K2H/K/E/L EVMs, the USB drivers in Kernel needs to be built-in (default modules). The configuration changes are:rDrE}rF(hljAhmj?ubaubjr)rG}rH(hlX CONFIG_USB=y CONFIG_USB_XHCI_HCD=y CONFIG_USB_XHCI_PCI=y CONFIG_USB_XHCI_PLATFORM=y CONFIG_USB_STORAGE=y CONFIG_USB_DWC3=y CONFIG_USB_DWC3_HOST=y CONFIG_USB_DWC3_KEYSTONE=y CONFIG_EXTCON=y CONFIG_EXTCON_USB_GPIO=y CONFIG_SCSI_MOD=y CONFIG_SCSI=y CONFIG_BLK_DEV_SD=yhmjhwhh|juh~}rI(hhh]h]h]h]h]uhMhhh]rJhX CONFIG_USB=y CONFIG_USB_XHCI_HCD=y CONFIG_USB_XHCI_PCI=y CONFIG_USB_XHCI_PLATFORM=y CONFIG_USB_STORAGE=y CONFIG_USB_DWC3=y CONFIG_USB_DWC3_HOST=y CONFIG_USB_DWC3_KEYSTONE=y CONFIG_EXTCON=y CONFIG_EXTCON_USB_GPIO=y CONFIG_SCSI_MOD=y CONFIG_SCSI=y CONFIG_BLK_DEV_SD=yrKrL}rM(hlUhmjGubaubh)rN}rO(hlXThe USB should have boot partition of FAT32 format, and rootfs partition of EXT4 format. The boot partition must contain the following images:rPhmjhwhh|hh~}rQ(h]h]h]h]h]uhMhhh]rRhXThe USB should have boot partition of FAT32 format, and rootfs partition of EXT4 format. The boot partition must contain the following images:rSrT}rU(hljPhmjNubaubjr)rV}rW(hlXmkeystone--evm.dtb skern-.bin k2-fw-initrd.cpio.gz zImage where =k2hk, k2e, k2lhmjhwhh|juh~}rX(hhh]h]h]h]h]uhMhhh]rYhXmkeystone--evm.dtb skern-.bin k2-fw-initrd.cpio.gz zImage where =k2hk, k2e, k2lrZr[}r\(hlUhmjVubaubh)r]}r^(hlXJThe rootfs partition contains the filesystem from ProcSDK release package.r_hmjhwhh|hh~}r`(h]h]h]h]h]uhMhhh]rahXJThe rootfs partition contains the filesystem from ProcSDK release package.rbrc}rd(hlj_hmj]ubaubjr)re}rf(hlX# mkdir /mnt/temp # mount -t ext4 /dev/sdb2 /mnt/temp # cd /mnt/temp # tar xvf /filesyste/tisdk-server-rootfs-image-k2hk-evm.tar.xz # cd /mnt # umount temphmjhwhh|juh~}rg(hhh]h]h]h]h]uhMhhh]rhhX# mkdir /mnt/temp # mount -t ext4 /dev/sdb2 /mnt/temp # cd /mnt/temp # tar xvf /filesyste/tisdk-server-rootfs-image-k2hk-evm.tar.xz # cd /mnt # umount temprirj}rk(hlUhmjeubaubh)rl}rm(hlX2Set up the following u-boot environment variables:rnhmjhwhh|hh~}ro(h]h]h]h]h]uhMhhh]rphX2Set up the following u-boot environment variables:rqrr}rs(hljnhmjlubaubjr)rt}ru(hlXsetenv args_all 'setenv bootargs console=ttyS0,115200n8 rootwait' setenv args_usb 'setenv bootargs ${bootargs} rootdelay=3 rootfstype=ext4 root=/dev/sda2 rw' setenv get_fdt_usb 'fatload usb 0:1 ${fdtaddr} ${name_fdt}' setenv get_kern_usb 'fatload usb 0:1 ${loadaddr} ${name_kern}' setenv get_mon_usb 'fatload usb 0:1 ${addr_mon} ${name_mon}' setenv init_fw_rd_usb 'fatload usb 0:1 ${rdaddr} ${name_fw_rd}; setenv filesize ; run set_rd_spec' setenv init_usb 'usb start; run args_all args_usb' setenv boot usb saveenv boothmjhwhh|juh~}rv(hhh]h]h]h]h]uhMhhh]rwhXsetenv args_all 'setenv bootargs console=ttyS0,115200n8 rootwait' setenv args_usb 'setenv bootargs ${bootargs} rootdelay=3 rootfstype=ext4 root=/dev/sda2 rw' setenv get_fdt_usb 'fatload usb 0:1 ${fdtaddr} ${name_fdt}' setenv get_kern_usb 'fatload usb 0:1 ${loadaddr} ${name_kern}' setenv get_mon_usb 'fatload usb 0:1 ${addr_mon} ${name_mon}' setenv init_fw_rd_usb 'fatload usb 0:1 ${rdaddr} ${name_fw_rd}; setenv filesize ; run set_rd_spec' setenv init_usb 'usb start; run args_all args_usb' setenv boot usb saveenv bootrxry}rz(hlUhmjtubaubh)r{}r|(hlXZ**Note:**: must be at least the hex size of the k2-fw-initrd.cpio.gz file size.r}hmjhwhh|hh~}r~(h]h]h]h]h]uhMhhh]r(j)r}r(hlX **Note:**h~}r(h]h]h]h]h]uhmj{h]rhXNote:rr}r(hlUhmjubah|j'ubhXP: must be at least the hex size of the k2-fw-initrd.cpio.gz file size.rr}r(hlXQ: must be at least the hex size of the k2-fw-initrd.cpio.gz file size.hmj{ubeubh)r}r(hlUhmjhwhh|hh~}r(hX#CONFIG_part_family in ('J7_family')h]h]h]h]h]uhMhhh]r(jC)r}r(hlX'Enabling USB 3.0 host port on J721e EVMrhmjhwhh|jGh~}r(h]rUj721e-evm-usb-30-hostrah]h]h]h]rh auhNhhh]rhX'Enabling USB 3.0 host port on J721e EVMrr}r(hljhmjubaubj)r}r(hlXuJ721e SoC does not support booting from USB mass storage devices. But can be used as storage device at U-Boot prompt.rhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXuJ721e SoC does not support booting from USB mass storage devices. But can be used as storage device at U-Boot prompt.rr}r(hljhmjubaubaubh)r}r(hlXiUSB0 instance on J721e base board is connected to TypeC port that can be used both as host port and device port. By default, USB0 is port is configured to be in **peripheral mode**. Since U-Boot does not support dynamic switching of USB roles, below DT fragment needs to be applied and U-Boot image needs to be rebuilt to make USB0 port to be USB 3.0 host port.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXUSB0 instance on J721e base board is connected to TypeC port that can be used both as host port and device port. By default, USB0 is port is configured to be in rr}r(hlXUSB0 instance on J721e base board is connected to TypeC port that can be used both as host port and device port. By default, USB0 is port is configured to be in hmjubj)r}r(hlX**peripheral mode**h~}r(h]h]h]h]h]uhmjh]rhXperipheral moderr}r(hlUhmjubah|j'ubhX. Since U-Boot does not support dynamic switching of USB roles, below DT fragment needs to be applied and U-Boot image needs to be rebuilt to make USB0 port to be USB 3.0 host port.rr}r(hlX. Since U-Boot does not support dynamic switching of USB roles, below DT fragment needs to be applied and U-Boot image needs to be rebuilt to make USB0 port to be USB 3.0 host port.hmjubeubjr)r}r(hlXdiff --git a/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi b/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi index 50effb4812b2..28986c4d2c2a 100644 --- a/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi +++ b/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi @@ -184,11 +184,10 @@ &usbss0 { u-boot,dm-spl; - ti,usb2-only; }; &usb0 { - dr_mode = "peripheral"; + dr_mode = "host"; u-boot,dm-spl; };hmjhwhh|juh~}r(hhh]h]h]h]h]uhM hhh]rhXdiff --git a/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi b/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi index 50effb4812b2..28986c4d2c2a 100644 --- a/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi +++ b/arch/arm/dts/k3-j721e-common-proc-board-u-boot.dtsi @@ -184,11 +184,10 @@ &usbss0 { u-boot,dm-spl; - ti,usb2-only; }; &usb0 { - dr_mode = "peripheral"; + dr_mode = "host"; u-boot,dm-spl; };rr}r(hlUhmjubaubeubeubhn)r}r(hlUhmj hwhh|h}h~}r(h]h]h]h]rU9booting-from-sd-emmc-from-spl-single-stage-or-falcon-moderah]rhauhMhhh]r(h)r}r(hlX;Booting from SD/eMMC from SPL (Single stage or Falcon mode)rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX;Booting from SD/eMMC from SPL (Single stage or Falcon mode)rr}r(hljhmjubaubh)r}r(hlX*In this boot mode SPL (first stage bootloader) directly boots the Linux kernel. Optionally, in order to enter into U-Boot, reset the board while keeping 'c' key on the serial terminal pressed. When falcon mode is enabled in U-Boot build (usually enabled by default), ``MLO`` checks if there is a valid ``uImage`` present at a defined offset. If ``uImage`` is present, it is booted directly. If valid ``uImage`` is not found, ``MLO`` falls back to checking if the ``uImage`` exists in a FAT partition. If it fails, it falls back to booting ``u-boot.img``.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hX In this boot mode SPL (first stage bootloader) directly boots the Linux kernel. Optionally, in order to enter into U-Boot, reset the board while keeping 'c' key on the serial terminal pressed. When falcon mode is enabled in U-Boot build (usually enabled by default), rr}r(hlX In this boot mode SPL (first stage bootloader) directly boots the Linux kernel. Optionally, in order to enter into U-Boot, reset the board while keeping 'c' key on the serial terminal pressed. When falcon mode is enabled in U-Boot build (usually enabled by default), hmjubj)r}r(hlX``MLO``h~}r(h]h]h]h]h]uhmjh]rhXMLOrr}r(hlUhmjubah|jubhX checks if there is a valid rr}r(hlX checks if there is a valid hmjubj)r}r(hlX ``uImage``h~}r(h]h]h]h]h]uhmjh]rhXuImagerr}r(hlUhmjubah|jubhX! present at a defined offset. If rr}r(hlX! present at a defined offset. If hmjubj)r}r(hlX ``uImage``h~}r(h]h]h]h]h]uhmjh]rhXuImagerr}r(hlUhmjubah|jubhX- is present, it is booted directly. If valid rr}r(hlX- is present, it is booted directly. If valid hmjubj)r}r(hlX ``uImage``h~}r(h]h]h]h]h]uhmjh]rhXuImagerr}r(hlUhmjubah|jubhX is not found, rr}r(hlX is not found, hmjubj)r}r(hlX``MLO``h~}r(h]h]h]h]h]uhmjh]rhXMLOrr}r(hlUhmjubah|jubhX falls back to checking if the rr}r(hlX falls back to checking if the hmjubj)r}r(hlX ``uImage``h~}r(h]h]h]h]h]uhmjh]rhXuImager r }r (hlUhmjubah|jubhXB exists in a FAT partition. If it fails, it falls back to booting r r }r(hlXB exists in a FAT partition. If it fails, it falls back to booting hmjubj)r}r(hlX``u-boot.img``h~}r(h]h]h]h]h]uhmjh]rhX u-boot.imgrr}r(hlUhmjubah|jubhX.r}r(hlX.hmjubeubh)r}r(hlXThe falcon boot uses ``uImage``. To build the kernel ``uImage``, you will need to keep the U-Boot tool ``mkimage`` in your ``$PATH``hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXThe falcon boot uses rr}r(hlXThe falcon boot uses hmjubj)r}r (hlX ``uImage``h~}r!(h]h]h]h]h]uhmjh]r"hXuImager#r$}r%(hlUhmjubah|jubhX. To build the kernel r&r'}r((hlX. To build the kernel hmjubj)r)}r*(hlX ``uImage``h~}r+(h]h]h]h]h]uhmjh]r,hXuImager-r.}r/(hlUhmj)ubah|jubhX(, you will need to keep the U-Boot tool r0r1}r2(hlX(, you will need to keep the U-Boot tool hmjubj)r3}r4(hlX ``mkimage``h~}r5(h]h]h]h]h]uhmjh]r6hXmkimager7r8}r9(hlUhmj3ubah|jubhX in your r:r;}r<(hlX in your hmjubj)r=}r>(hlX ``$PATH``h~}r?(h]h]h]h]h]uhmjh]r@hX$PATHrArB}rC(hlUhmj=ubah|jubeubjr)rD}rE(hlX,# make uImage modules dtbs LOADADDR=80008000hmjhwhh|juh~}rF(hhh]h]h]h]h]uhM+hhh]rGhX,# make uImage modules dtbs LOADADDR=80008000rHrI}rJ(hlUhmjDubaubh)rK}rL(hlXIf kernel is not build with ``CONFIG_CMDLINE`` to set correct bootargs, then add the needed ``bootargs`` in ``chosen`` node in DTB file, using ``fdtput`` host utility. For example, for DRA74x EVM:hmjhwhh|hh~}rM(h]h]h]h]h]uhM"hhh]rN(hXIf kernel is not build with rOrP}rQ(hlXIf kernel is not build with hmjKubj)rR}rS(hlX``CONFIG_CMDLINE``h~}rT(h]h]h]h]h]uhmjKh]rUhXCONFIG_CMDLINErVrW}rX(hlUhmjRubah|jubhX. to set correct bootargs, then add the needed rYrZ}r[(hlX. to set correct bootargs, then add the needed hmjKubj)r\}r](hlX ``bootargs``h~}r^(h]h]h]h]h]uhmjKh]r_hXbootargsr`ra}rb(hlUhmj\ubah|jubhX in rcrd}re(hlX in hmjKubj)rf}rg(hlX ``chosen``h~}rh(h]h]h]h]h]uhmjKh]rihXchosenrjrk}rl(hlUhmjfubah|jubhX node in DTB file, using rmrn}ro(hlX node in DTB file, using hmjKubj)rp}rq(hlX ``fdtput``h~}rr(h]h]h]h]h]uhmjKh]rshXfdtputrtru}rv(hlUhmjpubah|jubhX+ host utility. For example, for DRA74x EVM:rwrx}ry(hlX+ host utility. For example, for DRA74x EVM:hmjKubeubjr)rz}r{(hlXi# fdtput -v -t s arch/arm/boot/dts/dra7-evm.dtb "/chosen" bootargs "console=ttyO0,115200n8 root="hmjhwhh|juh~}r|(hhh]h]h]h]h]uhM3hhh]r}hXi# fdtput -v -t s arch/arm/boot/dts/dra7-evm.dtb "/chosen" bootargs "console=ttyO0,115200n8 root="r~r}r(hlUhmjzubaubh)r}r(hlX``MLO``, ``u-boot.img`` (optional), DTB, ``uImage`` are all stored on the same medium, either the SD or the eMMC. There are two ways to store the binaries in the SD (resp. eMMC):hmjhwhh|hh~}r(h]h]h]h]h]uhM*hhh]r(j)r}r(hlX``MLO``h~}r(h]h]h]h]h]uhmjh]rhXMLOrr}r(hlUhmjubah|jubhX, rr}r(hlX, hmjubj)r}r(hlX``u-boot.img``h~}r(h]h]h]h]h]uhmjh]rhX u-boot.imgrr}r(hlUhmjubah|jubhX (optional), DTB, rr}r(hlX (optional), DTB, hmjubj)r}r(hlX ``uImage``h~}r(h]h]h]h]h]uhmjh]rhXuImagerr}r(hlUhmjubah|jubhX are all stored on the same medium, either the SD or the eMMC. There are two ways to store the binaries in the SD (resp. eMMC):rr}r(hlX are all stored on the same medium, either the SD or the eMMC. There are two ways to store the binaries in the SD (resp. eMMC):hmjubeubjr)r}r(hlXn* raw: binaries are stored at fixed offset in the medium * fat: binaries are stored as file in a FAT partitionhmjhwhh|juh~}r(hhh]h]h]h]h]uhM;hhh]rhXn* raw: binaries are stored at fixed offset in the medium * fat: binaries are stored as file in a FAT partitionrr}r(hlUhmjubaubh)r}r(hlXQTo flash binaries to SD or eMMC, you can use DFU. For SD boot, from u-boot promptrhmjhwhh|hh~}r(h]h]h]h]h]uhM3hhh]rhXQTo flash binaries to SD or eMMC, you can use DFU. For SD boot, from u-boot promptrr}r(hljhmjubaubjr)r}r(hlXG=> env default -a; setenv dfu_alt_info ${dfu_alt_info_mmc}; dfu 0 mmc 0hmjhwhh|juh~}r(hhh]h]h]h]h]uhMChhh]rhXG=> env default -a; setenv dfu_alt_info ${dfu_alt_info_mmc}; dfu 0 mmc 0rr}r(hlUhmjubaubh)r}r(hlX!For eMMC boot, from u-boot promptrhmjhwhh|hh~}r(h]h]h]h]h]uhM:hhh]rhX!For eMMC boot, from u-boot promptrr}r(hljhmjubaubjr)r}r(hlXH=> env default -a; setenv dfu_alt_info ${dfu_alt_info_emmc}; dfu 0 mmc 1hmjhwhh|juh~}r(hhh]h]h]h]h]uhMIhhh]rhXH=> env default -a; setenv dfu_alt_info ${dfu_alt_info_emmc}; dfu 0 mmc 1rr}r(hlUhmjubaubh)r}r(hlXNote: On boards like AM57x GP EVM or BeagleBoard x15, where the second USB instance is used as USB client, replace "dfu 0 mmc X" with "dfu 1 mmc X"rhmjhwhh|hh~}r(h]h]h]h]h]uhM@hhh]rhXNote: On boards like AM57x GP EVM or BeagleBoard x15, where the second USB instance is used as USB client, replace "dfu 0 mmc X" with "dfu 1 mmc X"rr}r(hljhmjubaubh)r}r(hlX"On the host side: binaries in FAT:rhmjhwhh|hh~}r(h]h]h]h]h]uhMDhhh]rhX"On the host side: binaries in FAT:rr}r(hljhmjubaubjr)r}r(hlX$ sudo dfu-util -D MLO -a MLO $ sudo dfu-util -D u-boot.img -a u-boot.img $ sudo dfu-util -D dra7-evm.dtb -a spl-os-args $ sudo dfu-util -D uImage -a spl-os-imagehmjhwhh|juh~}r(hhh]h]h]h]h]uhMShhh]rhX$ sudo dfu-util -D MLO -a MLO $ sudo dfu-util -D u-boot.img -a u-boot.img $ sudo dfu-util -D dra7-evm.dtb -a spl-os-args $ sudo dfu-util -D uImage -a spl-os-imagerr}r(hlUhmjubaubh)r}r(hlX raw binaries:rhmjhwhh|hh~}r(h]h]h]h]h]uhMMhhh]rhX raw binaries:rr}r(hljhmjubaubjr)r}r(hlX$ sudo dfu-util -D MLO -a MLO.raw $ sudo dfu-util -D u-boot.img -a u-boot.img.raw $ sudo dfu-util -D dra7-evm.dtb -a spl-os-args.raw $ sudo dfu-util -D uImage -a spl-os-image.rawhmjhwhh|juh~}r(hhh]h]h]h]h]uhM\hhh]rhX$ sudo dfu-util -D MLO -a MLO.raw $ sudo dfu-util -D u-boot.img -a u-boot.img.raw $ sudo dfu-util -D dra7-evm.dtb -a spl-os-args.raw $ sudo dfu-util -D uImage -a spl-os-image.rawrr}r(hlUhmjubaubh)r}r(hlX If the binaries are files in a fat partition, you need to specify their name if they differ from the default values ("uImage" and "args"). Note that DFU uses the names "spl-os-image" and "spl-os-args", so this step is required in the case of DFU. From u-boot promptrhmjhwhh|hh~}r(h]h]h]h]h]uhMVhhh]rhX If the binaries are files in a fat partition, you need to specify their name if they differ from the default values ("uImage" and "args"). Note that DFU uses the names "spl-os-image" and "spl-os-args", so this step is required in the case of DFU. From u-boot promptrr}r(hljhmjubaubjr)r}r(hlXZ=> setenv falcon_image_file spl-os-image => setenv falcon_args_file spl-os-args => saveenvhmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhhh]rhXZ=> setenv falcon_image_file spl-os-image => setenv falcon_args_file spl-os-args => saveenvrr}r(hlUhmjubaubh)r}r(hlX@Set the environment variable "boot\_os" to 1. From u-boot promptrhmjhwhh|hh~}r(h]h]h]h]h]uhMahhh]rhX?Set the environment variable "boot_os" to 1. From u-boot promptrr}r(hlX@Set the environment variable "boot\_os" to 1. From u-boot prompthmjubaubjr)r}r(hlX=> setenv boot_os 1 => saveenvhmjhwhh|juh~}r(hhh]h]h]h]h]uhMphhh]rhX=> setenv boot_os 1 => saveenvr r }r (hlUhmjubaubh)r }r (hlXSet the board boot from SD (or eMMC respectively) and reset the EVM. The SPL directly boots the kernel image from SD (or eMMC).rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhhh]rhXSet the board boot from SD (or eMMC respectively) and reset the EVM. The SPL directly boots the kernel image from SD (or eMMC).rr}r(hljhmj ubaubjC)r}r(hlUhmjhwhh|jZh~}r(h]h]h]h]h]uhMkhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubeubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUspirah]r hJauhMnhhh]r!(h)r"}r#(hlXSPIr$hmjhwhh|hh~}r%(h]h]h]h]h]uhMnhhh]r&hXSPIr'r(}r)(hlj$hmj"ubaubh)r*}r+(hlUhmjhwhh|hh~}r,(hX#CONFIG_part_family in ('J7_family')h]h]h]h]h]uhMphhh]r-j)r.}r/(hlXHSPI is not supported on J721E platform (not be confused with QSPI/OSPI).r0hmj*hwhh|jh~}r1(h]h]h]h]h]uhNhhh]r2h)r3}r4(hlj0hmj.hwhh|hh~}r5(h]h]h]h]h]uhMsh]r6hXHSPI is not supported on J721E platform (not be confused with QSPI/OSPI).r7r8}r9(hlj0hmj3ubaubaubaubh)r:}r;(hlXaThis section documents how to write files to the SPI device and use it to load and then boot the Linux Kernel using a root filesystem also found on SPI. At this time, no special builds of U-Boot are required to perform these operations on the supported hardware. The table below however, lists builds that will also use the SPI flash for the environment instead of the default, which typically is NAND in AM57x and DRA7x EVMs, but in Keystone-2 EVMs, it is only NOR. Finally, for simplicity we assume the files are being loaded from an SD card. Using the network interface (if applicable) is documented above.r<hmjhwhh|hh~}r=(h]h]h]h]h]uhMuhhh]r>hXaThis section documents how to write files to the SPI device and use it to load and then boot the Linux Kernel using a root filesystem also found on SPI. At this time, no special builds of U-Boot are required to perform these operations on the supported hardware. The table below however, lists builds that will also use the SPI flash for the environment instead of the default, which typically is NAND in AM57x and DRA7x EVMs, but in Keystone-2 EVMs, it is only NOR. Finally, for simplicity we assume the files are being loaded from an SD card. Using the network interface (if applicable) is documented above.r?r@}rA(hlj<hmj:ubaubhn)rB}rC(hlUhmjhwhh|h}h~}rD(h]h]h]h]rEUwriting-to-spi-from-u-bootrFah]rGh#auhMhhh]rH(h)rI}rJ(hlXWriting to SPI from U-BootrKhmjBhwhh|hh~}rL(h]h]h]h]h]uhMhhh]rMhXWriting to SPI from U-BootrNrO}rP(hljKhmjIubaubh)rQ}rR(hlX#Note for AM57x and DRA7x platforms:rShmjBhwhh|hh~}rT(h]h]h]h]h]uhMhhh]rUhX#Note for AM57x and DRA7x platforms:rVrW}rX(hljShmjQubaubj#)rY}rZ(hlUhmjBhwhh|j&h~}r[(j(X-h]h]h]h]h]uhMhhh]r\(j )r]}r^(hlX`From the U-Boot build, the **MLO.byteswap** and **u-boot.img** files are the ones to be written.hmjYhwhh|jh~}r_(h]h]h]h]h]uhNhhh]r`h)ra}rb(hlX`From the U-Boot build, the **MLO.byteswap** and **u-boot.img** files are the ones to be written.hmj]hwhh|hh~}rc(h]h]h]h]h]uhMh]rd(hXFrom the U-Boot build, the rerf}rg(hlXFrom the U-Boot build, the hmjaubj)rh}ri(hlX**MLO.byteswap**h~}rj(h]h]h]h]h]uhmjah]rkhX MLO.byteswaprlrm}rn(hlUhmjhubah|j'ubhX and rorp}rq(hlX and hmjaubj)rr}rs(hlX**u-boot.img**h~}rt(h]h]h]h]h]uhmjah]ruhX u-boot.imgrvrw}rx(hlUhmjrubah|j'ubhX" files are the ones to be written.ryrz}r{(hlX" files are the ones to be written.hmjaubeubaubj )r|}r}(hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.hmjYhwhh|jh~}r~(h]h]h]h]h]uhNhhh]rh)r}r(hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.rhmj|hwhh|hh~}r(h]h]h]h]h]uhMh]rhXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.rr}r(hljhmjubaubaubj )r}r(hlXtAt this time the SPI mtd partition map has not yet been updated to include an example location for the device tree. hmjYhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXsAt this time the SPI mtd partition map has not yet been updated to include an example location for the device tree.rhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXsAt this time the SPI mtd partition map has not yet been updated to include an example location for the device tree.rr}r(hljhmjubaubaubeubjr)r}r(hlXU-Boot # mmc rescan U-Boot # sf probe 0 U-Boot # sf erase 0 +80000 U-Boot # fatload mmc 0 ${loadaddr} MLO.byteswap U-Boot # sf write ${loadaddr} 0 ${filesize} U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # sf write ${loadaddr} 0x20000 ${filesize} U-Boot # sf erase 80000 +${spiimgsize} U-Boot # fatload mmc 0 ${loadaddr} zImage U-Boot # sf write ${loadaddr} ${spisrcaddr} ${filesize}hmjBhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXU-Boot # mmc rescan U-Boot # sf probe 0 U-Boot # sf erase 0 +80000 U-Boot # fatload mmc 0 ${loadaddr} MLO.byteswap U-Boot # sf write ${loadaddr} 0 ${filesize} U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # sf write ${loadaddr} 0x20000 ${filesize} U-Boot # sf erase 80000 +${spiimgsize} U-Boot # fatload mmc 0 ${loadaddr} zImage U-Boot # sf write ${loadaddr} ${spisrcaddr} ${filesize}rr}r(hlUhmjubaubh)r}r(hlX,Note for Keystone-2 (K2H/K/E/L/G) platforms:rhmjBhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX,Note for Keystone-2 (K2H/K/E/L/G) platforms:rr}r(hljhmjubaubj#)r}r(hlUhmjBhwhh|j&h~}r(j(X-h]h]h]h]h]uhMhhh]r(j )r}r(hlXLFrom the U-Boot build, the **u-boot-spi.gph** file is the one to be written.hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXLFrom the U-Boot build, the **u-boot-spi.gph** file is the one to be written.hmjhwhh|hh~}r(h]h]h]h]h]uhMh]r(hXFrom the U-Boot build, the rr}r(hlXFrom the U-Boot build, the hmjubj)r}r(hlX**u-boot-spi.gph**h~}r(h]h]h]h]h]uhmjh]rhXu-boot-spi.gphrr}r(hlUhmjubah|j'ubhX file is the one to be written.rr}r(hlX file is the one to be written.hmjubeubaubj )r}r(hlX@We load the file from a tftp server via netowrk in this example.rhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX@We load the file from a tftp server via netowrk in this example.rr}r(hljhmjubaubaubj )r}r(hlX@The series commands burns the u-boot image to the SPI NOR flash hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlX?The series commands burns the u-boot image to the SPI NOR flashrhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX?The series commands burns the u-boot image to the SPI NOR flashrr}r(hljhmjubaubaubeubjr)r}r(hlXU-Boot # env default -f -a U-Boot # setenv serverip U-Boot # setenv tftp_root U-Boot # setenv name_uboot u-boot-spi.gph U-Boot # run get_uboot_net U-Boot # run burn_uboot_spihmjBhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXU-Boot # env default -f -a U-Boot # setenv serverip U-Boot # setenv tftp_root U-Boot # setenv name_uboot u-boot-spi.gph U-Boot # run get_uboot_net U-Boot # run burn_uboot_spirr}r(hlUhmjubaubjC)r}r(hlUhmjBhwhh|jZh~}r(h]h]h]h]h]uhMhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rUbooting-from-spirah]rhRauhMhhh]r(h)r}r(hlXBooting from SPIrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXBooting from SPIrr}r(hljhmjubaubh)r}r(hlXWithin the default environment for each board that supports SPI there is a boot command called **spiboot** that will automatically load the kernel and boot. For the exact details of each use **printenv** on the **spiboot** variable and then in turn **printenv** other sub-sections of the command. The most important variables here are **spiroot** and **spirootfstype**. For Keystone-2 platforms, it is configured to be **ARM SPI** boot mode using SW1 dip switch setting. Please refer to the Hardware Setup of each Keystone-2 EVM.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hX_Within the default environment for each board that supports SPI there is a boot command called rr}r(hlX_Within the default environment for each board that supports SPI there is a boot command called hmjubj)r}r(hlX **spiboot**h~}r(h]h]h]h]h]uhmjh]rhXspibootrr}r(hlUhmjubah|j'ubhXU that will automatically load the kernel and boot. For the exact details of each use rr}r(hlXU that will automatically load the kernel and boot. For the exact details of each use hmjubj)r}r(hlX **printenv**h~}r(h]h]h]h]h]uhmjh]rhXprintenvrr}r(hlUhmjubah|j'ubhX on the r r }r (hlX on the hmjubj)r }r (hlX **spiboot**h~}r(h]h]h]h]h]uhmjh]rhXspibootrr}r(hlUhmj ubah|j'ubhX variable and then in turn rr}r(hlX variable and then in turn hmjubj)r}r(hlX **printenv**h~}r(h]h]h]h]h]uhmjh]rhXprintenvrr}r(hlUhmjubah|j'ubhXJ other sub-sections of the command. The most important variables here are rr}r(hlXJ other sub-sections of the command. The most important variables here are hmjubj)r }r!(hlX **spiroot**h~}r"(h]h]h]h]h]uhmjh]r#hXspirootr$r%}r&(hlUhmj ubah|j'ubhX and r'r(}r)(hlX and hmjubj)r*}r+(hlX**spirootfstype**h~}r,(h]h]h]h]h]uhmjh]r-hX spirootfstyper.r/}r0(hlUhmj*ubah|j'ubhX3. For Keystone-2 platforms, it is configured to be r1r2}r3(hlX3. For Keystone-2 platforms, it is configured to be hmjubj)r4}r5(hlX **ARM SPI**h~}r6(h]h]h]h]h]uhmjh]r7hXARM SPIr8r9}r:(hlUhmj4ubah|j'ubhXc boot mode using SW1 dip switch setting. Please refer to the Hardware Setup of each Keystone-2 EVM.r;r<}r=(hlXc boot mode using SW1 dip switch setting. Please refer to the Hardware Setup of each Keystone-2 EVM.hmjubeubjC)r>}r?(hlUhmjhwhh|jZh~}r@(h]h]h]h]h]uhMhhh]rAjH)rB}rC(hlUjLKhmj>hwhh|hh~}rD(h]h]h]h]h]uhKhhh]ubaubeubeubhn)rE}rF(hlUhmhshwhh|h}h~}rG(h]h]h]h]rHU ospi-qspirIah]rJhFauhMhhh]rK(h)rL}rM(hlX OSPI/QSPIrNhmjEhwhh|hh~}rO(h]h]h]h]h]uhMhhh]rPhX OSPI/QSPIrQrR}rS(hljNhmjLubaubh)rT}rU(hlXLOSPI/QSPI is a serial peripheral interface like SPI the major difference being the support for Octal/Quad read, uses 8/4 data lines for read compared to 2 lines used by the traditional SPI. This section documents how to write files to the QSPI device and use it to load and then boot the Linux Kernel using a root filesystem also found on QSPI. At this time, no special builds of U-Boot are required to perform these operations on the supported hardware. For simplicity we assume the files are being loaded from an SD card. Using the network interface (if applicable) is documented above.rVhmjEhwhh|hh~}rW(h]h]h]h]h]uhMhhh]rXhXLOSPI/QSPI is a serial peripheral interface like SPI the major difference being the support for Octal/Quad read, uses 8/4 data lines for read compared to 2 lines used by the traditional SPI. This section documents how to write files to the QSPI device and use it to load and then boot the Linux Kernel using a root filesystem also found on QSPI. At this time, no special builds of U-Boot are required to perform these operations on the supported hardware. For simplicity we assume the files are being loaded from an SD card. Using the network interface (if applicable) is documented above.rYrZ}r[(hljVhmjTubaubhn)r\}r](hlUhmjEhwhh|h}h~}r^(h]h]h]h]r_Uam654-j721e-supportr`ah]rah\auhMhhh]rb(h)rc}rd(hlXAM654/J721E Supportrehmj\hwhh|hh~}rf(h]h]h]h]h]uhMhhh]rghXAM654/J721E Supportrhri}rj(hljehmjcubaubh)rk}rl(hlX/ROM supports booting from OSPI from offset 0x0.rmhmj\hwhh|hh~}rn(h]h]h]h]h]uhMhhh]rohX/ROM supports booting from OSPI from offset 0x0.rprq}rr(hljmhmjkubaubh)rs}rt(hlX**Flashing Images to OSPI**ruhmj\hwhh|hh~}rv(h]h]h]h]h]uhMhhh]rwj)rx}ry(hljuh~}rz(h]h]h]h]h]uhmjsh]r{hXFlashing Images to OSPIr|r}}r~(hlUhmjxubah|j'ubaubh)r}r(hlXBelow commands can be used to download tiboot3.bin, tispl.bin and u-boot.img over tftp and then flash it to OSPI at respective addresses.rhmj\hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXBelow commands can be used to download tiboot3.bin, tispl.bin and u-boot.img over tftp and then flash it to OSPI at respective addresses.rr}r(hljhmjubaubjr)r}r(hlX(=> sf probe => tftp ${loadaddr} tiboot3.bin => sf update $loadaddr 0x0 $filesize => tftp ${loadaddr} tispl.bin => sf update $loadaddr 0x80000 $filesize => tftp ${loadaddr} u-boot.img => sf update $loadaddr 0x280000 $filesize => tftp ${loadaddr} sysfw.itb => sf update $loadaddr 0x6C0000 $filesizehmj\hwhh|juh~}r(jwjxXconsolehhh]h]h]jy}h]h]uhMhhh]rhX(=> sf probe => tftp ${loadaddr} tiboot3.bin => sf update $loadaddr 0x0 $filesize => tftp ${loadaddr} tispl.bin => sf update $loadaddr 0x80000 $filesize => tftp ${loadaddr} u-boot.img => sf update $loadaddr 0x280000 $filesize => tftp ${loadaddr} sysfw.itb => sf update $loadaddr 0x6C0000 $filesizerr}r(hlUhmjubaubh)r}r(hlX**Flash Layout for OSPI**rhmj\hwhh|hh~}r(h]h]h]h]h]uhMhhh]rj)r}r(hljh~}r(h]h]h]h]h]uhmjh]rhXFlash Layout for OSPIrr}r(hlUhmjubah|j'ubaubjr)r}r(hlX 0x0 +----------------------------+ | ospi.tiboot3(512K) | | | 0x80000 +----------------------------+ | ospi.tispl(2M) | | | 0x280000 +----------------------------+ | ospi.u-boot(4M) | | | 0x680000 +----------------------------+ | ospi.env(128K) | | | 0x6A0000 +----------------------------+ | ospi.env.backup (128K) | | | 0x6C0000 +----------------------------+ | ospi.sysfw(1M) | | | 0x7C0000 +----------------------------+ | padding (256k) | 0x800000 +----------------------------+ | ospi.rootfs(UBIFS) | | | +----------------------------+hmj\hwhh|juh~}r(jwjxXconsolehhh]h]h]jy}h]h]uhMhhh]rhX 0x0 +----------------------------+ | ospi.tiboot3(512K) | | | 0x80000 +----------------------------+ | ospi.tispl(2M) | | | 0x280000 +----------------------------+ | ospi.u-boot(4M) | | | 0x680000 +----------------------------+ | ospi.env(128K) | | | 0x6A0000 +----------------------------+ | ospi.env.backup (128K) | | | 0x6C0000 +----------------------------+ | ospi.sysfw(1M) | | | 0x7C0000 +----------------------------+ | padding (256k) | 0x800000 +----------------------------+ | ospi.rootfs(UBIFS) | | | +----------------------------+rr}r(hlUhmjubaubh)r}r(hlXKernel Image and DT are expected to be present in the /boot folder of UBIFS ospi.rootfs just like in SD card case. U-Boot looks for UBI volume named "rootfs" for rootfs.rhmj\hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXKernel Image and DT are expected to be present in the /boot folder of UBIFS ospi.rootfs just like in SD card case. U-Boot looks for UBI volume named "rootfs" for rootfs.rr}r(hljhmjubaubh)r}r(hlX/To boot kernel from OSPI, at the U-Boot prompt:rhmj\hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX/To boot kernel from OSPI, at the U-Boot prompt:rr}r(hljhmjubaubjr)r}r(hlX=> setenv boot ubi => boothmj\hwhh|juh~}r(jwjxXconsolehhh]h]h]jy}h]h]uhMhhh]rhX=> setenv boot ubi => bootrr}r(hlUhmjubaubeubhn)r}r(hlUhmjEhwhh|h}h~}r(h]h]h]h]rUdra7xx-supportrah]rhauhMhhh]r(h)r}r(hlXDRA7xx supportrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXDRA7xx supportrr}r(hljhmjubaubh)r}r(hlXMemory Layout of QSPI Flashrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXMemory Layout of QSPI Flashrr}r(hljhmjubaubjr)r}r(hlX+----------------+ 0x00000 | MLO | | | +----------------+ 0x040000 | u-boot.img | | | +----------------+ 0x140000 | DTB blob | +----------------+ 0x1c0000 | u-boot env | +----------------+ 0x1d0000 | u-boot env | | (backup) | +----------------+ 0x1e0000 | | | uImage | | | | | +----------------+ 0x9e0000 | | | other data | | | +----------------+hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX+----------------+ 0x00000 | MLO | | | +----------------+ 0x040000 | u-boot.img | | | +----------------+ 0x140000 | DTB blob | +----------------+ 0x1c0000 | u-boot env | +----------------+ 0x1d0000 | u-boot env | | (backup) | +----------------+ 0x1e0000 | | | uImage | | | | | +----------------+ 0x9e0000 | | | other data | | | +----------------+rr}r(hlUhmjubaubjC)r}r(hlXWriting to QSPI from U-Bootrhmjhwhh|jGh~}r(h]rUwriting-to-qspi-from-u-bootrah]h]h]h]rh&auhNhhh]rhXWriting to QSPI from U-Bootrr}r(hljhmjubaubh)r}r(hlXNote:rhmjhwhh|hh~}r(h]h]h]h]h]uhM%hhh]rhXNote:rr}r(hljhmjubaubj#)r}r(hlUhmjhwhh|j&h~}r(j(X-h]h]h]h]h]uhM'hhh]r(j )r}r(hlXWFrom the U-Boot build, the **MLO** and **u-boot.img** files are the ones to be written.hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXWFrom the U-Boot build, the **MLO** and **u-boot.img** files are the ones to be written.hmjhwhh|hh~}r(h]h]h]h]h]uhM'h]r(hXFrom the U-Boot build, the rr}r(hlXFrom the U-Boot build, the hmjubj)r}r(hlX**MLO**h~}r(h]h]h]h]h]uhmjh]rhXMLOrr}r(hlUhmjubah|j'ubhX and rr}r(hlX and hmjubj)r}r(hlX**u-boot.img**h~}r(h]h]h]h]h]uhmjh]rhX u-boot.imgrr}r(hlUhmjubah|j'ubhX" files are the ones to be written.r r }r (hlX" files are the ones to be written.hmjubeubaubj )r }r (hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists. hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.rhmj hwhh|hh~}r(h]h]h]h]h]uhM)h]rhXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.rr}r(hljhmjubaubaubeubh)r}r(hlX$Writing MLO and u-boot.img binaries.rhmjhwhh|hh~}r(h]h]h]h]h]uhM-hhh]rhX$Writing MLO and u-boot.img binaries.rr}r(hljhmjubaubh)r }r!(hlX3For QSPI\_1 build U-Boot with ``dra7xx_evm_config``r"hmjhwhh|hh~}r#(h]h]h]h]h]uhM/hhh]r$(hXFor QSPI_1 build U-Boot with r%r&}r'(hlXFor QSPI\_1 build U-Boot with hmj ubj)r(}r)(hlX``dra7xx_evm_config``h~}r*(h]h]h]h]h]uhmj h]r+hXdra7xx_evm_configr,r-}r.(hlUhmj(ubah|jubeubjr)r/}r0(hlXU-Boot # mmc rescan U-Boot # fatload mmc 0 ${loadaddr} MLO U-Boot # sf probe 0 U-Boot # sf erase 0x00000 0x100000 U-Boot # sf write ${loadaddr} 0x00000 ${filesize} U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # sf write ${loadaddr} 0x40000 ${filesize}hmjhwhh|juh~}r1(hhh]h]h]h]h]uhM>hhh]r2hXU-Boot # mmc rescan U-Boot # fatload mmc 0 ${loadaddr} MLO U-Boot # sf probe 0 U-Boot # sf erase 0x00000 0x100000 U-Boot # sf write ${loadaddr} 0x00000 ${filesize} U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # sf write ${loadaddr} 0x40000 ${filesize}r3r4}r5(hlUhmj/ubaubh)r6}r7(hlX'change SW2[5:0] = 110110 for qspi boot.r8hmjhwhh|hh~}r9(h]h]h]h]h]uhM;hhh]r:hX'change SW2[5:0] = 110110 for qspi boot.r;r<}r=(hlj8hmj6ubaubh)r>}r?(hlX<For QSPI\_4 build U-Boot with ``dra7xx_evm_qspiboot_config``r@hmjhwhh|hh~}rA(h]h]h]h]h]uhM=hhh]rB(hXFor QSPI_4 build U-Boot with rCrD}rE(hlXFor QSPI\_4 build U-Boot with hmj>ubj)rF}rG(hlX``dra7xx_evm_qspiboot_config``h~}rH(h]h]h]h]h]uhmj>h]rIhXdra7xx_evm_qspiboot_configrJrK}rL(hlUhmjFubah|jubeubjr)rM}rN(hlXU-Boot # mmc rescan U-Boot # fatload mmc 0 ${loadaddr} MLO U-Boot # sf probe 0 U-Boot # sf erase 0x00000 0x100000 U-Boot # sf write ${loadaddr} 0x00000 0x10000 U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # sf write ${loadaddr} 0x40000 0x60000hmjhwhh|juh~}rO(hhh]h]h]h]h]uhMLhhh]rPhXU-Boot # mmc rescan U-Boot # fatload mmc 0 ${loadaddr} MLO U-Boot # sf probe 0 U-Boot # sf erase 0x00000 0x100000 U-Boot # sf write ${loadaddr} 0x00000 0x10000 U-Boot # fatload mmc 0 ${loadaddr} u-boot.img U-Boot # sf write ${loadaddr} 0x40000 0x60000rQrR}rS(hlUhmjMubaubh)rT}rU(hlX'change SW2[5:0] = 110111 for qspi boot.rVhmjhwhh|hh~}rW(h]h]h]h]h]uhMIhhh]rXhX'change SW2[5:0] = 110111 for qspi boot.rYrZ}r[(hljVhmjTubaubjC)r\}r](hlUhmjhwhh|jZh~}r^(h]h]h]h]h]uhMKhhh]r_jH)r`}ra(hlUjLKhmj\hwhh|hh~}rb(h]h]h]h]h]uhKhhh]ubaubjC)rc}rd(hlXWriting to QSPI using DFUrehmjhwhh|jGh~}rf(h]rgUwriting-to-qspi-using-dfurhah]h]h]h]rih%auhNhhh]rjhXWriting to QSPI using DFUrkrl}rm(hljehmjcubaubh)rn}ro(hlX\Setup: Connect the usb0 port of EVM to ubuntu host PC. Make sure dfu-util tool is installed.rphmjhwhh|hh~}rq(h]h]h]h]h]uhMPhhh]rrhX\Setup: Connect the usb0 port of EVM to ubuntu host PC. Make sure dfu-util tool is installed.rsrt}ru(hljphmjnubaubjr)rv}rw(hlX#sudo apt-get install dfu-utilhmjhwhh|juh~}rx(hhh]h]h]h]h]uhM`hhh]ryhX#sudo apt-get install dfu-utilrzr{}r|(hlUhmjvubaubh)r}}r~(hlX From u-boot:rhmjhwhh|hh~}r(h]h]h]h]h]uhMWhhh]rhX From u-boot:rr}r(hljhmj}ubaubjr)r}r(hlXdU-Boot # env default -a U-Boot # setenv dfu_alt_info ${dfu_alt_info_qspi}; dfu 0 sf "0:0:64000000:0"hmjhwhh|juh~}r(hhh]h]h]h]h]uhMfhhh]rhXdU-Boot # env default -a U-Boot # setenv dfu_alt_info ${dfu_alt_info_qspi}; dfu 0 sf "0:0:64000000:0"rr}r(hlUhmjubaubh)r}r(hlXLFrom ubuntu PC: Using dfu-util utilities to flash the binares to QSPI flash.rhmjhwhh|hh~}r(h]h]h]h]h]uhM^hhh]rhXLFrom ubuntu PC: Using dfu-util utilities to flash the binares to QSPI flash.rr}r(hljhmjubaubjr)r}r(hlX# sudo dfu-util -l (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc. (C) 2010-2011 Tormod Volden (DfuSe support) This program is Free Software and has ABSOLUTELY NO WARRANTY dfu-util does currently only support DFU version 1.0 Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=0, name="MLO" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=1, name="u-boot.img" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=2, name="u-boot-spl-os" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=3, name="u-boot-env" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=4, name="u-boot-env.backup" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=5, name="kernel"hmjhwhh|juh~}r(hhh]h]h]h]h]uhMnhhh]rhX# sudo dfu-util -l (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc. (C) 2010-2011 Tormod Volden (DfuSe support) This program is Free Software and has ABSOLUTELY NO WARRANTY dfu-util does currently only support DFU version 1.0 Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=0, name="MLO" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=1, name="u-boot.img" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=2, name="u-boot-spl-os" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=3, name="u-boot-env" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=4, name="u-boot-env.backup" Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=5, name="kernel"rr}r(hlUhmjubaubh)r}r(hlXXFlash the binaries to the respective regions using alternate interface number (alt=).rhmjhwhh|hh~}r(h]h]h]h]h]uhMohhh]rhXXFlash the binaries to the respective regions using alternate interface number (alt=).rr}r(hljhmjubaubjr)r}r(hlX# sudo dfu-util -c 1 -i 0 -a 0 -D MLO # sudo dfu-util -c 1 -i 0 -a 1 -D u-boot.img # sudo dfu-util -c 1 -i 0 -a 2 -D # sudo dfu-util -c 1 -i 0 -a 5 -D uImagehmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX# sudo dfu-util -c 1 -i 0 -a 0 -D MLO # sudo dfu-util -c 1 -i 0 -a 1 -D u-boot.img # sudo dfu-util -c 1 -i 0 -a 2 -D # sudo dfu-util -c 1 -i 0 -a 5 -D uImagerr}r(hlUhmjubaubjC)r}r(hlXBooting from QSPI from u-bootrhmjhwhh|jGh~}r(h]rUbooting-from-qspi-from-u-bootrah]h]h]h]rhUauhNhhh]rhXBooting from QSPI from u-bootrr}r(hljhmjubaubh)r}r(hlXThe default environment does not contain a QSPI boot command. The following example uses the partition table found in the kernel.rhmjhwhh|hh~}r(h]h]h]h]h]uhM|hhh]rhXThe default environment does not contain a QSPI boot command. The following example uses the partition table found in the kernel.rr}r(hljhmjubaubjr)r}r(hlXU-Boot # sf probe 0 U-Boot # sf read ${loadaddr} 0x1e0000 0x800000 U-Boot # sf read ${fdtaddr} 0x140000 0x80000 U-Boot # setenv bootargs console=${console} root=/dev/mtdblock19 rootfstype=jffs2 U-Boot # bootz ${loadaddr} - ${fdtaddr}hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXU-Boot # sf probe 0 U-Boot # sf read ${loadaddr} 0x1e0000 0x800000 U-Boot # sf read ${fdtaddr} 0x140000 0x80000 U-Boot # setenv bootargs console=${console} root=/dev/mtdblock19 rootfstype=jffs2 U-Boot # bootz ${loadaddr} - ${fdtaddr}rr}r(hlUhmjubaubjC)r}r(hlX8Booting from QSPI from SPL (Single stage or Falcon mode)rhmjhwhh|jGh~}r(h]rU6booting-from-qspi-from-spl-single-stage-or-falcon-moderah]h]h]h]rh1auhNhhh]rhX8Booting from QSPI from SPL (Single stage or Falcon mode)rr}r(hljhmjubaubh)r}r(hlXIn this boot mode SPL (first stage bootloader) directly boots the Linux kernel. Optionally, in order to enter into U-Boot, reset the board while keeping 'c' key on the serial terminal pressed. When falcon mode is enabled in U-Boot build (usually enabled by default), MLO checks if there is a valid uImage present at a defined offset. If uImage is present, it is booted directly. If valid uImage is not found, MLO falls back to booting u-boot.img.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXIn this boot mode SPL (first stage bootloader) directly boots the Linux kernel. Optionally, in order to enter into U-Boot, reset the board while keeping 'c' key on the serial terminal pressed. When falcon mode is enabled in U-Boot build (usually enabled by default), MLO checks if there is a valid uImage present at a defined offset. If uImage is present, it is booted directly. If valid uImage is not found, MLO falls back to booting u-boot.img.rr}r(hljhmjubaubh)r}r(hlXKFor QSPI single stage or Falcon mode, the CONFIG\_QSPI\_BOOT shall enabled.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXIFor QSPI single stage or Falcon mode, the CONFIG_QSPI_BOOT shall enabled.rr}r(hlXKFor QSPI single stage or Falcon mode, the CONFIG\_QSPI\_BOOT shall enabled.hmjubaubjr)r}r(hlXMenuconfig->Bood media [ ] Support for booting from NAND flash .. [*] Support for booting from QSPI flash [ ] Support for booting from SATA ...hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXMenuconfig->Bood media [ ] Support for booting from NAND flash .. [*] Support for booting from QSPI flash [ ] Support for booting from SATA ...rr}r(hlUhmjubaubh)r}r(hlXMLO, u-boot.img (optional), DTB, uImage are stored in QSPI flash memory. Refer the "Memory Layout" section for offset details. To flash binaries to QSPI, you can use `DFU `__, for example.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXMLO, u-boot.img (optional), DTB, uImage are stored in QSPI flash memory. Refer the "Memory Layout" section for offset details. To flash binaries to QSPI, you can use rr}r(hlXMLO, u-boot.img (optional), DTB, uImage are stored in QSPI flash memory. Refer the "Memory Layout" section for offset details. To flash binaries to QSPI, you can use hmjubh)r}r(hlXG`DFU `__h~}r(UnameXDFUhX=Foundational_Components_U-Boot.html#writing-to-qspi-using-dfuh]h]h]h]h]uhmjh]rhXDFUrr}r(hlUhmjubah|hubhX, for example.rr}r(hlX, for example.hmjubeubh)r}r(hlXwThe QSPI boot uses uImage. Build the kernel uImage. You will need to keep the U-Boot tool ``mkimage`` in your ``$PATH``hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXZThe QSPI boot uses uImage. Build the kernel uImage. You will need to keep the U-Boot tool rr}r(hlXZThe QSPI boot uses uImage. Build the kernel uImage. You will need to keep the U-Boot tool hmjubj)r}r(hlX ``mkimage``h~}r(h]h]h]h]h]uhmjh]rhXmkimagerr}r(hlUhmjubah|jubhX in your rr}r(hlX in your hmjubj)r}r(hlX ``$PATH``h~}r (h]h]h]h]h]uhmjh]r hX$PATHr r }r (hlUhmjubah|jubeubjr)r}r(hlX,# make uImage modules dtbs LOADADDR=80008000hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX,# make uImage modules dtbs LOADADDR=80008000rr}r(hlUhmjubaubh)r}r(hlXIf kernel is not build with ``CONFIG_CMDLINE`` to set correct bootargs, then add the needed bootargs in chosen node in DTB file, using fdtput host utility. For example, for DRA74x EVM:hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXIf kernel is not build with rr}r(hlXIf kernel is not build with hmjubj)r}r(hlX``CONFIG_CMDLINE``h~}r(h]h]h]h]h]uhmjh]rhXCONFIG_CMDLINEr r!}r"(hlUhmjubah|jubhX to set correct bootargs, then add the needed bootargs in chosen node in DTB file, using fdtput host utility. For example, for DRA74x EVM:r#r$}r%(hlX to set correct bootargs, then add the needed bootargs in chosen node in DTB file, using fdtput host utility. For example, for DRA74x EVM:hmjubeubjr)r&}r'(hlXi# fdtput -v -t s arch/arm/boot/dts/dra7-evm.dtb "/chosen" bootargs "console=ttyO0,115200n8 root="hmjhwhh|juh~}r((hhh]h]h]h]h]uhMhhh]r)hXi# fdtput -v -t s arch/arm/boot/dts/dra7-evm.dtb "/chosen" bootargs "console=ttyO0,115200n8 root="r*r+}r,(hlUhmj&ubaubh)r-}r.(hlX-Set the environment variable "boot\_os" to 1.r/hmjhwhh|hh~}r0(h]h]h]h]h]uhMhhh]r1hX,Set the environment variable "boot_os" to 1.r2r3}r4(hlX-Set the environment variable "boot\_os" to 1.hmj-ubaubh)r5}r6(hlXFrom u-boot promptr7hmjhwhh|hh~}r8(h]h]h]h]h]uhMhhh]r9hXFrom u-boot promptr:r;}r<(hlj7hmj5ubaubjr)r=}r>(hlX=> setenv boot_os 1 => saveenvhmjhwhh|juh~}r?(hhh]h]h]h]h]uhMhhh]r@hX=> setenv boot_os 1 => saveenvrArB}rC(hlUhmj=ubaubh)rD}rE(hlXSet the `board boot from QSPI `__ and reset the EVM. The SPL directly boots the kernel image from QSPI.hmjhwhh|hh~}rF(h]h]h]h]h]uhMhhh]rG(hXSet the rHrI}rJ(hlXSet the hmjDubh)rK}rL(hlXZ`board boot from QSPI `__h~}rM(UnameXboard boot from QSPIhX?Foundational_Components_U-Boot.html#writing-to-qspi-from-u-booth]h]h]h]h]uhmjDh]rNhXboard boot from QSPIrOrP}rQ(hlUhmjKubah|hubhXF and reset the EVM. The SPL directly boots the kernel image from QSPI.rRrS}rT(hlXF and reset the EVM. The SPL directly boots the kernel image from QSPI.hmjDubeubjC)rU}rV(hlUhmjhwhh|jZh~}rW(h]h]h]h]h]uhMhhh]rXjH)rY}rZ(hlUjLKhmjUhwhh|hh~}r[(h]h]h]h]h]uhKhhh]ubaubeubhn)r\}r](hlUhmjEhwhh|h}h~}r^(h]h]h]h]r_Uam43xx-supportr`ah]rah5auhMhhh]rb(h)rc}rd(hlXAM43xx supportrehmj\hwhh|hh~}rf(h]h]h]h]h]uhMhhh]rghXAM43xx supportrhri}rj(hljehmjcubaubh)rk}rl(hlXYUsing QSPI on AM43xx platforms is done as eXecute In Place and U-Boot is directly booted.rmhmj\hwhh|hh~}rn(h]h]h]h]h]uhMhhh]rohXYUsing QSPI on AM43xx platforms is done as eXecute In Place and U-Boot is directly booted.rprq}rr(hljmhmjkubaubjC)rs}rt(hlXWriting to QSPI from U-Bootruhmj\hwhh|jGh~}rv(h]rwUwriting-to-qspi-from-u-boot-1rxah]h]h]h]ryh auhNhhh]rzhXWriting to QSPI from U-Bootr{r|}r}(hljuhmjsubaubh)r~}r(hlXNote:rhmj\hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXNote:rr}r(hljhmj~ubaubj#)r}r(hlUhmj\hwhh|j&h~}r(j(X-h]h]h]h]h]uhMhhh]r(j )r}r(hlXGFrom the U-Boot build the **u-boot.bin** file is the one to be written.hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXGFrom the U-Boot build the **u-boot.bin** file is the one to be written.hmjhwhh|hh~}r(h]h]h]h]h]uhMh]r(hXFrom the U-Boot build the rr}r(hlXFrom the U-Boot build the hmjubj)r}r(hlX**u-boot.bin**h~}r(h]h]h]h]h]uhmjh]rhX u-boot.binrr}r(hlUhmjubah|j'ubhX file is the one to be written.rr}r(hlX file is the one to be written.hmjubeubaubj )r}r(hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists. hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.rhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.rr}r(hljhmjubaubaubeubjr)r}r(hlXU-Boot # mmc rescan U-Boot # fatload mmc 0 ${loadaddr} u-boot.bin U-Boot # sf probe 0 U-Boot # sf erase 0x0 0x100000 U-Boot # sf write ${loadaddr} 0x0 ${filesize}hmj\hwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXU-Boot # mmc rescan U-Boot # fatload mmc 0 ${loadaddr} u-boot.bin U-Boot # sf probe 0 U-Boot # sf erase 0x0 0x100000 U-Boot # sf write ${loadaddr} 0x0 ${filesize}rr}r(hlUhmjubaubjC)r}r(hlXBooting from QSPIrhmj\hwhh|jGh~}r(h]rUbooting-from-qspirah]h]h]h]rh'auhNhhh]rhXBooting from QSPIrr}r(hljhmjubaubh)r}r(hlXThe default environment does not contain a QSPI boot command. The following example uses the partition table found in the kernel.rhmj\hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXThe default environment does not contain a QSPI boot command. The following example uses the partition table found in the kernel.rr}r(hljhmjubaubjr)r}r(hlXU-Boot # sf probe 0 U-Boot # sf read ${loadaddr} 0x1a0000 0x800000 U-Boot # sf read ${fdtaddr} 0x100000 0x80000 U-Boot # setenv bootargs console=${console} spi-ti-qspi.enable_qspi=1 root=/dev/mtdblock6 rootfstype=jffs2 U-Boot # bootz ${loadaddr} - ${fdtaddr}hmj\hwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXU-Boot # sf probe 0 U-Boot # sf read ${loadaddr} 0x1a0000 0x800000 U-Boot # sf read ${fdtaddr} 0x100000 0x80000 U-Boot # setenv bootargs console=${console} spi-ti-qspi.enable_qspi=1 root=/dev/mtdblock6 rootfstype=jffs2 U-Boot # bootz ${loadaddr} - ${fdtaddr}rr}r(hlUhmjubaubjC)r}r(hlUhmj\hwhh|jZh~}r(h]h]h]h]h]uhMhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubeubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUnorrah]rhauhMhhh]r(h)r}r(hlXNORrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXNORrr}r(hljhmjubaubh)r}r(hlUhmjhwhh|hh~}r(hX#CONFIG_part_family in ('J7_family')h]h]h]h]h]uhMhhh]rj)r}r(hlX0Parallel NOR is not supported on J721E platform.rhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhX0Parallel NOR is not supported on J721E platform.rr}r(hljhmjubaubaubaubh)r}r(hlX!This section documents how to write files to the NOR device and use it to load and then boot the Linux Kernel using a root filesystem also found on NOR. In order for NOR to be visible to U-Boot a special build of U-Boot is required on the supported hardware. The table below lists builds that see NOR and in some cases also use theit for the environment instead of the default, which typically is NAND. Finally, for simplicity we assume the files are being loaded from an SD card. Using the network interface (if applicable) is documented above.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX!This section documents how to write files to the NOR device and use it to load and then boot the Linux Kernel using a root filesystem also found on NOR. In order for NOR to be visible to U-Boot a special build of U-Boot is required on the supported hardware. The table below lists builds that see NOR and in some cases also use theit for the environment instead of the default, which typically is NAND. Finally, for simplicity we assume the files are being loaded from an SD card. Using the network interface (if applicable) is documented above.rr}r(hljhmjubaubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rUwriting-to-nor-from-u-bootrah]rhZauhMhhh]r(h)r}r(hlXWriting to NOR from U-Bootrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXWriting to NOR from U-Bootrr}r(hljhmjubaubh)r }r (hlXNote:r hmjhwhh|hh~}r (h]h]h]h]h]uhMhhh]r hXNote:rr}r(hlj hmj ubaubj#)r}r(hlUhmjhwhh|j&h~}r(j(X-h]h]h]h]h]uhMhhh]r(j )r}r(hlXHFrom the U-Boot build, the **u-boot.bin** file is the one to be written.hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXHFrom the U-Boot build, the **u-boot.bin** file is the one to be written.hmjhwhh|hh~}r(h]h]h]h]h]uhMh]r(hXFrom the U-Boot build, the rr}r(hlXFrom the U-Boot build, the hmjubj)r }r!(hlX**u-boot.bin**h~}r"(h]h]h]h]h]uhmjh]r#hX u-boot.binr$r%}r&(hlUhmj ubah|j'ubhX file is the one to be written.r'r(}r)(hlX file is the one to be written.hmjubeubaubj )r*}r+(hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.hmjhwhh|jh~}r,(h]h]h]h]h]uhNhhh]r-h)r.}r/(hlXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.r0hmj*hwhh|hh~}r1(h]h]h]h]h]uhMh]r2hXWe load all files from an SD card in this example but they can just as easily be loaded via network (documented above) or other interface that exists.r3r4}r5(hlj0hmj.ubaubaubj )r6}r7(hlXtAt this time the NOR mtd partition map has not yet been updated to include an example location for the device tree. hmjhwhh|jh~}r8(h]h]h]h]h]uhNhhh]r9h)r:}r;(hlXsAt this time the NOR mtd partition map has not yet been updated to include an example location for the device tree.r<hmj6hwhh|hh~}r=(h]h]h]h]h]uhMh]r>hXsAt this time the NOR mtd partition map has not yet been updated to include an example location for the device tree.r?r@}rA(hlj<hmj:ubaubaubeubj)rB}rC(hlUhmjhwhh|jh~}rD(h]h]h]h]h]uhNhhh]rEj)rF}rG(hlUh~}rH(h]h]h]h]h]UcolsKuhmjBh]rI(j)rJ}rK(hlUh~}rL(h]h]h]h]h]UcolwidthKuhmjFh]h|j"ubj)rM}rN(hlUh~}rO(h]h]h]h]h]UcolwidthK;uhmjFh]h|j"ubj/)rP}rQ(hlUh~}rR(h]h]h]h]h]uhmjFh]rSj4)rT}rU(hlUh~}rV(h]h]h]h]h]uhmjPh]rW(j9)rX}rY(hlUh~}rZ(h]h]h]h]h]uhmjTh]r[h)r\}r](hlXBoardr^hmjXhwhh|hh~}r_(h]h]h]h]h]uhM h]r`hXBoardrarb}rc(hlj^hmj\ubaubah|jFubj9)rd}re(hlUh~}rf(h]h]h]h]h]uhmjTh]rgh)rh}ri(hlX Config targetrjhmjdhwhh|hh~}rk(h]h]h]h]h]uhM h]rlhX Config targetrmrn}ro(hljjhmjhubaubah|jFubeh|jwubah|jxubjy)rp}rq(hlUh~}rr(h]h]h]h]h]uhmjFh]rsj4)rt}ru(hlUh~}rv(h]h]h]h]h]uhmjph]rw(j9)rx}ry(hlUh~}rz(h]h]h]h]h]uhmjth]r{h)r|}r}(hlX AM335x EVMr~hmjxhwhh|hh~}r(h]h]h]h]h]uhM h]rhX AM335x EVMrr}r(hlj~hmj|ubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjth]rh)r}r(hlX7am335x\_evm\_nor\_config / am335x\_evm\_norboot\_confighmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX1am335x_evm_nor_config / am335x_evm_norboot_configrr}r(hlX7am335x\_evm\_nor\_config / am335x\_evm\_norboot\_confighmjubaubah|jFubeh|jwubah|jubeh|jubaubjr)r}r(hlX U-Boot # mmc rescan U-Boot # load mmc 0 ${loadaddr} u-boot.bin U-Boot # protect off 08000000 +4c0000 U-Boot # erase 08000000 +4c0000 U-Boot # cp.b ${loadaddr} 08000000 ${filesize} U-Boot # fatload mmc 0 ${loadaddr} zImage U-Boot # cp.b ${loadaddr} 080c0000 ${filesize}hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX U-Boot # mmc rescan U-Boot # load mmc 0 ${loadaddr} u-boot.bin U-Boot # protect off 08000000 +4c0000 U-Boot # erase 08000000 +4c0000 U-Boot # cp.b ${loadaddr} 08000000 ${filesize} U-Boot # fatload mmc 0 ${loadaddr} zImage U-Boot # cp.b ${loadaddr} 080c0000 ${filesize}rr}r(hlUhmjubaubeubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rUbooting-from-norrah]rh]auhMhhh]r(h)r}r(hlXBooting from NORrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXBooting from NORrr}r(hljhmjubaubh)r}r(hlXWithin the default environment there is not a shortcut for booting. One needs to pass **root=/dev/mtdblockN** where N is the number of the rootfs partition in **bootargs**.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXVWithin the default environment there is not a shortcut for booting. One needs to pass rr}r(hlXVWithin the default environment there is not a shortcut for booting. One needs to pass hmjubj)r}r(hlX**root=/dev/mtdblockN**h~}r(h]h]h]h]h]uhmjh]rhXroot=/dev/mtdblockNrr}r(hlUhmjubah|j'ubhX2 where N is the number of the rootfs partition in rr}r(hlX2 where N is the number of the rootfs partition in hmjubj)r}r(hlX **bootargs**h~}r(h]h]h]h]h]uhmjh]rhXbootargsrr}r(hlUhmjubah|j'ubhX.r}r(hlX.hmjubeubjC)r}r(hlUhmjhwhh|jZh~}r(h]h]h]h]h]uhM hhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubeubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUuartrah]rhCauhM#hhh]r(h)r}r(hlXUARTrhmjhwhh|hh~}r(h]h]h]h]h]uhM#hhh]rhXUARTrr}r(hljhmjubaubh)r}r(hlXThis section documents how to use the UART to load files to boot the board into U-Boot. After that the user is expected to know how they want to continue loading files.rhmjhwhh|hh~}r(h]h]h]h]h]uhM&hhh]rhXThis section documents how to use the UART to load files to boot the board into U-Boot. After that the user is expected to know how they want to continue loading files.rr}r(hljhmjubaubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rU$booting-u-boot-from-the-console-uartrah]rh`auhM+hhh]r(h)r}r(hlX$Booting U-Boot from the console UARTrhmjhwhh|hh~}r(h]h]h]h]h]uhM+hhh]rhX$Booting U-Boot from the console UARTrr}r(hljhmjubaubh)r}r(hlXIn some cases we support loading SPL and U-Boot over the console UART. You will need to use the **spl/u-boot-spl.bin** and **u-boot.img** files to boot. As per the TRM, the file is to be loaded via the X-MODEM protocol at 115200 baud 8 stop bits no parity (same as using it for console). SPL in turn expects to be sent **u-boot.img** at the same rate but via Y-MODEM. An example session from the host PC, assuming console is on ttyUSB0 and already configured would be and the **lrzsz** package is installedhmjhwhh|hh~}r(h]h]h]h]h]uhM-hhh]r(hX`In some cases we support loading SPL and U-Boot over the console UART. You will need to use the rr}r(hlX`In some cases we support loading SPL and U-Boot over the console UART. You will need to use the hmjubj)r}r(hlX**spl/u-boot-spl.bin**h~}r(h]h]h]h]h]uhmjh]rhXspl/u-boot-spl.binrr}r(hlUhmjubah|j'ubhX and rr}r(hlX and hmjubj)r}r(hlX**u-boot.img**h~}r(h]h]h]h]h]uhmjh]rhX u-boot.imgrr}r(hlUhmjubah|j'ubhX files to boot. As per the TRM, the file is to be loaded via the X-MODEM protocol at 115200 baud 8 stop bits no parity (same as using it for console). SPL in turn expects to be sent rr}r(hlX files to boot. As per the TRM, the file is to be loaded via the X-MODEM protocol at 115200 baud 8 stop bits no parity (same as using it for console). SPL in turn expects to be sent hmjubj)r}r(hlX**u-boot.img**h~}r (h]h]h]h]h]uhmjh]r hX u-boot.imgr r }r (hlUhmjubah|j'ubhX at the same rate but via Y-MODEM. An example session from the host PC, assuming console is on ttyUSB0 and already configured would be and the rr}r(hlX at the same rate but via Y-MODEM. An example session from the host PC, assuming console is on ttyUSB0 and already configured would be and the hmjubj)r}r(hlX **lrzsz**h~}r(h]h]h]h]h]uhmjh]rhXlrzszrr}r(hlUhmjubah|j'ubhX package is installedrr}r(hlX package is installedhmjubeubjr)r}r(hlX$ sx -kb /path/to/u-boot-spl.bin < /dev/ttyUSB0 > /dev/ttyUSB0 $ sx -kb --ymodem /path/to/u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0hmjhwhh|juh~}r(hhh]h]h]h]h]uhMChhh]rhX$ sx -kb /path/to/u-boot-spl.bin < /dev/ttyUSB0 > /dev/ttyUSB0 $ sx -kb --ymodem /path/to/u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0rr }r!(hlUhmjubaubh)r"}r#(hlXIn K3 based platforms, ROM supports booting from MCU_UART0 via X-Modem protocol. The entire UART-based boot process up to U-Boot (proper) prompt goes through different stages and uses different UART peripherals as follows:r$hmjhwhh|hh~}r%(h]h]h]h]h]uhM;hhh]r&hXIn K3 based platforms, ROM supports booting from MCU_UART0 via X-Modem protocol. The entire UART-based boot process up to U-Boot (proper) prompt goes through different stages and uses different UART peripherals as follows:r'r(}r)(hlj$hmj"ubaubj)r*}r+(hlUhmjhwhh|jh~}r,(h]h]h]h]h]uhNhhh]r-j)r.}r/(hlUh~}r0(h]h]h]h]h]UcolsKuhmj*h]r1(j)r2}r3(hlUh~}r4(h]h]h]h]h]UcolwidthKuhmj.h]h|j"ubj)r5}r6(hlUh~}r7(h]h]h]h]h]UcolwidthKuhmj.h]h|j"ubj)r8}r9(hlUh~}r:(h]h]h]h]h]UcolwidthK uhmj.h]h|j"ubj)r;}r<(hlUh~}r=(h]h]h]h]h]UcolwidthK uhmj.h]h|j"ubj/)r>}r?(hlUh~}r@(h]h]h]h]h]uhmj.h]rAj4)rB}rC(hlUh~}rD(h]h]h]h]h]uhmj>h]rE(j9)rF}rG(hlUh~}rH(h]h]h]h]h]uhmjBh]rIh)rJ}rK(hlXWHOrLhmjFhwhh|hh~}rM(h]h]h]h]h]uhM@h]rNhXWHOrOrP}rQ(hljLhmjJubaubah|jFubj9)rR}rS(hlUh~}rT(h]h]h]h]h]uhmjBh]rUh)rV}rW(hlX Loading WHATrXhmjRhwhh|hh~}rY(h]h]h]h]h]uhM@h]rZhX Loading WHATr[r\}r](hljXhmjVubaubah|jFubj9)r^}r_(hlUh~}r`(h]h]h]h]h]uhmjBh]rah)rb}rc(hlX HW Modulerdhmj^hwhh|hh~}re(h]h]h]h]h]uhM@h]rfhX HW Modulergrh}ri(hljdhmjbubaubah|jFubj9)rj}rk(hlUh~}rl(h]h]h]h]h]uhmjBh]rmh)rn}ro(hlXProtocolrphmjjhwhh|hh~}rq(h]h]h]h]h]uhM@h]rrhXProtocolrsrt}ru(hljphmjnubaubah|jFubeh|jwubah|jxubjy)rv}rw(hlUh~}rx(h]h]h]h]h]uhmj.h]ry(j4)rz}r{(hlUh~}r|(h]h]h]h]h]uhmjvh]r}(j9)r~}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlXBoot ROMrhmj~hwhh|hh~}r(h]h]h]h]h]uhMBh]rhXBoot ROMrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlX tiboot3.binrhmjhwhh|hh~}r(h]h]h]h]h]uhMBh]rhX tiboot3.binrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlX MCU_UART0rhmjhwhh|hh~}r(h]h]h]h]h]uhMBh]rhX MCU_UART0rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjzh]rh)r}r(hlXX-Modemrhmjhwhh|hh~}r(h]h]h]h]h]uhMBh]rhXX-Modemrr}r(hljhmjubaubah|jFubeh|jwubj4)r}r(hlUh~}r(h]h]h]h]h]uhmjvh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXR5 SPLrhmjhwhh|hh~}r(h]h]h]h]h]uhMDh]rhXR5 SPLrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX sysfw.itbrhmjhwhh|hh~}r(h]h]h]h]h]uhMDh]rhX sysfw.itbrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX MCU_UART0rhmjhwhh|hh~}r(h]h]h]h]h]uhMDh]rhX MCU_UART0rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXY-Modemrhmjhwhh|hh~}r(h]h]h]h]h]uhMDh]rhXY-Modemrr}r(hljhmjubaubah|jFubeh|jwubj4)r}r(hlUh~}r(h]h]h]h]h]uhmjvh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXR5 SPLrhmjhwhh|hh~}r(h]h]h]h]h]uhMFh]rhXR5 SPLrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX tispl.binrhmjhwhh|hh~}r(h]h]h]h]h]uhMFh]rhX tispl.binrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX MAIN_UART0rhmjhwhh|hh~}r(h]h]h]h]h]uhMFh]rhX MAIN_UART0rr}r (hljhmjubaubah|jFubj9)r }r (hlUh~}r (h]h]h]h]h]uhmjh]r h)r}r(hlXY-Modemrhmj hwhh|hh~}r(h]h]h]h]h]uhMFh]rhXY-Modemrr}r(hljhmjubaubah|jFubeh|jwubj4)r}r(hlUh~}r(h]h]h]h]h]uhmjvh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX A53/A72 SPLr hmjhwhh|hh~}r!(h]h]h]h]h]uhMHh]r"hX A53/A72 SPLr#r$}r%(hlj hmjubaubah|jFubj9)r&}r'(hlUh~}r((h]h]h]h]h]uhmjh]r)h)r*}r+(hlX u-boot.imgr,hmj&hwhh|hh~}r-(h]h]h]h]h]uhMHh]r.hX u-boot.imgr/r0}r1(hlj,hmj*ubaubah|jFubj9)r2}r3(hlUh~}r4(h]h]h]h]h]uhmjh]r5h)r6}r7(hlX MAIN_UART0r8hmj2hwhh|hh~}r9(h]h]h]h]h]uhMHh]r:hX MAIN_UART0r;r<}r=(hlj8hmj6ubaubah|jFubj9)r>}r?(hlUh~}r@(h]h]h]h]h]uhmjh]rAh)rB}rC(hlXY-ModemrDhmj>hwhh|hh~}rE(h]h]h]h]h]uhMHh]rFhXY-ModemrGrH}rI(hljDhmjBubaubah|jFubeh|jwubeh|jubeh|jubaubh)rJ}rK(hlX^UART_BOOT_MAIN_UART and UART_BOOT_MCU_UART should be set to serial ports such as /dev/ttyUSBx.rLhmjhwhh|hh~}rM(h]h]h]h]h]uhMKhhh]rNhX^UART_BOOT_MAIN_UART and UART_BOOT_MCU_UART should be set to serial ports such as /dev/ttyUSBx.rOrP}rQ(hljLhmjJubaubjr)rR}rS(hlX1$ sb --xmodem $OUT_R5/tiboot3.bin > $UART_BOOT_MCU_UART < $UART_BOOT_MCU_UART $ sb --ymodem $SYSFW_ITB > $UART_BOOT_MCU_UART < $UART_BOOT_MCU_UART $ sb --ymodem $OUT_AXX/tispl.bin > $UART_BOOT_MAIN_UART < $UART_BOOT_MAIN_UART $ sb --xmodem $OUT_AXX/u-boot.img > $UART_BOOT_MAIN_UART < $UART_BOOT_MAIN_UARThmjhwhh|juh~}rT(hhh]h]h]h]h]uhMZhhh]rUhX1$ sb --xmodem $OUT_R5/tiboot3.bin > $UART_BOOT_MCU_UART < $UART_BOOT_MCU_UART $ sb --ymodem $SYSFW_ITB > $UART_BOOT_MCU_UART < $UART_BOOT_MCU_UART $ sb --ymodem $OUT_AXX/tispl.bin > $UART_BOOT_MAIN_UART < $UART_BOOT_MAIN_UART $ sb --xmodem $OUT_AXX/u-boot.img > $UART_BOOT_MAIN_UART < $UART_BOOT_MAIN_UARTrVrW}rX(hlUhmjRubaubeubeubhn)rY}rZ(hlUhmhshwhh|h}h~}r[(h]h]h]h]r\Usatar]ah]r^hQauhMUhhh]r_(h)r`}ra(hlXSATArbhmjYhwhh|hh~}rc(h]h]h]h]h]uhMUhhh]rdhXSATArerf}rg(hljbhmj`ubaubj)rh}ri(hlX(SATA is not supported on J721E platform.rjhmjYhwhh|jh~}rk(h]h]h]h]h]uhNhhh]rlh)rm}rn(hljjhmjhhwhh|hh~}ro(h]h]h]h]h]uhMXh]rphX(SATA is not supported on J721E platform.rqrr}rs(hljjhmjmubaubaubh)rt}ru(hlX9SATA and eSATA devices show up as SCSI devices in U-boot.rvhmjYhwhh|hh~}rw(h]h]h]h]h]uhMZhhh]rxhX9SATA and eSATA devices show up as SCSI devices in U-boot.ryrz}r{(hljvhmjtubaubhn)r|}r}(hlUhmjYhwhh|h}h~}r~(h]h]h]h]rUviewing-sata-devicesrah]rhauhM]hhh]r(h)r}r(hlXViewing SATA Devicesrhmj|hwhh|hh~}r(h]h]h]h]h]uhM]hhh]rhXViewing SATA Devicesrr}r(hljhmjubaubh)r}r(hlXNTo view all SCSI devices that U-boot sees the command "scsi info" can be used.rhmj|hwhh|hh~}r(h]h]h]h]h]uhM^hhh]rhXNTo view all SCSI devices that U-boot sees the command "scsi info" can be used.rr}r(hljhmjubaubh)r}r(hlXOOutput of this command when ran on AM57x General Purpose EVM can be seen below.rhmj|hwhh|hh~}r(h]h]h]h]h]uhMahhh]rhXOOutput of this command when ran on AM57x General Purpose EVM can be seen below.rr}r(hljhmjubaubjr)r}r(hlXscsi part Device 0: (0:0) Vendor: ATA Prod.: PLEXTOR PX-64M6M Rev: 1.08 Type: Hard Disk Capacity: 61057.3 MB = 59.6 GB (125045424 x 512)hmj|hwhh|juh~}r(hhh]h]h]h]h]uhMqhhh]rhXscsi part Device 0: (0:0) Vendor: ATA Prod.: PLEXTOR PX-64M6M Rev: 1.08 Type: Hard Disk Capacity: 61057.3 MB = 59.6 GB (125045424 x 512)rr}r(hlUhmjubaubh)r}r(hlXDevice 0 represents the instance of the scsi device. Therefore, in later commands when a "" parameter is seen replace it with the appropriate device number.rhmj|hwhh|hh~}r(h]h]h]h]h]uhMkhhh]rhXDevice 0 represents the instance of the scsi device. Therefore, in later commands when a "" parameter is seen replace it with the appropriate device number.rr}r(hljhmjubaubeubhn)r}r(hlUhmjYhwhh|h}h~}r(h]h]h]h]rUviewing-partitionsrah]rhNauhMphhh]r(h)r}r(hlXViewing Partitionsrhmjhwhh|hh~}r(h]h]h]h]h]uhMphhh]rhXViewing Partitionsrr}r(hljhmjubaubh)r}r(hlX^To view all the partitions found on the SATA device the command "scsi part " can be used.rhmjhwhh|hh~}r(h]h]h]h]h]uhMqhhh]rhX^To view all the partitions found on the SATA device the command "scsi part " can be used.rr}r(hljhmjubaubh)r}r(hlXOOutput of this command when ran on AM57x General Purpose EVM can be seen below.rhmjhwhh|hh~}r(h]h]h]h]h]uhMthhh]rhXOOutput of this command when ran on AM57x General Purpose EVM can be seen below.rr}r(hljhmjubaubjr)r}r(hlX-Partition Map for SCSI device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1 2048 161793 6cc50771-01 0c Boot 2 165888 33552385 6cc50771-02 83 3 33720320 91325104 6cc50771-03 83hmjhwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhX-Partition Map for SCSI device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1 2048 161793 6cc50771-01 0c Boot 2 165888 33552385 6cc50771-02 83 3 33720320 91325104 6cc50771-03 83rr}r(hlUhmjubaubh)r}r(hlX"All entries above represent different partitions that exist on the particular scsi device. To reference a particular partition a user will reference it the part number shown above. In commands shown below should be replaced with the appropriate partition number seen from this table.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX"All entries above represent different partitions that exist on the particular scsi device. To reference a particular partition a user will reference it the part number shown above. In commands shown below should be replaced with the appropriate partition number seen from this table.rr}r(hljhmjubaubeubhn)r}r(hlUhmjYhwhh|h}h~}r(h]h]h]h]rU%identifying-partition-filesystem-typerah]rh"auhMhhh]r(h)r}r(hlX%Identifying Partition Filesystem Typerhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX%Identifying Partition Filesystem Typerr}r(hljhmjubaubh)r}r(hlXAs shown above the "scsi part " command can be used to view all the partitions available on the particular scsi device. However, the proper commands to use depend on the filesystem type each partition have been formatted to.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXAs shown above the "scsi part " command can be used to view all the partitions available on the particular scsi device. However, the proper commands to use depend on the filesystem type each partition have been formatted to.rr}r(hljhmjubaubh)r}r(hlXIn the "scsi part " command the partition type can be found under the type column. The values under the Type column are referred to as partition id. Depending on the partition id will dedicate which commands to use to read and write partition. Partition id of "0c" refers to a FAT32 partition. Partition id of "83" refers to a native Linux file system which ext2,ext3 and ext4 fall under. Go `here `__ to find a complete list of partition ids.hmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXIn the "scsi part " command the partition type can be found under the type column. The values under the Type column are referred to as partition id. Depending on the partition id will dedicate which commands to use to read and write partition. Partition id of "0c" refers to a FAT32 partition. Partition id of "83" refers to a native Linux file system which ext2,ext3 and ext4 fall under. Go rr}r(hlXIn the "scsi part " command the partition type can be found under the type column. The values under the Type column are referred to as partition id. Depending on the partition id will dedicate which commands to use to read and write partition. Partition id of "0c" refers to a FAT32 partition. Partition id of "83" refers to a native Linux file system which ext2,ext3 and ext4 fall under. Go hmjubh)r}r(hlXM`here `__h~}r(UnameXherehXBhttps://en.wikipedia.org/wiki/Partition_type#List_of_partition_IDsh]h]h]h]h]uhmjh]rhXhererr}r(hlUhmjubah|hubhX* to find a complete list of partition ids.rr}r(hlX* to find a complete list of partition ids.hmjubeubjC)r}r(hlUhmjhwhh|jZh~}r(h]h]h]h]h]uhMhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubhn)r}r(hlUhmjYhwhh|h}h~}r (h]h]h]h]r U(viewing-reading-and-writing-to-partitionr ah]r hauhMhhh]r (h)r}r(hlX)Viewing, Reading and Writing to Partitionrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhX)Viewing, Reading and Writing to Partitionrr}r(hljhmjubaubh)r}r(hlXDepending on the filesystem type of the partition will depend on the exact commands to use to read and write to the partition. The two most common partitions are FAT32, EXT2 and EXT4. Luckily the commands to view, read and write to the partition all look the same. Viewing partition uses ls, reading files is load and writing files is write. Replace with fat, ext2 and ext4 depending on the filesystem type.rhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXDepending on the filesystem type of the partition will depend on the exact commands to use to read and write to the partition. The two most common partitions are FAT32, EXT2 and EXT4. Luckily the commands to view, read and write to the partition all look the same. Viewing partition uses ls, reading files is load and writing files is write. Replace with fat, ext2 and ext4 depending on the filesystem type.rr}r(hljhmjubaubeubhn)r}r(hlUhmjYhwhh|h}h~}r (h]h]h]h]r!Uview-partition-contentsr"ah]r#hauhMhhh]r$(h)r%}r&(hlXView Partition Contentsr'hmjhwhh|hh~}r((h]h]h]h]h]uhMhhh]r)hXView Partition Contentsr*r+}r,(hlj'hmj%ubaubh)r-}r.(hlX[To view the contents of a FAT32 partition the user would use "fatls scsi :"r/hmjhwhh|hh~}r0(h]h]h]h]h]uhMhhh]r1hX[To view the contents of a FAT32 partition the user would use "fatls scsi :"r2r3}r4(hlj/hmj-ubaubh)r5}r6(hlXZBelow command list the contents of SCSI device 0 partition 1 on AM57x General Purpose EVM:r7hmjhwhh|hh~}r8(h]h]h]h]h]uhMhhh]r9hXZBelow command list the contents of SCSI device 0 partition 1 on AM57x General Purpose EVM:r:r;}r<(hlj7hmj5ubaubjr)r=}r>(hlX6=> fatls scsi 0:1 110578 test 1 file(s), 0 dir(s)hmjhwhh|juh~}r?(hhh]h]h]h]h]uhMhhh]r@hX6=> fatls scsi 0:1 110578 test 1 file(s), 0 dir(s)rArB}rC(hlUhmj=ubaubjC)rD}rE(hlXWrite File to PartitionrFhmjhwhh|jGh~}rG(h]rHUwrite-file-to-partitionrIah]h]h]h]rJhVauhNhhh]rKhXWrite File to PartitionrLrM}rN(hljFhmjDubaubh)rO}rP(hlX"To write a file on a EXT4 partition the user must have first read the file to be written into memory and then also know the size of the file. Luckily U-boot automatically sets the environment variable "filesize" to the filesize of a file that was loaded into memory via U-boot load command.rQhmjhwhh|hh~}rR(h]h]h]h]h]uhMhhh]rShX"To write a file on a EXT4 partition the user must have first read the file to be written into memory and then also know the size of the file. Luckily U-boot automatically sets the environment variable "filesize" to the filesize of a file that was loaded into memory via U-boot load command.rTrU}rV(hljQhmjOubaubh)rW}rX(hlXTo write to a ext4 partition the user would execute the below command: ext4write scsi : rYhmjhwhh|hh~}rZ(h]h]h]h]h]uhMhhh]r[hXTo write to a ext4 partition the user would execute the below command: ext4write scsi : r\r]}r^(hljYhmjWubaubh)r_}r`(hlXIn the above command refers to the address in memory the file has already been loaded into. Absolute filename path must start with / to indicate the root. Filesize is the amount in bytes to be written.rahmjhwhh|hh~}rb(h]h]h]h]h]uhMhhh]rchXIn the above command refers to the address in memory the file has already been loaded into. Absolute filename path must start with / to indicate the root. Filesize is the amount in bytes to be written.rdre}rf(hljahmj_ubaubh)rg}rh(hlXdBelow is an example of writing the file "tester" previously loaded into memory onto a EXT4 partitionrihmjhwhh|hh~}rj(h]h]h]h]h]uhMhhh]rkhXdBelow is an example of writing the file "tester" previously loaded into memory onto a EXT4 partitionrlrm}rn(hljihmjgubaubjr)ro}rp(hlX=> ext4write scsi 0:3 ${loadaddr} /tester ${filesize} File System is consistent update journal finished 110578 bytes written in 2650 ms (40 KiB/s)hmjhwhh|juh~}rq(hhh]h]h]h]h]uhMhhh]rrhX=> ext4write scsi 0:3 ${loadaddr} /tester ${filesize} File System is consistent update journal finished 110578 bytes written in 2650 ms (40 KiB/s)rsrt}ru(hlUhmjoubaubjC)rv}rw(hlUhmjhwhh|jZh~}rx(h]h]h]h]h]uhMhhh]ryjH)rz}r{(hlUjLKhmjvhwhh|hh~}r|(h]h]h]h]h]uhKhhh]ubaubeubeubhn)r}}r~(hlUhmhshwhh|h}h~}r(h]h]h]h]rUufsrah]rh+auhMhhh]r(h)r}r(hlXUFSrhmj}hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXUFSrr}r(hljhmjubaubh)r}r(hlXUniversal Flash Subsystem (UFS) devices show up as scsi devices similar to SATA in the `previous section `__. One additional command to initialize all ufs devices is:hmj}hwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hXWUniversal Flash Subsystem (UFS) devices show up as scsi devices similar to SATA in the rr}r(hlXWUniversal Flash Subsystem (UFS) devices show up as scsi devices similar to SATA in the hmjubh)r}r(hlX?`previous section `__h~}r(UnameXprevious sectionhX(Foundational_Components_U-Boot.html#satah]h]h]h]h]uhmjh]rhXprevious sectionrr}r(hlUhmjubah|hubhX:. One additional command to initialize all ufs devices is:rr}r(hlX:. One additional command to initialize all ufs devices is:hmjubeubcdocutils.nodes definition_list r)r}r(hlUhmj}hwhh|Udefinition_listrh~}r(h]h]h]h]h]uhNhhh]rcdocutils.nodes definition_list_item r)r}r(hlXr:: => ufs init Device at ufs@4e84000 up at:[RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2 hmjhwhh|Udefinition_list_itemrh~}r(h]h]h]h]h]uhMh]r(cdocutils.nodes term r)r}r(hlX::rhmjhwhh|Utermrh~}r(h]h]h]h]h]uhMh]rhX::rr}r(hljhmjubaubcdocutils.nodes definition r)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXn=> ufs init Device at ufs@4e84000 up at:[RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2hmjhwhh|hh~}r(h]h]h]h]h]uhMh]r(hX=> ufs init Device at rr}r(hlX=> ufs init Device at hmjubh)r}r(hlX ufs@4e84000h~}r(UrefuriXmailto:ufs@4e84000h]h]h]h]h]uhmjh]rhX ufs@4e84000rr}r(hlUhmjubah|hubhXM up at:[RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2rr}r(hlXM up at:[RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2hmjubeubah|U definitionrubeubaubjC)r}r(hlUhmj}hwhh|jZh~}r(h]h]h]h]h]uhMhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubh)r}r(hlXBThen we can go ahead with 'scsi scan' to see the attached devices:rhmj}hwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXBThen we can go ahead with 'scsi scan' to see the attached devices:rr}r(hljhmjubaubjr)r}r(hlXQ => scsi scan scanning bus for devices... Device 0: (0:0) Vendor: TOSHIBA Prod.: THGAF8G8T23BAILB Rev: 0300 Type: Hard Disk Capacity: 31.9 MB = 0.0 GB (8191 x 4096) Device 0: (0:1) Vendor: TOSHIBA Prod.: THGAF8G8T23BAILB Rev: 0300 Type: Hard Disk Capacity: 30499.9 MB = 29.7 GB (7807999 x 4096)hmj}hwhh|juh~}r(hhh]h]h]h]h]uhMhhh]rhXQ => scsi scan scanning bus for devices... Device 0: (0:0) Vendor: TOSHIBA Prod.: THGAF8G8T23BAILB Rev: 0300 Type: Hard Disk Capacity: 31.9 MB = 0.0 GB (8191 x 4096) Device 0: (0:1) Vendor: TOSHIBA Prod.: THGAF8G8T23BAILB Rev: 0300 Type: Hard Disk Capacity: 30499.9 MB = 29.7 GB (7807999 x 4096)rr}r(hlUhmjubaubjC)r}r(hlUhmj}hwhh|jZh~}r(h]h]h]h]h]uhMhhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubh)r}r(hlXAll the remaining scsi commands detailed in the `previous section `__ are also applicable.hmj}hwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hX0All the remaining scsi commands detailed in the rr}r(hlX0All the remaining scsi commands detailed in the hmjubh)r}r(hlX?`previous section `__h~}r(UnameXprevious sectionhX(Foundational_Components_U-Boot.html#satah]h]h]h]h]uhmjh]rhXprevious sectionrr}r(hlUhmjubah|hubhX are also applicable.rr}r(hlX are also applicable.hmjubeubh)r}r(hlXjFor more information about UFS see `Kernel UFS Guide `__.hmj}hwhh|hh~}r(h]h]h]h]h]uhMhhh]r(hX#For more information about UFS see rr}r(hlX#For more information about UFS see hmjubh)r}r(hlXF`Kernel UFS Guide `__h~}r(UnameXKernel UFS GuidehX/Foundational_Components_Kernel_Drivers.html#ufsh]h]h]h]h]uhmjh]rhXKernel UFS Guiderr}r(hlUhmjubah|hubhX.r}r(hlX.hmjubeubeubhn)r}r (hlUhmhshwhh|h}h~}r (h]h]h]h]r Uddr3-eccr ah]r hDauhMhhh]r(h)r}r(hlXDDR3 ECCrhmjhwhh|hh~}r(h]h]h]h]h]uhMhhh]rhXDDR3 ECCrr}r(hljhmjubaubj)r}r(hlXDDDR3 ECC feature described below is enabled for Keystone-II devices.rhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhMh]rhXDDDR3 ECC feature described below is enabled for Keystone-II devices.r r!}r"(hljhmjubaubaubhn)r#}r$(hlUhmjhwhh|h}h~}r%(h]h]h]h]r&Uddr3-ecc-in-keystone-iir'ah]r(hPauhMhhh]r)(h)r*}r+(hlXDDR3 ECC in Keystone-IIr,hmj#hwhh|hh~}r-(h]h]h]h]h]uhMhhh]r.hXDDR3 ECC in Keystone-IIr/r0}r1(hlj,hmj*ubaubh)r2}r3(hlXtSome of the TI SoC devices have DDR ECC enabled. Keystone-II devices (K2H/K2E/K2G) enable the DDR3 error detection and correction feature. The DDR3 controller supports ECC on the data written or read from the SDRAM and is enabled by programming the ECC Control register. 8-bit ECC is calculated over 64-bit data quanta for K2H and K2E, but 4-bit ECC over 32-bit data for K2G. The ECC is calculated for all accesses that are within the address ranges protected by ECC. 1-bit error is correctable by ECC and 2-bit error is not correctable and will be treated as unrecoverable error by software and trigger the reset of the device.r4hmj#hwhh|hh~}r5(h]h]h]h]h]uhMhhh]r6hXtSome of the TI SoC devices have DDR ECC enabled. Keystone-II devices (K2H/K2E/K2G) enable the DDR3 error detection and correction feature. The DDR3 controller supports ECC on the data written or read from the SDRAM and is enabled by programming the ECC Control register. 8-bit ECC is calculated over 64-bit data quanta for K2H and K2E, but 4-bit ECC over 32-bit data for K2G. The ECC is calculated for all accesses that are within the address ranges protected by ECC. 1-bit error is correctable by ECC and 2-bit error is not correctable and will be treated as unrecoverable error by software and trigger the reset of the device.r7r8}r9(hlj4hmj2ubaubhn)r:}r;(hlUhmj#hwhh|h}h~}r<(h]h]h]h]r=Uddr3-ecc-handlingr>ah]r?hXauhM hhh]r@(h)rA}rB(hlXDDR3 ECC HandlingrChmj:hwhh|hh~}rD(h]h]h]h]h]uhM hhh]rEhXDDR3 ECC HandlingrFrG}rH(hljChmjAubaubh)rI}rJ(hlXKeystone-II U-boot checks if the DDR3 controller supports ECC RMW or not. If ECC RMW is not supported (in K2H PG1.x devices), U-boot will disable the ECC by default, otherwise it always enables ECC (in K2H PG2.0, K2E, and K2G devices)rKhmj:hwhh|hh~}rL(h]h]h]h]h]uhM hhh]rMhXKeystone-II U-boot checks if the DDR3 controller supports ECC RMW or not. If ECC RMW is not supported (in K2H PG1.x devices), U-boot will disable the ECC by default, otherwise it always enables ECC (in K2H PG2.0, K2E, and K2G devices)rNrO}rP(hljKhmjIubaubh)rQ}rR(hlXDuring the ECC initialization, U-boot fills the entire memory (up to 8GB) to zeros using an EDMA channel after ECC is enabled. For K2H device, U-boot configures the chip level interrupt controller to route the DDR3 ECC error interrupt to ARM interrupt controller. For K2E and K2G devices, since DDR3 ECC error interrupt is directly routed to ARM interrupt controller, there is no need to configure the chip level interrupt controller.rShmj:hwhh|hh~}rT(h]h]h]h]h]uhM hhh]rUhXDuring the ECC initialization, U-boot fills the entire memory (up to 8GB) to zeros using an EDMA channel after ECC is enabled. For K2H device, U-boot configures the chip level interrupt controller to route the DDR3 ECC error interrupt to ARM interrupt controller. For K2E and K2G devices, since DDR3 ECC error interrupt is directly routed to ARM interrupt controller, there is no need to configure the chip level interrupt controller.rVrW}rX(hljShmjQubaubh)rY}rZ(hlXA DDR3 command is added to simulate the ECC error by generating bit errors in DDR data at certain address. The command format is:r[hmj:hwhh|hh~}r\(h]h]h]h]h]uhM hhh]r]hXA DDR3 command is added to simulate the ECC error by generating bit errors in DDR data at certain address. The command format is:r^r_}r`(hlj[hmjYubaubjr)ra}rb(hlX*ddr ecc_err hmj:hwhh|juh~}rc(hhh]h]h]h]h]uhM hhh]rdhX*ddr ecc_err rerf}rg(hlUhmjaubaubh)rh}ri(hlXZThe command will read a 32-bit data from , and write (data ^ bit_err) back to rjhmj:hwhh|hh~}rk(h]h]h]h]h]uhM hhh]rlhXZThe command will read a 32-bit data from , and write (data ^ bit_err) back to rmrn}ro(hljjhmjhubaubjr)rp}rq(hlXE.g.: ddr ecc_err 0x90000000 0x1 (this will genereate a 1-bit error on bit 0 of the data in ddr address 0x9000_0000) ddr ecc_err 0xa0000000 0x1001 (this will genereate 2-bit error on bit 0 & 3 of the data in ddr address 0xa000_0000)hmj:hwhh|juh~}rr(hhh]h]h]h]h]uhM& hhh]rshXE.g.: ddr ecc_err 0x90000000 0x1 (this will genereate a 1-bit error on bit 0 of the data in ddr address 0x9000_0000) ddr ecc_err 0xa0000000 0x1001 (this will genereate 2-bit error on bit 0 & 3 of the data in ddr address 0xa000_0000)rtru}rv(hlUhmjpubaubh)rw}rx(hlX(A new environment variable "ecc_test" is also introduced to test ECC. By default, ecc_test = 0, and any detection of 2-bit error will reset the device. If ecc_test = 1, U-boot will bypass the error and continues to boot Linux kernel so that Linux kernel can handle the error in interrupt service.ryhmj:hwhh|hh~}rz(h]h]h]h]h]uhM hhh]r{hX(A new environment variable "ecc_test" is also introduced to test ECC. By default, ecc_test = 0, and any detection of 2-bit error will reset the device. If ecc_test = 1, U-boot will bypass the error and continues to boot Linux kernel so that Linux kernel can handle the error in interrupt service.r|r}}r~(hljyhmjwubaubj)r}r(hlX**DDR3 ECC Handling in Keystone-II Linux kernel** Linux kernel requests an IRQ handler for DDR3 ECC error interrupt, the handler checks the DDR3 controller interrupt status register, if the error is 2-bit error, Linux kernel will reboot the device. User can also use a user mode command to read the DDR3 ECC registers (e.g. 1-bit error count register, etc.), the DDR3 controller register and interrupt mapping are defined in the sysctrl node of device tree binding:hmj:hwhh|jh~}r(h]h]h]h]h]uhNhhh]r(h)r}r(hlX1**DDR3 ECC Handling in Keystone-II Linux kernel**rhmjhwhh|hh~}r(h]h]h]h]h]uhM" h]rj)r}r(hljh~}r(h]h]h]h]h]uhmjh]rhX-DDR3 ECC Handling in Keystone-II Linux kernelrr}r(hlUhmjubah|j'ubaubh)r}r(hlXLinux kernel requests an IRQ handler for DDR3 ECC error interrupt, the handler checks the DDR3 controller interrupt status register, if the error is 2-bit error, Linux kernel will reboot the device. User can also use a user mode command to read the DDR3 ECC registers (e.g. 1-bit error count register, etc.), the DDR3 controller register and interrupt mapping are defined in the sysctrl node of device tree binding:rhmjhwhh|hh~}r(h]h]h]h]h]uhM$ h]rhXLinux kernel requests an IRQ handler for DDR3 ECC error interrupt, the handler checks the DDR3 controller interrupt status register, if the error is 2-bit error, Linux kernel will reboot the device. User can also use a user mode command to read the DDR3 ECC registers (e.g. 1-bit error count register, etc.), the DDR3 controller register and interrupt mapping are defined in the sysctrl node of device tree binding:rr}r(hljhmjubaubeubjr)r}r(hlXE.g. K2H SOC device tree: sysctrl { reg = <0x21010000 0x0200>; /* DDR3 controller reg */ interrupts = <0 24 0xf01 /* L1L2 ECC error interrupt */ 0 448 0xf01>; /* DDR3 ECC error interrupt */ };hmj:hwhh|juh~}r(hhh]h]h]h]h]uhM6 hhh]rhXE.g. K2H SOC device tree: sysctrl { reg = <0x21010000 0x0200>; /* DDR3 controller reg */ interrupts = <0 24 0xf01 /* L1L2 ECC error interrupt */ 0 448 0xf01>; /* DDR3 ECC error interrupt */ };rr}r(hlUhmjubaubjC)r}r(hlUhmj:hwhh|jZh~}r(h]h]h]h]h]uhM2 hhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubeubeubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUhyperbus-and-hyperflashrah]rhIauhM5 hhh]r(h)r}r(hlXHyperBus and HyperFlashrhmjhwhh|hh~}r(h]h]h]h]h]uhM5 hhh]rhXHyperBus and HyperFlashrr}r(hljhmjubaubh)r}r(hlXHyperBus is Low Signal Count, High Performance Double Data Rate (DDR) Bus interface between a host system master and one or more slave interfaces. Its a 8-bit data bus (DQ[7:0]) with Read-Write Data Strobe (RWDS) signal and either Single-ended clock(3.0V parts) or Differential clock (1.8V parts). It uses ChipSelect lines to select b/w multiple slaves. At bus level, it follows a separate protocol described in HyperBus specification.rhmjhwhh|hh~}r(h]h]h]h]h]uhM6 hhh]rhXHyperBus is Low Signal Count, High Performance Double Data Rate (DDR) Bus interface between a host system master and one or more slave interfaces. Its a 8-bit data bus (DQ[7:0]) with Read-Write Data Strobe (RWDS) signal and either Single-ended clock(3.0V parts) or Differential clock (1.8V parts). It uses ChipSelect lines to select b/w multiple slaves. At bus level, it follows a separate protocol described in HyperBus specification.rr}r(hljhmjubaubh)r}r(hlX3HyperFlash is a NOR flash based device storage over HyperBus. HyperFlash follows CFI AMD/Fujitsu Extended Command Set (0x0002) similar to that of existing parallel NORs. Since Hyperbus is x8 DDR bus, its equivalent to x16 parallel NOR flash wrt bits per clk. But Hyperbus operates at very high frequencies.rhmjhwhh|hh~}r(h]h]h]h]h]uhM8 hhh]rhX3HyperFlash is a NOR flash based device storage over HyperBus. HyperFlash follows CFI AMD/Fujitsu Extended Command Set (0x0002) similar to that of existing parallel NORs. Since Hyperbus is x8 DDR bus, its equivalent to x16 parallel NOR flash wrt bits per clk. But Hyperbus operates at very high frequencies.rr}r(hljhmjubaubh)r}r(hlXHyperFlash on TI's J721E EVM is connected to HyperBus Memory Controller that supports memory mapped IO access to flash. HyperFlash is supported under MTD framework and U-Boot's standard MTD commands can be used to access HyperFlashrhmjhwhh|hh~}r(h]h]h]h]h]uhM: hhh]rhXHyperFlash on TI's J721E EVM is connected to HyperBus Memory Controller that supports memory mapped IO access to flash. HyperFlash is supported under MTD framework and U-Boot's standard MTD commands can be used to access HyperFlashrr}r(hljhmjubaubh)r}r(hlX!**Supported Devices** - J721E EVMhmjhwhh|hh~}r(h]h]h]h]h]uhM< hhh]r(j)r}r(hlX**Supported Devices**h~}r(h]h]h]h]h]uhmjh]rhXSupported Devicesrr}r(hlUhmjubah|j'ubhX - J721E EVMrr}r(hlX - J721E EVMhmjubeubh)r}r(hlX$To list detected HyperFlash devices:rhmjhwhh|hh~}r(h]h]h]h]h]uhM? hhh]rhX$To list detected HyperFlash devices:rr}r(hljhmjubaubjr)r}r(hlX=> mtd list List of MTD devices: * nor0 - type: NOR flash - block size: 0x40000 bytes /* Each erase sector size is of 256KB */ - min I/O: 0x1 bytes - 0x000000000000-0x000004000000 : "nor0" /* Detected 64MB devices labeled as "nor0" */hmjhwhh|juh~}r(hhh]h]h]h]h]uhMN hhh]rhX=> mtd list List of MTD devices: * nor0 - type: NOR flash - block size: 0x40000 bytes /* Each erase sector size is of 256KB */ - min I/O: 0x1 bytes - 0x000000000000-0x000004000000 : "nor0" /* Detected 64MB devices labeled as "nor0" */rr}r(hlUhmjubaubj)r}r(hlXFOn J721E EVM, SW3.1 should be set to ON position to select HyperFlash.rhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhMM h]rhXFOn J721E EVM, SW3.1 should be set to ON position to select HyperFlash.rr}r(hljhmjubaubaubh)r}r(hlXBelow Example shows how to erase and write different boot images to HyperFlash from U-Boot prompt. Erase has to be a multiple of erase sector size. ::hmjhwhh|hh~}r(h]h]h]h]h]uhMO hhh]rhXBelow Example shows how to erase and write different boot images to HyperFlash from U-Boot prompt. Erase has to be a multiple of erase sector size.rr}r(hlXBelow Example shows how to erase and write different boot images to HyperFlash from U-Boot prompt. Erase has to be a multiple of erase sector size.hmjubaubjr)r}r(hlX=> mtd erase nor0 0 0x40000 /* Erase from offset 0 to 256KB of HyperFlash labeled nor0 */ Erasing 0x00000000 ... 0x0003ffff (1 eraseblock(s)) => fatload mmc 1 0x82000000 tiboot3.bin /* Load an img from SD into DDR to flash into HyperFlash */ 180932 bytes read in 10 ms (17.3 MiB/s) => mtd write nor0 0x82000000 0x0 $filesize /* Write the loaded image into HyperFlash labeled nor0 */ Writing 180932 byte(s) at offset 0x00000000 =>hmjhwhh|juh~}r(hhh]h]h]h]h]uhM^ hhh]rhX=> mtd erase nor0 0 0x40000 /* Erase from offset 0 to 256KB of HyperFlash labeled nor0 */ Erasing 0x00000000 ... 0x0003ffff (1 eraseblock(s)) => fatload mmc 1 0x82000000 tiboot3.bin /* Load an img from SD into DDR to flash into HyperFlash */ 180932 bytes read in 10 ms (17.3 MiB/s) => mtd write nor0 0x82000000 0x0 $filesize /* Write the loaded image into HyperFlash labeled nor0 */ Writing 180932 byte(s) at offset 0x00000000 =>rr}r(hlUhmjubaubh)r}r(hlX-Below Example shows how to read back the datarhmjhwhh|hh~}r(h]h]h]h]h]uhM[ hhh]rhX-Below Example shows how to read back the datarr }r (hljhmjubaubjr)r }r (hlX=> mtd read nor0 0x82000000 0x0 0x40000 /* Read from offset 0 to 0x4000 to DDR address 0x82000000 from nor0 */ Reading 262144 byte(s) at offset 0x00000000hmjhwhh|juh~}r (hhh]h]h]h]h]uhMj hhh]rhX=> mtd read nor0 0x82000000 0x0 0x40000 /* Read from offset 0 to 0x4000 to DDR address 0x82000000 from nor0 */ Reading 262144 byte(s) at offset 0x00000000rr}r(hlUhmj ubaubh)r}r(hlX!**Flashing Images to HyperFlash**rhmjhwhh|hh~}r(h]h]h]h]h]uhMb hhh]rj)r}r(hljh~}r(h]h]h]h]h]uhmjh]rhXFlashing Images to HyperFlashrr}r(hlUhmjubah|j'ubaubh)r}r(hlXBelow commands can be used to download tiboot3.bin, tispl.bin and u-boot.img over tftp and then flash it to HyperFlash at respective addresses.r hmjhwhh|hh~}r!(h]h]h]h]h]uhMd hhh]r"hXBelow commands can be used to download tiboot3.bin, tispl.bin and u-boot.img over tftp and then flash it to HyperFlash at respective addresses.r#r$}r%(hlj hmjubaubjr)r&}r'(hlXM=> mtd erase nor0 0 0x800000 => tftp ${loadaddr} tiboot3.bin => mtd write nor0 $loadaddr 0x0 $filesize => tftp ${loadaddr} tispl.bin => mtd write nor0 $loadaddr 0x80000 $filesize => tftp ${loadaddr} u-boot.img => mtd write nor0 $loadaddr 0x280000 $filesize => tftp ${loadaddr} sysfw.itb => mtd write nor0 $loadaddr 0x6C0000 $filesizehmjhwhh|juh~}r((jwjxXconsolehhh]h]h]jy}h]h]uhMg hhh]r)hXM=> mtd erase nor0 0 0x800000 => tftp ${loadaddr} tiboot3.bin => mtd write nor0 $loadaddr 0x0 $filesize => tftp ${loadaddr} tispl.bin => mtd write nor0 $loadaddr 0x80000 $filesize => tftp ${loadaddr} u-boot.img => mtd write nor0 $loadaddr 0x280000 $filesize => tftp ${loadaddr} sysfw.itb => mtd write nor0 $loadaddr 0x6C0000 $filesizer*r+}r,(hlUhmj&ubaubj)r-}r.(hlUhmjhwhh|jh~}r/(h]h]h]h]h]uhNhhh]r0j)r1}r2(hlXe**Flash Layout for HyperFlash** Below is the layout for HyperFlash in order to boot from HyperFlash: hmj-hwhh|jh~}r3(h]h]h]h]h]uhMt h]r4(j)r5}r6(hlX**Flash Layout for HyperFlash**r7hmj1hwhh|jh~}r8(h]h]h]h]h]uhMt h]r9j)r:}r;(hlj7h~}r<(h]h]h]h]h]uhmj5h]r=hXFlash Layout for HyperFlashr>r?}r@(hlUhmj:ubah|j'ubaubj)rA}rB(hlUh~}rC(h]h]h]h]h]uhmj1h]rDh)rE}rF(hlXDBelow is the layout for HyperFlash in order to boot from HyperFlash:rGhmjAhwhh|hh~}rH(h]h]h]h]h]uhMt h]rIhXDBelow is the layout for HyperFlash in order to boot from HyperFlash:rJrK}rL(hljGhmjEubaubah|jubeubaubjr)rM}rN(hlXG 0x0 +----------------------------+ | hbmc.tiboot3(512K) | | | 0x80000 +----------------------------+ | hbmc.tispl(2M) | | | 0x280000 +----------------------------+ | hbmc.u-boot(4M) | | | 0x680000 +----------------------------+ | hbmc.env(128K) | | | 0x6C0000 +----------------------------+ | hbmc.sysfw(1M) | | | 0x7C0000 +----------------------------+ | padding (256k) | 0x800000 +----------------------------+ | hbmc.rootfs(UBIFS) | | | +----------------------------+hmjhwhh|juh~}rO(jwjxXconsolehhh]h]h]jy}h]h]uhMv hhh]rPhXG 0x0 +----------------------------+ | hbmc.tiboot3(512K) | | | 0x80000 +----------------------------+ | hbmc.tispl(2M) | | | 0x280000 +----------------------------+ | hbmc.u-boot(4M) | | | 0x680000 +----------------------------+ | hbmc.env(128K) | | | 0x6C0000 +----------------------------+ | hbmc.sysfw(1M) | | | 0x7C0000 +----------------------------+ | padding (256k) | 0x800000 +----------------------------+ | hbmc.rootfs(UBIFS) | | | +----------------------------+rQrR}rS(hlUhmjMubaubh)rT}rU(hlX***Bootmode Switch Settings for J721E EVM**rVhmjhwhh|hh~}rW(h]h]h]h]h]uhM hhh]rXj)rY}rZ(hljVh~}r[(h]h]h]h]h]uhmjTh]r\hX&Bootmode Switch Settings for J721E EVMr]r^}r_(hlUhmjYubah|j'ubaubh)r`}ra(hlX}After writing the images, change the bootmode switches on the EVM to the following in order to boot from HyperFlash at 83MHz:rbhmjhwhh|hh~}rc(h]h]h]h]h]uhM hhh]rdhX}After writing the images, change the bootmode switches on the EVM to the following in order to boot from HyperFlash at 83MHz:rerf}rg(hljbhmj`ubaubj)rh}ri(hlUhmjhwhh|jh~}rj(h]h]h]h]h]uhNhhh]rkj)rl}rm(hlUh~}rn(h]h]h]h]h]UcolsK uhmjhh]ro(j)rp}rq(hlUh~}rr(h]h]h]h]h]UcolwidthK uhmjlh]h|j"ubj)rs}rt(hlUh~}ru(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)rv}rw(hlUh~}rx(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)ry}rz(hlUh~}r{(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)r|}r}(hlUh~}r~(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)r}r(hlUh~}r(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)r}r(hlUh~}r(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)r}r(hlUh~}r(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)r}r(hlUh~}r(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)r}r(hlUh~}r(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubj)r}r(hlUh~}r(h]h]h]h]h]UcolwidthKuhmjlh]h|j"ubjy)r}r(hlUh~}r(h]h]h]h]h]uhmjlh]r(j4)r}r(hlUh~}r(h]h]h]h]h]uhmjh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX Switch No.rhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX Switch No.rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX1hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX1r}r(hlX1hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX2hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX2r}r(hlX2hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX3hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX3r}r(hlX3hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX4hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX4r}r(hlX4hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX5hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX5r}r(hlX5hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX6hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX6r}r(hlX6hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX7hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX7r}r(hlX7hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX8hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX8r}r(hlX8hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX9hmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX9r}r(hlX9hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlX10rhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhX10rr }r (hljhmjubaubah|jFubeh|jwubj4)r }r (hlUh~}r (h]h]h]h]h]uhmjh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmj h]rh)r}r(hlXSW8rhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXSW8rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmj h]rh)r}r (hlXOFFr!hmjhwhh|hh~}r"(h]h]h]h]h]uhM h]r#hXOFFr$r%}r&(hlj!hmjubaubah|jFubj9)r'}r((hlUh~}r)(h]h]h]h]h]uhmj h]r*h)r+}r,(hlXOFFr-hmj'hwhh|hh~}r.(h]h]h]h]h]uhM h]r/hXOFFr0r1}r2(hlj-hmj+ubaubah|jFubj9)r3}r4(hlUh~}r5(h]h]h]h]h]uhmj h]r6h)r7}r8(hlXOFFr9hmj3hwhh|hh~}r:(h]h]h]h]h]uhM h]r;hXOFFr<r=}r>(hlj9hmj7ubaubah|jFubj9)r?}r@(hlUh~}rA(h]h]h]h]h]uhmj h]rBh)rC}rD(hlXOFFrEhmj?hwhh|hh~}rF(h]h]h]h]h]uhM h]rGhXOFFrHrI}rJ(hljEhmjCubaubah|jFubj9)rK}rL(hlUh~}rM(h]h]h]h]h]uhmj h]rNh)rO}rP(hlXOFFrQhmjKhwhh|hh~}rR(h]h]h]h]h]uhM h]rShXOFFrTrU}rV(hljQhmjOubaubah|jFubj9)rW}rX(hlUh~}rY(h]h]h]h]h]uhmj h]rZh)r[}r\(hlXOFFr]hmjWhwhh|hh~}r^(h]h]h]h]h]uhM h]r_hXOFFr`ra}rb(hlj]hmj[ubaubah|jFubj9)rc}rd(hlUh~}re(h]h]h]h]h]uhmj h]rfh)rg}rh(hlXOFFrihmjchwhh|hh~}rj(h]h]h]h]h]uhM h]rkhXOFFrlrm}rn(hljihmjgubaubah|jFubj9)ro}rp(hlUh~}rq(h]h]h]h]h]uhmj h]rrh)rs}rt(hlXOFFruhmjohwhh|hh~}rv(h]h]h]h]h]uhM h]rwhXOFFrxry}rz(hljuhmjsubaubah|jFubj9)r{}r|(hlUh~}r}(h]h]h]h]h]uhmj h]r~h)r}r(hlXOFFrhmj{hwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmj h]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubeh|jwubj4)r}r(hlUh~}r(h]h]h]h]h]uhmjh]r(j9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXSW9rhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXSW9rr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFr hmjhwhh|hh~}r (h]h]h]h]h]uhM h]r hXOFFr r }r(hlj hmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubeh|jwubj4)r}r(hlUh~}r(h]h]h]h]h]uhmjh]r(j9)r}r (hlUh~}r!(h]h]h]h]h]uhmjh]r"h)r#}r$(hlXSW3r%hmjhwhh|hh~}r&(h]h]h]h]h]uhM h]r'hXSW3r(r)}r*(hlj%hmj#ubaubah|jFubj9)r+}r,(hlUh~}r-(h]h]h]h]h]uhmjh]r.h)r/}r0(hlXONr1hmj+hwhh|hh~}r2(h]h]h]h]h]uhM h]r3hXONr4r5}r6(hlj1hmj/ubaubah|jFubj9)r7}r8(hlUh~}r9(h]h]h]h]h]uhmjh]r:h)r;}r<(hlXONr=hmj7hwhh|hh~}r>(h]h]h]h]h]uhM h]r?hXONr@rA}rB(hlj=hmj;ubaubah|jFubj9)rC}rD(hlUh~}rE(h]h]h]h]h]uhmjh]rFh)rG}rH(hlXONrIhmjChwhh|hh~}rJ(h]h]h]h]h]uhM h]rKhXONrLrM}rN(hljIhmjGubaubah|jFubj9)rO}rP(hlUh~}rQ(h]h]h]h]h]uhmjh]rRh)rS}rT(hlXONrUhmjOhwhh|hh~}rV(h]h]h]h]h]uhM h]rWhXONrXrY}rZ(hljUhmjSubaubah|jFubj9)r[}r\(hlUh~}r](h]h]h]h]h]uhmjh]r^h)r_}r`(hlXOFFrahmj[hwhh|hh~}rb(h]h]h]h]h]uhM h]rchXOFFrdre}rf(hljahmj_ubaubah|jFubj9)rg}rh(hlUh~}ri(h]h]h]h]h]uhmjh]rjh)rk}rl(hlXOFFrmhmjghwhh|hh~}rn(h]h]h]h]h]uhM h]rohXOFFrprq}rr(hljmhmjkubaubah|jFubj9)rs}rt(hlUh~}ru(h]h]h]h]h]uhmjh]rvh)rw}rx(hlXONryhmjshwhh|hh~}rz(h]h]h]h]h]uhM h]r{hXONr|r}}r~(hljyhmjwubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXONrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXONrr}r(hljhmjubaubah|jFubj9)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rh)r}r(hlXOFFrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXOFFrr}r(hljhmjubaubah|jFubeh|jwubeh|jubeh|jubaubeubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rU remoteprocrah]rhLauhM hhh]r(h)r}r(hlX REMOTEPROCrhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhX REMOTEPROCrr}r(hljhmjubaubh)r}r(hlXThis section documents how to initialize, load, start and stop remote cores from U-Boot prompt. Following remotecores support is available in U-boot:rhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXThis section documents how to initialize, load, start and stop remote cores from U-Boot prompt. Following remotecores support is available in U-boot:rr}r(hljhmjubaubj#)r}r(hlUhmjhwhh|j&h~}r(j(X-h]h]h]h]h]uhM hhh]r(j )r}r(hlXCortex-R5F in Lockstep morerhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXCortex-R5F in Lockstep morerr}r(hljhmjubaubaubj )r}r(hlXCortex-R5F in split moderhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXCortex-R5F in split moderr}r(hljhmjubaubaubj )r}r(hlXC66x DSPrhmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hljhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXC66x DSPrr}r(hljhmjubaubaubj )r}r(hlX C71x DSP hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXC71x DSPrhmjhwhh|hh~}r(h]h]h]h]h]uhM h]rhXC71x DSPrr}r(hljhmjubaubaubeubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rUinitializationrah]rhYauhM hhh]r(h)r}r(hlXInitializationrhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXInitializationrr}r(hljhmjubaubh)r}r(hlXU-Boot supports for initializing all the available remotecores in one go or initialize individual core based on the DT alias id.rhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXU-Boot supports for initializing all the available remotecores in one go or initialize individual core based on the DT alias id.rr}r(hljhmjubaubh)r}r(hlXAThe below command will initialize all the available remote cores:rhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]r hXAThe below command will initialize all the available remote cores:r r }r (hljhmjubaubjr)r }r(hlX => rproc inithmjhwhh|juh~}r(hhh]h]h]h]h]uhM hhh]rhX => rproc initrr}r(hlUhmj ubaubh)r}r(hlX<The below command will initialize just the given remote corerhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhX<The below command will initialize just the given remote corerr}r(hljhmjubaubjr)r}r(hlX=> rproc init hmjhwhh|juh~}r(hhh]h]h]h]h]uhM hhh]rhX=> rproc init r r!}r"(hlUhmjubaubh)r#}r$(hlXPThe below command lists all the available/initialized remotecores in the system.r%hmjhwhh|hh~}r&(h]h]h]h]h]uhM hhh]r'hXPThe below command lists all the available/initialized remotecores in the system.r(r)}r*(hlj%hmj#ubaubjr)r+}r,(hlX=> rproc list 0 - Name:'r5f@41000000' type:'internal memory mapped' supports: load start stop reset 1 - Name:'r5f@41400000' type:'internal memory mapped' supports: load start stop reset 2 - Name:'r5f@5c00000' type:'internal memory mapped' supports: load start stop reset 3 - Name:'r5f@5d00000' type:'internal memory mapped' supports: load start stop reset 4 - Name:'r5f@5e00000' type:'internal memory mapped' supports: load start stop reset 5 - Name:'r5f@5f00000' type:'internal memory mapped' supports: load start stop reset 6 - Name:'dsp@4d80800000' type:'internal memory mapped' supports: load start stop reset 7 - Name:'dsp@4d81800000' type:'internal memory mapped' supports: load start stop reset 8 - Name:'dsp@64800000' type:'internal memory mapped' supports: load start stop resethmjhwhh|juh~}r-(hhh]h]h]h]h]uhM hhh]r.hX=> rproc list 0 - Name:'r5f@41000000' type:'internal memory mapped' supports: load start stop reset 1 - Name:'r5f@41400000' type:'internal memory mapped' supports: load start stop reset 2 - Name:'r5f@5c00000' type:'internal memory mapped' supports: load start stop reset 3 - Name:'r5f@5d00000' type:'internal memory mapped' supports: load start stop reset 4 - Name:'r5f@5e00000' type:'internal memory mapped' supports: load start stop reset 5 - Name:'r5f@5f00000' type:'internal memory mapped' supports: load start stop reset 6 - Name:'dsp@4d80800000' type:'internal memory mapped' supports: load start stop reset 7 - Name:'dsp@4d81800000' type:'internal memory mapped' supports: load start stop reset 8 - Name:'dsp@64800000' type:'internal memory mapped' supports: load start stop resetr/r0}r1(hlUhmj+ubaubeubhn)r2}r3(hlUhmjhwhh|h}h~}r4(h]h]h]h]r5Uloadingr6ah]r7hauhM hhh]r8(h)r9}r:(hlXLoadingr;hmj2hwhh|hh~}r<(h]h]h]h]h]uhM hhh]r=hXLoadingr>r?}r@(hlj;hmj9ubaubh)rA}rB(hlX~Once Initialized, remotecores can be loaded with a relevant image. Make sure image is loaded only after initializing the core.rChmj2hwhh|hh~}rD(h]h]h]h]h]uhM hhh]rEhX~Once Initialized, remotecores can be loaded with a relevant image. Make sure image is loaded only after initializing the core.rFrG}rH(hljChmjAubaubjr)rI}rJ(hlX=> load mmc 1:2 0x90000000 /lib/firmware/j7-main-r5f0_0-fw 2536540 bytes read in 112 ms (21.6 MiB/s) => rproc load 2 0x90000000 0x${filesize} Load Remote Processor 2 with data@addr=0x90000000 2536540 bytes: Success!hmj2hwhh|juh~}rK(hhh]h]h]h]h]uhM hhh]rLhX=> load mmc 1:2 0x90000000 /lib/firmware/j7-main-r5f0_0-fw 2536540 bytes read in 112 ms (21.6 MiB/s) => rproc load 2 0x90000000 0x${filesize} Load Remote Processor 2 with data@addr=0x90000000 2536540 bytes: Success!rMrN}rO(hlUhmjIubaubeubhn)rP}rQ(hlUhmjhwhh|h}h~}rR(h]h]h]h]rSUstartingrTah]rUhdauhM hhh]rV(h)rW}rX(hlXStartingrYhmjPhwhh|hh~}rZ(h]h]h]h]h]uhM hhh]r[hXStartingr\r]}r^(hljYhmjWubaubh)r_}r`(hlXJSuccessfully loaded remotecore can be started using the following command.rahmjPhwhh|hh~}rb(h]h]h]h]h]uhM hhh]rchXJSuccessfully loaded remotecore can be started using the following command.rdre}rf(hljahmj_ubaubjr)rg}rh(hlX=> rproc start 2hmjPhwhh|juh~}ri(hhh]h]h]h]h]uhM hhh]rjhX=> rproc start 2rkrl}rm(hlUhmjgubaubeubhn)rn}ro(hlUhmjhwhh|h}h~}rp(h]h]h]h]rqUstoprrah]rshauhM hhh]rt(h)ru}rv(hlXStoprwhmjnhwhh|hh~}rx(h]h]h]h]h]uhM hhh]ryhXStoprzr{}r|(hljwhmjuubaubh)r}}r~(hlX@A running remotecore can be stopped using the following command.rhmjnhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhX@A running remotecore can be stopped using the following command.rr}r(hljhmj}ubaubjr)r}r(hlX=> rproc stop 2hmjnhwhh|juh~}r(hhh]h]h]h]h]uhM hhh]rhX=> rproc stop 2rr}r(hlUhmjubaubh)r}r(hlXiMake sure all the commands are run in the above given sequence. Currently IPC is not supported in U-boot.rhmjnhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXiMake sure all the commands are run in the above given sequence. Currently IPC is not supported in U-boot.rr}r(hljhmjubaubjC)r}r(hlUhmjnhwhh|jZh~}r(h]h]h]h]h]uhM hhh]rjH)r}r(hlUjLKhmjhwhh|hh~}r(h]h]h]h]h]uhKhhh]ubaubeubeubhn)r}r(hlUhmhshwhh|h}h~}r(h]h]h]h]rUuboot-spl-debugging-tipsrah]rh6auhM hhh]r(h)r}r(hlXUboot SPL Debugging Tipsrhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXUboot SPL Debugging Tipsrr}r(hljhmjubaubh)r}r(hlXThe following section demonstrates how to connect a board to CCS and load the SPL symbols for debugging. For the experiment below, users are expected to boot their board from a SD card.rhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXThe following section demonstrates how to connect a board to CCS and load the SPL symbols for debugging. For the experiment below, users are expected to boot their board from a SD card.rr}r(hljhmjubaubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rUstep-1-downloading-ccsrah]rhauhM hhh]r(h)r}r(hlXStep 1: Downloading CCSrhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXStep 1: Downloading CCSrr}r(hljhmjubaubj)r}r(hlUhmjhwhh|jh~}r(jU.h]h]h]j Uh]h]j j uhM hhh]rj )r}r(hlXpPlease download the CCS from the following link: http://software-dl.ti.com/ccs/esd/documents/ccs_downloads.html hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXoPlease download the CCS from the following link: http://software-dl.ti.com/ccs/esd/documents/ccs_downloads.htmlhmjhwhh|hh~}r(h]h]h]h]h]uhM h]r(hX1Please download the CCS from the following link: rr}r(hlX1Please download the CCS from the following link: hmjubh)r}r(hlX>http://software-dl.ti.com/ccs/esd/documents/ccs_downloads.htmlrh~}r(Urefurijh]h]h]h]h]uhmjh]rhX>http://software-dl.ti.com/ccs/esd/documents/ccs_downloads.htmlrr}r(hlUhmjubah|hubeubaubaubh)r}r(hlXY**NOTE**: We will be building Uboot on a Linux machine and it is recommended to install CCS on the same operating system (OS). If CCS is not installed on the same OS, CCS will not be able to locate the code files. Please follow the Linux instructions on the following link: http://software-dl.ti.com/ccs/esd/documents/ccs_linux_host_support.htmlrhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]r(j)r}r(hlX**NOTE**h~}r(h]h]h]h]h]uhmjh]rhXNOTErr}r(hlUhmjubah|j'ubhX : We will be building Uboot on a Linux machine and it is recommended to install CCS on the same operating system (OS). If CCS is not installed on the same OS, CCS will not be able to locate the code files. Please follow the Linux instructions on the following link: rr}r(hlX : We will be building Uboot on a Linux machine and it is recommended to install CCS on the same operating system (OS). If CCS is not installed on the same OS, CCS will not be able to locate the code files. Please follow the Linux instructions on the following link: hmjubh)r}r(hlXGhttp://software-dl.ti.com/ccs/esd/documents/ccs_linux_host_support.htmlrh~}r(Urefurijh]h]h]h]h]uhmjh]rhXGhttp://software-dl.ti.com/ccs/esd/documents/ccs_linux_host_support.htmlrr}r(hlUhmjubah|hubeubeubhn)r}r(hlUhmjhwhh|h}h~}r(h]h]h]h]rU+step-2-creating-a-target-configuration-filerah]rh_auhM hhh]r(h)r}r(hlX,Step 2: Creating a Target Configuration Filerhmjhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhX,Step 2: Creating a Target Configuration Filerr}r(hljhmjubaubj)r}r(hlUhmjhwhh|jh~}r(jU.h]h]h]j Uh]h]j j uhM hhh]r(j )r}r(hlXThe first step is to create a target configuration file in CCS. Navigate to "View"-> "Target Configurations": .. Image:: ../images/Uboot_Image1.pnghmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]r(h)r}r(hlXmThe first step is to create a target configuration file in CCS. Navigate to "View"-> "Target Configurations":rhmjhwhh|hh~}r (h]h]h]h]h]uhM h]r hXmThe first step is to create a target configuration file in CCS. Navigate to "View"-> "Target Configurations":r r }r (hljhmjubaubj>)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rcdocutils.nodes image r)r}r(hlX%.. Image:: ../images/Uboot_Image1.pngh~}r(UuriX linux/../images/Uboot_Image1.pngrh]h]h]h]U candidatesr}rU*jsh]uhmjh]h|Uimagerubah|j[ubeubj )r}r(hlXRight click on the "Target Configurations" window and select "New Target Configuration": .. Image:: ../images/Uboot_Image2.pnghmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]r(h)r}r(hlXXRight click on the "Target Configurations" window and select "New Target Configuration":r hmjhwhh|hh~}r!(h]h]h]h]h]uhM h]r"hXXRight click on the "Target Configurations" window and select "New Target Configuration":r#r$}r%(hlj hmjubaubj>)r&}r'(hlUh~}r((h]h]h]h]h]uhmjh]r)j)r*}r+(hlX%.. Image:: ../images/Uboot_Image2.pngh~}r,(UuriX linux/../images/Uboot_Image2.pngr-h]h]h]h]j}r.U*j-sh]uhmj&h]h|jubah|j[ubeubj )r/}r0(hlXSCreate a name for target configuration: .. Image:: ../images/Uboot_Image3.pnghmjhwhh|jh~}r1(h]h]h]h]h]uhNhhh]r2(h)r3}r4(hlX'Create a name for target configuration:r5hmj/hwhh|hh~}r6(h]h]h]h]h]uhM h]r7hX'Create a name for target configuration:r8r9}r:(hlj5hmj3ubaubj>)r;}r<(hlUh~}r=(h]h]h]h]h]uhmj/h]r>j)r?}r@(hlX%.. Image:: ../images/Uboot_Image3.pngh~}rA(UuriX linux/../images/Uboot_Image3.pngrBh]h]h]h]j}rCU*jBsh]uhmj;h]h|jubah|j[ubeubj )rD}rE(hlXSelect the appropriate SoC and JTAG. **Note**: If we select the SoC name, the GEL files will not be loaded. However, if we select the board options, the GEL files will be loaded by default. In the below example, if GPEVM_AM65x or IDK_AM65x is selected, the GEL files are automatically enabled in the configuration. While debugging Uboot, it is recommended to avoid GEL files because Uboot is responsible for initializing the peripherals: .. Image:: ../images/Uboot_Image4.pnghmjhwhh|jh~}rF(h]h]h]h]h]uhNhhh]rG(h)rH}rI(hlXSelect the appropriate SoC and JTAG. **Note**: If we select the SoC name, the GEL files will not be loaded. However, if we select the board options, the GEL files will be loaded by default. In the below example, if GPEVM_AM65x or IDK_AM65x is selected, the GEL files are automatically enabled in the configuration. While debugging Uboot, it is recommended to avoid GEL files because Uboot is responsible for initializing the peripherals:hmjDhwhh|hh~}rJ(h]h]h]h]h]uhM h]rK(hX%Select the appropriate SoC and JTAG. rLrM}rN(hlX%Select the appropriate SoC and JTAG. hmjHubj)rO}rP(hlX**Note**h~}rQ(h]h]h]h]h]uhmjHh]rRhXNoterSrT}rU(hlUhmjOubah|j'ubhX: If we select the SoC name, the GEL files will not be loaded. However, if we select the board options, the GEL files will be loaded by default. In the below example, if GPEVM_AM65x or IDK_AM65x is selected, the GEL files are automatically enabled in the configuration. While debugging Uboot, it is recommended to avoid GEL files because Uboot is responsible for initializing the peripherals:rVrW}rX(hlX: If we select the SoC name, the GEL files will not be loaded. However, if we select the board options, the GEL files will be loaded by default. In the below example, if GPEVM_AM65x or IDK_AM65x is selected, the GEL files are automatically enabled in the configuration. While debugging Uboot, it is recommended to avoid GEL files because Uboot is responsible for initializing the peripherals:hmjHubeubj>)rY}rZ(hlUh~}r[(h]h]h]h]h]uhmjDh]r\j)r]}r^(hlX%.. Image:: ../images/Uboot_Image4.pngh~}r_(UuriX linux/../images/Uboot_Image4.pngr`h]h]h]h]j}raU*j`sh]uhmjYh]h|jubah|j[ubeubj )rb}rc(hlXNext, click save and test connection to ensure CCS is able to communicate with the debugger: .. Image:: ../images/Uboot_Image5.png hmjhwhh|jh~}rd(h]h]h]h]h]uhNhhh]re(h)rf}rg(hlX\Next, click save and test connection to ensure CCS is able to communicate with the debugger:rhhmjbhwhh|hh~}ri(h]h]h]h]h]uhM h]rjhX\Next, click save and test connection to ensure CCS is able to communicate with the debugger:rkrl}rm(hljhhmjfubaubj>)rn}ro(hlUh~}rp(h]h]h]h]h]uhmjbh]rqj)rr}rs(hlX&.. Image:: ../images/Uboot_Image5.png h~}rt(UuriX linux/../images/Uboot_Image5.pngruh]h]h]h]j}rvU*jush]uhmjnh]h|jubah|j[ubeubeubeubhn)rw}rx(hlUhmjhwhh|h}h~}ry(h]h]h]h]rzUstep-3-loading-symbol-filesr{ah]r|hauhM hhh]r}(h)r~}r(hlXStep 3: Loading Symbol filesrhmjwhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXStep 3: Loading Symbol filesrr}r(hljhmj~ubaubh)r}r(hlXBefore the symbols are loaded, a test code will be added to the SPL code. The test code will loop within itself and the only way to break the loop is to change the Program Counter via the CCS. For the current experiment, the AM65EVM is used but the same experiment could be performed on other boards. The following test code is added to the "board_init_f" function in the file /board-support//arch/arm/mach-k3/am6_init.c:rhmjwhwhh|hh~}r(h]h]h]h]h]uhM hhh]rhXBefore the symbols are loaded, a test code will be added to the SPL code. The test code will loop within itself and the only way to break the loop is to change the Program Counter via the CCS. For the current experiment, the AM65EVM is used but the same experiment could be performed on other boards. The following test code is added to the "board_init_f" function in the file /board-support//arch/arm/mach-k3/am6_init.c:rr}r(hljhmjubaubjr)r}r(hlXstore_boot_index_from_rom(); /* Make all control module registers accessible */ ctrl_mmr_unlock(); asm("test: nop"); asm(" nop"); asm(" b test "); asm(" nop"); asm(" nop"); setup_am654_navss_northbridge();hmjwhwhh|juh~}r(jwjxXchhh]h]h]jy}h]h]uhM hhh]rhXstore_boot_index_from_rom(); /* Make all control module registers accessible */ ctrl_mmr_unlock(); asm("test: nop"); asm(" nop"); asm(" b test "); asm(" nop"); asm(" nop"); setup_am654_navss_northbridge();rr}r(hlUhmjubaubh)r}r(hlX>If a user is working with AM335x/AM437x/AM57xx, the test code could be added in the "early_system_init" function in the file /board-support//arch/arm/mach-omap2/hwinit-common.c. The location of the test code on all platforms will vary based on the section of the SPL we are trying to debug.rhmjwhwhh|hh~}r(h]h]h]h]h]uhM! hhh]rhX>If a user is working with AM335x/AM437x/AM57xx, the test code could be added in the "early_system_init" function in the file /board-support//arch/arm/mach-omap2/hwinit-common.c. The location of the test code on all platforms will vary based on the section of the SPL we are trying to debug.rr}r(hljhmjubaubj)r}r(hlUhmjwhwhh|jh~}r(jU.h]h]h]j Uh]h]j j uhM# hhh]r(j )r}r(hlXThere are two methods of compiling Uboot: `method1 `__ and `method2 `__. Both methods will generate the necessary symbol file required for SPL debugging. hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXThere are two methods of compiling Uboot: `method1 `__ and `method2 `__. Both methods will generate the necessary symbol file required for SPL debugging.hmjhwhh|hh~}r(h]h]h]h]h]uhM# h]r(hX*There are two methods of compiling Uboot: rr}r(hlX*There are two methods of compiling Uboot: hmjubh)r}r(hlXD`method1 `__h~}r(UnameXmethod1hX6Overview_Getting_Started_Guide.html#top-level-makefileh]h]h]h]h]uhmjh]rhXmethod1rr}r(hlUhmjubah|hubhX and rr}r(hlX and hmjubh)r}r(hlXI`method2 `__h~}r(UnameXmethod2hX;Foundational_Components_U-Boot.html#building-mlo-and-u-booth]h]h]h]h]uhmjh]rhXmethod2rr}r(hlUhmjubah|hubhXR. Both methods will generate the necessary symbol file required for SPL debugging.rr}r(hlXR. Both methods will generate the necessary symbol file required for SPL debugging.hmjubeubaubj )r}r(hlX On AM335x/AM437x/AM57xx, the symbol file is located in the following directory "/board-support//spl/u-boot-spl". For AM654x, the symbol file is located in the following directory "/board-support/u-boot_build/r5/spl/u-boot-spl". hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlX On AM335x/AM437x/AM57xx, the symbol file is located in the following directory "/board-support//spl/u-boot-spl". For AM654x, the symbol file is located in the following directory "/board-support/u-boot_build/r5/spl/u-boot-spl".rhmjhwhh|hh~}r(h]h]h]h]h]uhM% h]rhX On AM335x/AM437x/AM57xx, the symbol file is located in the following directory "/board-support//spl/u-boot-spl". For AM654x, the symbol file is located in the following directory "/board-support/u-boot_build/r5/spl/u-boot-spl".rr}r(hljhmjubaubaubj )r}r(hlXAfter building Uboot, copy the relevant images on the SD card. For AM335x/AM437x/AM57xx, copy MLO and u-boot.img to the SD card. For AM65x, copy sysfw.itb, tiboot3.bin, tispl.bin and u-boot.img to the SD card. hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlXAfter building Uboot, copy the relevant images on the SD card. For AM335x/AM437x/AM57xx, copy MLO and u-boot.img to the SD card. For AM65x, copy sysfw.itb, tiboot3.bin, tispl.bin and u-boot.img to the SD card.rhmjhwhh|hh~}r(h]h]h]h]h]uhM' h]rhXAfter building Uboot, copy the relevant images on the SD card. For AM335x/AM437x/AM57xx, copy MLO and u-boot.img to the SD card. For AM65x, copy sysfw.itb, tiboot3.bin, tispl.bin and u-boot.img to the SD card.rr}r(hljhmjubaubaubj )r}r(hlX,Install the SD card and power on the board. hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]rh)r}r(hlX+Install the SD card and power on the board.rhmjhwhh|hh~}r(h]h]h]h]h]uhM) h]rhX+Install the SD card and power on the board.rr}r(hljhmjubaubaubj )r}r(hlXkOn CCS, launch the target configuration file created in Step2: .. Image:: ../images/Uboot_Image6.png hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]r(h)r}r(hlX>On CCS, launch the target configuration file created in Step2:rhmjhwhh|hh~}r(h]h]h]h]h]uhM+ h]rhX>On CCS, launch the target configuration file created in Step2:rr}r(hljhmjubaubj>)r}r(hlUh~}r(h]h]h]h]h]uhmjh]rj)r}r(hlX&.. Image:: ../images/Uboot_Image6.png h~}r(UuriX linux/../images/Uboot_Image6.pngrh]h]h]h]j}rU*jsh]uhmjh]h|jubah|j[ubeubj )r}r(hlXAfter successful launch, connect to one of the ARM cores. On AM65x, the inital SPL code is executed on the R5 so the user would connect to the R5 core. For the AM335x/AM437/AM57xx, please connect to the A8/A9/A15 core. .. Image:: ../images/Uboot_Image7.png hmjhwhh|jh~}r(h]h]h]h]h]uhNhhh]r(h)r}r(hlXAfter successful launch, connect to one of the ARM cores. On AM65x, the inital SPL code is executed on the R5 so the user would connect to the R5 core. For the AM335x/AM437/AM57xx, please connect to the A8/A9/A15 core.rhmjhwhh|hh~}r (h]h]h]h]h]uhM/ h]r hXAfter successful launch, connect to one of the ARM cores. On AM65x, the inital SPL code is executed on the R5 so the user would connect to the R5 core. For the AM335x/AM437/AM57xx, please connect to the A8/A9/A15 core.r r }r (hljhmjubaubj>)r }r (hlUh~}r (h]h]h]h]h]uhmjh]r j)r }r (hlX&.. Image:: ../images/Uboot_Image7.png h~}r (UuriX linux/../images/Uboot_Image7.pngr h]h]h]h]j}r U*j sh]uhmj h]h|jubah|j[ubeubj )r }r (hlXAfter connecting to the core, click on "Run"-> "Load"->"Load Symbols...": .. Image:: ../images/Uboot_Image8.png .. Image:: ../images/Uboot_Image9.png .. Image:: ../images/Uboot_Image10.png hmjhwhh|jh~}r (h]h]h]h]h]uhNhhh]r (h)r }r (hlXIAfter connecting to the core, click on "Run"-> "Load"->"Load Symbols...":r hmj hwhh|hh~}r (h]h]h]h]h]uhM3 h]r hXIAfter connecting to the core, click on "Run"-> "Load"->"Load Symbols...":r r }r (hlj hmj ubaubj>)r }r (hlUh~}r (h]h]h]h]h]uhmj h]r (j)r }r (hlX%.. Image:: ../images/Uboot_Image8.pngh~}r (UuriX linux/../images/Uboot_Image8.pngr! h]h]h]h]j}r" U*j! sh]uhmj h]h|jubj)r# }r$ (hlX%.. Image:: ../images/Uboot_Image9.pngh~}r% (UuriX linux/../images/Uboot_Image9.pngr& h]h]h]h]j}r' U*j& sh]uhmj h]h|jubj)r( }r) (hlX'.. Image:: ../images/Uboot_Image10.png h~}r* (UuriX!linux/../images/Uboot_Image10.pngr+ h]h]h]h]j}r, U*j+ sh]uhmj h]h|jubeh|j[ubeubj )r- }r. (hlXAfter loading the code, CCS should find the source code file and it should be stuck at the code previously added: .. Image:: ../images/Uboot_Image11.png hmjhwhh|jh~}r/ (h]h]h]h]h]uhNhhh]r0 (h)r1 }r2 (hlXqAfter loading the code, CCS should find the source code file and it should be stuck at the code previously added:r3 hmj- hwhh|hh~}r4 (h]h]h]h]h]uhM9 h]r5 hXqAfter loading the code, CCS should find the source code file and it should be stuck at the code previously added:r6 r7 }r8 (hlj3 hmj1 ubaubj>)r9 }r: (hlUh~}r; (h]h]h]h]h]uhmj- h]r< j)r= }r> (hlX'.. Image:: ../images/Uboot_Image11.png h~}r? (UuriX!linux/../images/Uboot_Image11.pngr@ h]h]h]h]j}rA U*j@ sh]uhmj9 h]h|jubah|j[ubeubj )rB }rC (hlXzTo break out of the loop, change the program counter in the Register Window: .. Image:: ../images/Uboot_Image12.png hmjhwhh|jh~}rD (h]h]h]h]h]uhNhhh]rE (h)rF }rG (hlXLTo break out of the loop, change the program counter in the Register Window:rH hmjB hwhh|hh~}rI (h]h]h]h]h]uhM= h]rJ hXLTo break out of the loop, change the program counter in the Register Window:rK rL }rM (hljH hmjF ubaubj>)rN }rO (hlUh~}rP (h]h]h]h]h]uhmjB h]rQ j)rR }rS (hlX'.. Image:: ../images/Uboot_Image12.png h~}rT (UuriX!linux/../images/Uboot_Image12.pngrU h]h]h]h]j}rV U*jU sh]uhmjN h]h|jubah|j[ubeubeubh)rW }rX (hlXaAt this point, the user has the ability to step through the SPL code and debug issues in the SPL.rY hmjwhwhh|hh~}rZ (h]h]h]h]h]uhMA hhh]r[ hXaAt this point, the user has the ability to step through the SPL code and debug issues in the SPL.r\ r] }r^ (hljY hmjW ubaubh)r_ }r` (hlX**NOTE**: On K3 family of devices such as AM654x, a watchdog timer part of the DMSC is enabled by default by the ROM bootcode with a timeout of 3 minutes. The watchdog timer is serviced by System Firmware (SYSFW) during normal operation. If one is debugging SPL before the SYSFW is loaded, the watchdog timer will not get serviced automatically and the debug session will reset after 3 minutes. Therefore, it is recommended to start debugging SPL code only after the startup of SYSFW to avoid running into the watchdog timer reset. Similarly, the watchdog timer is also enabled on the AM335x/AM437x/AM57xx devices and please refer to the "Disable_Watchdog()" function in our gel files.ra hmjwhwhh|hh~}rb (h]h]h]h]h]uhMC hhh]rc (j)rd }re (hlX**NOTE**h~}rf (h]h]h]h]h]uhmj_ h]rg hXNOTErh ri }rj (hlUhmjd ubah|j'ubhX: On K3 family of devices such as AM654x, a watchdog timer part of the DMSC is enabled by default by the ROM bootcode with a timeout of 3 minutes. The watchdog timer is serviced by System Firmware (SYSFW) during normal operation. If one is debugging SPL before the SYSFW is loaded, the watchdog timer will not get serviced automatically and the debug session will reset after 3 minutes. Therefore, it is recommended to start debugging SPL code only after the startup of SYSFW to avoid running into the watchdog timer reset. Similarly, the watchdog timer is also enabled on the AM335x/AM437x/AM57xx devices and please refer to the "Disable_Watchdog()" function in our gel files.rk rl }rm (hlX: On K3 family of devices such as AM654x, a watchdog timer part of the DMSC is enabled by default by the ROM bootcode with a timeout of 3 minutes. The watchdog timer is serviced by System Firmware (SYSFW) during normal operation. If one is debugging SPL before the SYSFW is loaded, the watchdog timer will not get serviced automatically and the debug session will reset after 3 minutes. Therefore, it is recommended to start debugging SPL code only after the startup of SYSFW to avoid running into the watchdog timer reset. Similarly, the watchdog timer is also enabled on the AM335x/AM437x/AM57xx devices and please refer to the "Disable_Watchdog()" function in our gel files.hmj_ ubeubeubeubeubhwhh|h}h~}rn (h]h]h]h]ro Ugeneral-informationrp ah]rq h!auhK.hhh]rr (h)rs }rt (hlXGeneral Informationru hmhqhwhh|hh~}rv (h]h]h]h]h]uhK.hhh]rw hXGeneral Informationrx ry }rz (hlju hmjs ubaubhn)r{ }r| (hlUhmhqhwhh|h}h~}r} (h]h]h]h]r~ Ugetting-the-u-boot-source-coder ah]r hGauhK1hhh]r (h)r }r (hlXGetting the U-Boot Source Coder hmj{ hwhh|hh~}r (h]h]h]h]h]uhK1hhh]r hXGetting the U-Boot Source Coder r }r (hlj hmj ubaubjC)r }r (hlUhmj{ hwhh|jZh~}r (h]h]h]h]h]uhK3hhh]r (jH)r }r (hlX/The easiest way to get access to the U-boot source code is by downloading and installing the Processor SDK Linux. Once installed, the U-Boot source code is included in the SDK's board-support directory. For your convenience the sources also includes the U-Boot's git repository including commit history.r jLKhmj hwhh|hh~}r (h]h]h]h]h]uhK7hhh]r hX/The easiest way to get access to the U-boot source code is by downloading and installing the Processor SDK Linux. Once installed, the U-Boot source code is included in the SDK's board-support directory. For your convenience the sources also includes the U-Boot's git repository including commit history.r r }r (hlj hmj ubaubjH)r }r (hlX?Alternatively, U-Boot sources can directly be fetched from GIT.r jLKhmj hwhh|hh~}r (h]h]h]h]h]uhK8hhh]r hX?Alternatively, U-Boot sources can directly be fetched from GIT.r r }r (hlj hmj ubaubeubj>)r }r (hlUhmj{ hwNh|j[h~}r (h]h]h]h]h]uhNhhh]r h)r }r (hlUhmj hwhh|hh~}r (hXCONFIG_sdk in ('PLSDK')h]h]h]h]h]uhK:hhh]r h)r }r (hlXThe GIT repo URL, branch and commit id can be found in the `Processor\_SDK\_Linux\_Release\_Notes `__hmj hwhh|hh~}r (h]h]h]h]h]uhK`__h~}r (UnameX!Processor_SDK_Linux_Release_NoteshX0Release_Specific_PLSDK_Release_Notes.html#u-booth]h]h]h]h]uhmj h]r hX!Processor_SDK_Linux_Release_Notesr r }r (hlUhmj ubah|hubeubaubaubjC)r }r (hlUhmj{ hwhh|jZh~}r (h]h]h]h]h]uhK?hhh]r jH)r }r (hlUjLKhmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]ubaubeubhohn)r }r (hlUhmhqhwhh|h}h~}r (h]h]h]h]r U@build-and-boot-flow-on-64-bit-platforms-based-on-k3-architecturer ah]r h4auhKhhh]r (h)r }r (hlXBBuild and Boot Flow on 64-bit platforms (based on K3 architecture)r hmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]r hXBBuild and Boot Flow on 64-bit platforms (based on K3 architecture)r r }r (hlj hmj ubaubh)r }r (hlXSeveral prebuilt images are required from the TI Processor SDK for building U-Boot on K3 based platforms. Go `here `__ to download and install the SDK.hmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]r (hXmSeveral prebuilt images are required from the TI Processor SDK for building U-Boot on K3 based platforms. Go r r }r (hlXmSeveral prebuilt images are required from the TI Processor SDK for building U-Boot on K3 based platforms. Go hmj ubh)r }r (hlX5`here `__h~}r (UnameXherehX*Overview/Download_and_Install_the_SDK.htmlh]h]h]h]h]uhmj h]r hXherer r }r (hlUhmj ubah|hubhX! to download and install the SDK.r r }r (hlX! to download and install the SDK.hmj ubeubh)r }r (hlXTI-u-boot is included in the SDK in /board-support. Ensure that the u-boot version matches the `build information `__.hmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]r (hXnTI-u-boot is included in the SDK in /board-support. Ensure that the u-boot version matches the r r }r (hlXnTI-u-boot is included in the SDK in /board-support. Ensure that the u-boot version matches the hmj ubh)r }r (hlXM`build information `__h~}r (UnameXbuild informationhX5Release_Specific_Release_Notes.html#build-informationh]h]h]h]h]uhmj h]r hXbuild informationr r }r (hlUhmj ubah|hubhX.r }r (hlX.hmj ubeubjC)r }r (hlXSetting the tool chain pathr hmj hwhh|jGh~}r (h]r U setting-the-full-tool-chain-pathr ah]h]h]h]r h)auhNhhh]r hXSetting the tool chain pathr r }r (hlj hmj ubaubh)r }r (hlXWe strongly recommend using the toolchain that came with the Linux Core release that corresponds to this U-Boot release. For e.g:r hmj hwhh|hh~}r (h]h]h]h]h]uhKhhh]r hXWe strongly recommend using the toolchain that came with the Linux Core release that corresponds to this U-Boot release. For e.g:r r }r (hlj hmj ubaubjr)r }r (hlXexport PATH=$HOME/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin:$PATH export PATH=$HOME/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin:$PATHhmj hwhh|juh~}r!(hhh]h]h]h]h]uhMhhh]r!hXexport PATH=$HOME/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin:$PATH export PATH=$HOME/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin:$PATHr!r!}r!(hlUhmj ubaubjC)r!}r!(hlXCompiling R5 and ARM64 imagesr!hmj hwhh|jGh~}r!(h]r !Ucompiling-r5-and-arm64-imagesr !ah]h]h]h]r !h@auhNhhh]r !hXCompiling R5 and ARM64 imagesr !r!}r!(hlj!hmj!ubaubh)r!}r!(hlXMUse the following table to determine what defconfig to use to configure with:r!hmj hwhh|hh~}r!(h]h]h]h]h]uhM hhh]r!hXMUse the following table to determine what defconfig to use to configure with:r!r!}r!(hlj!hmj!ubaubj)r!}r!(hlUhmj hwhh|jh~}r!(h]h]h]h]h]uhNhhh]r!j)r!}r!(hlUh~}r!(h]h]h]h]h]UcolsKuhmj!h]r!(j)r !}r!!(hlUh~}r"!(h]h]h]h]h]UcolwidthKuhmj!h]h|j"ubj)r#!}r$!(hlUh~}r%!(h]h]h]h]h]UcolwidthK!uhmj!h]h|j"ubj)r&!}r'!(hlUh~}r(!(h]h]h]h]h]UcolwidthK uhmj!h]h|j"ubj)r)!}r*!(hlUh~}r+!(h]h]h]h]h]UcolwidthK uhmj!h]h|j"ubj)r,!}r-!(hlUh~}r.!(h]h]h]h]h]UcolwidthK uhmj!h]h|j"ubj)r/!}r0!(hlUh~}r1!(h]h]h]h]h]UcolwidthK uhmj!h]h|j"ubj/)r2!}r3!(hlUh~}r4!(h]h]h]h]h]uhmj!h]r5!j4)r6!}r7!(hlUh~}r8!(h]h]h]h]h]uhmj2!h]r9!(j9)r:!}r;!(hlUh~}r!}r?!(hlXBoardr@!hmj:!hwhh|hh~}rA!(h]h]h]h]h]uhM h]rB!hXBoardrC!rD!}rE!(hlj@!hmj>!ubaubah|jFubj9)rF!}rG!(hlUh~}rH!(h]h]h]h]h]uhmj6!h]rI!h)rJ!}rK!(hlX SD/eMMC BootrL!hmjF!hwhh|hh~}rM!(h]h]h]h]h]uhM h]rN!hX SD/eMMC BootrO!rP!}rQ!(hljL!hmjJ!ubaubah|jFubj9)rR!}rS!(hlUh~}rT!(h]h]h]h]h]uhmj6!h]rU!h)rV!}rW!(hlX UART bootrX!hmjR!hwhh|hh~}rY!(h]h]h]h]h]uhM h]rZ!hX UART bootr[!r\!}r]!(hljX!hmjV!ubaubah|jFubj9)r^!}r_!(hlUh~}r`!(h]h]h]h]h]uhmj6!h]ra!h)rb!}rc!(hlX OSPI bootrd!hmj^!hwhh|hh~}re!(h]h]h]h]h]uhM h]rf!hX OSPI bootrg!rh!}ri!(hljd!hmjb!ubaubah|jFubj9)rj!}rk!(hlUh~}rl!(h]h]h]h]h]uhmj6!h]rm!h)rn!}ro!(hlX Hyper Flashrp!hmjj!hwhh|hh~}rq!(h]h]h]h]h]uhM h]rr!hX Hyper Flashrs!rt!}ru!(hljp!hmjn!ubaubah|jFubj9)rv!}rw!(hlUh~}rx!(h]h]h]h]h]uhmj6!h]ry!h)rz!}r{!(hlXUSB DFUr|!hmjv!hwhh|hh~}r}!(h]h]h]h]h]uhM h]r~!hXUSB DFUr!r!}r!(hlj|!hmjz!ubaubah|jFubeh|jwubah|jxubjy)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!(j4)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!(j9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX AM65x EVM/IDKr!hmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX AM65x EVM/IDKr!r!}r!(hlj!hmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX4am65x\_evm\_r5\_defconfig am65x\_evm\_a53\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX.am65x_evm_r5_defconfig am65x_evm_a53_defconfigr!r!}r!(hlX4am65x\_evm\_r5\_defconfig am65x\_evm\_a53\_defconfighmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX4am65x\_evm\_r5\_defconfig am65x\_evm\_a53\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX.am65x_evm_r5_defconfig am65x_evm_a53_defconfigr!r!}r!(hlX4am65x\_evm\_r5\_defconfig am65x\_evm\_a53\_defconfighmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX3am65x\_evm\_r5_defconfig am65x\_evm\_a53\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX.am65x_evm_r5_defconfig am65x_evm_a53_defconfigr!r!}r!(hlX3am65x\_evm\_r5_defconfig am65x\_evm\_a53\_defconfighmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]h|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]h|jFubeh|jwubj4)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!(j9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX J721E EVMr!hmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX J721E EVMr!r!}r!(hlj!hmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX.j721e_evm_r5_defconfig j721e_evm_a72_defconfigr!r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX.j721e_evm_r5_defconfig j721e_evm_a72_defconfigr!r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX.j721e_evm_r5_defconfig j721e_evm_a72_defconfigr!r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r!hX.j721e_evm_r5_defconfig j721e_evm_a72_defconfigr!r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!ubaubah|jFubj9)r!}r!(hlUh~}r!(h]h]h]h]h]uhmj!h]r!h)r!}r!(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!hwhh|hh~}r!(h]h]h]h]h]uhMh]r"hX.j721e_evm_r5_defconfig j721e_evm_a72_defconfigr"r"}r"(hlX4j721e\_evm\_r5\_defconfig j721e\_evm\_a72\_defconfighmj!ubaubah|jFubeh|jwubeh|jubeh|jubaubh)r"}r"(hlXBelow are the steps for building images for AM65x IDK (substitute with the right config for the board that you are building for).r"hmj hwhh|hh~}r"(h]h]h]h]h]uhMhhh]r"hXBelow are the steps for building images for AM65x IDK (substitute with the right config for the board that you are building for).r "r "}r "(hlj"hmj"ubaubh)r "}r "(hlX**R5**r"hmj hwhh|hh~}r"(h]h]h]h]h]uhMhhh]r"j)r"}r"(hlj"h~}r"(h]h]h]h]h]uhmj "h]r"hXR5r"r"}r"(hlUhmj"ubah|j'ubaubjr)r"}r"(hlX$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am65x_evm_r5_defconfig O=/r5 $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=/r5hmj hwhh|juh~}r"(jwjxXconsolehhh]h]h]jy}h]h]uhMhhh]r"hX$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am65x_evm_r5_defconfig O=/r5 $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=/r5r"r"}r"(hlUhmj"ubaubh)r"}r "(hlX **ARM64**r!"hmj hwhh|hh~}r""(h]h]h]h]h]uhMhhh]r#"j)r$"}r%"(hlj!"h~}r&"(h]h]h]h]h]uhmj"h]r'"hXARM64r("r)"}r*"(hlUhmj$"ubah|j'ubaubjr)r+"}r,"(hlX!$ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- am65x_evm_a53_defconfig O=/a53 $ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- ATF=/board-support/prebuilt-images/bl31.bin TEE=/board-support/prebuilt-images/bl32.bin O=/a53hmj hwhh|juh~}r-"(jwjxXconsolehhh]h]h]jy}h]h]uhM!hhh]r."hX!$ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- am65x_evm_a53_defconfig O=/a53 $ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- ATF=/board-support/prebuilt-images/bl31.bin TEE=/board-support/prebuilt-images/bl32.bin O=/a53r/"r0"}r1"(hlUhmj+"ubaubjC)r2"}r3"(hlX Target Imagesr4"hmj hwhh|jGh~}r5"(h]h]h]h]h]uhM'hhh]r6"hX Target Imagesr7"r8"}r9"(hlj4"hmj2"ubaubh)r:"}r;"(hlXCopy the below images to the boot partition of an SD card and boot. Instructions to format the SD card can be found `here `__.hmj hwhh|hh~}r<"(h]h]h]h]h]uhM(hhh]r="(hXtCopy the below images to the boot partition of an SD card and boot. Instructions to format the SD card can be found r>"r?"}r@"(hlXtCopy the below images to the boot partition of an SD card and boot. Instructions to format the SD card can be found hmj:"ubh)rA"}rB"(hlXB`here `__h~}rC"(UnameXherehX7Overview/Processor_SDK_Linux_create_SD_card_script.htmlh]h]h]h]h]uhmj:"h]rD"hXhererE"rF"}rG"(hlUhmjA"ubah|hubhX.rH"}rI"(hlX.hmj:"ubeubj#)rJ"}rK"(hlUhmj hwhh|j&h~}rL"(j(X-h]h]h]h]h]uhM+hhh]rM"(j )rN"}rO"(hlX&tiboot3.bin from /r5rP"hmjJ"hwhh|jh~}rQ"(h]h]h]h]h]uhNhhh]rR"h)rS"}rT"(hljP"hmjN"hwhh|hh~}rU"(h]h]h]h]h]uhM+h]rV"hX&tiboot3.bin from /r5rW"rX"}rY"(hljP"hmjS"ubaubaubj )rZ"}r["(hlX1tispl.bin, u-boot.img from /a53r\"hmjJ"hwhh|jh~}r]"(h]h]h]h]h]uhNhhh]r^"h)r_"}r`"(hlj\"hmjZ"hwhh|hh~}ra"(h]h]h]h]h]uhM,h]rb"hX1tispl.bin, u-boot.img from /a53rc"rd"}re"(hlj\"hmj_"ubaubaubj )rf"}rg"(hlX>sysfw.itb from /board-support/prebuilt-images/ hmjJ"hwhh|jh~}rh"(h]h]h]h]h]uhNhhh]ri"h)rj"}rk"(hlX=sysfw.itb from /board-support/prebuilt-images/rl"hmjf"hwhh|hh~}rm"(h]h]h]h]h]uhM-h]rn"hX=sysfw.itb from /board-support/prebuilt-images/ro"rp"}rq"(hljl"hmjj"ubaubaubeubjC)rr"}rs"(hlX Image Formatsrt"hmj hwhh|jGh~}ru"(h]h]h]h]h]uhM0hhh]rv"hX Image Formatsrw"rx"}ry"(hljt"hmjr"ubaubj#)rz"}r{"(hlUhmj hwhh|j&h~}r|"(j(X-h]h]h]h]h]uhM1hhh]r}"j )r~"}r"(hlX tiboot3.bin hmjz"hwhh|jh~}r"(h]h]h]h]h]uhNhhh]r"h)r"}r"(hlX tiboot3.binr"hmj~"hwhh|hh~}r"(h]h]h]h]h]uhM1h]r"hX tiboot3.binr"r"}r"(hlj"hmj"ubaubaubaubjr)r"}r"(hlX+-----------------------+ | X.509 | | Certificate | | +-------------------+ | | | | | | | R5 | | | | u-boot-spl.bin | | | | | | | +-------------------+ | | | | | | | FIT header | | | | +---------------+ | | | | | | | | | | | DTB 1...N | | | | | +---------------+ | | | +-------------------+ | +-----------------------+hmj hwhh|juh~}r"(jwjxXconsolehhh]h]h]jy}h]h]uhM3hhh]r"hX+-----------------------+ | X.509 | | Certificate | | +-------------------+ | | | | | | | R5 | | | | u-boot-spl.bin | | | | | | | +-------------------+ | | | | | | | FIT header | | | | +---------------+ | | | | | | | | | | | DTB 1...N | | | | | +---------------+ | | | +-------------------+ | +-----------------------+r"r"}r"(hlUhmj"ubaubj#)r"}r"(hlUhmj hwhh|j&h~}r"(j(X-h]h]h]h]h]uhMHhhh]r"j )r"}r"(hlX tispl.bin hmj"hwhh|jh~}r"(h]h]h]h]h]uhNhhh]r"h)r"}r"(hlX tispl.binr"hmj"hwhh|hh~}r"(h]h]h]h]h]uhMHh]r"hX tispl.binr"r"}r"(hlj"hmj"ubaubaubaubjr)r"}r"(hlX+-----------------------+ | | | FIT HEADER | | +-------------------+ | | | | | | | ARM64 ATF | | | +-------------------+ | | | | | | | ARM64 OPTEE | | | +-------------------+ | | | | | | | ARM64 SPL | | | +-------------------+ | | | | | | | SPL DTB 1...N | | | +-------------------+ | +-----------------------+hmj hwhh|juh~}r"(jwjxXconsolehhh]h]h]jy}h]h]uhMJhhh]r"hX+-----------------------+ | | | FIT HEADER | | +-------------------+ | | | | | | | ARM64 ATF | | | +-------------------+ | | | | | | | ARM64 OPTEE | | | +-------------------+ | | | | | | | ARM64 SPL | | | +-------------------+ | | | | | | | SPL DTB 1...N | | | +-------------------+ | +-----------------------+r"r"}r"(hlUhmj"ubaubj#)r"}r"(hlUhmj hwhh|j&h~}r"(j(X-h]h]h]h]h]uhM^hhh]r"j )r"}r"(hlX sysfw.itb hmj"hwhh|jh~}r"(h]h]h]h]h]uhNhhh]r"h)r"}r"(hlX sysfw.itbr"hmj"hwhh|hh~}r"(h]h]h]h]h]uhM^h]r"hX sysfw.itbr"r"}r"(hlj"hmj"ubaubaubaubjr)r"}r"(hlX+-----------------------+ | | | FIT HEADER | | +-------------------+ | | | | | | | sysfw.bin | | | +-------------------+ | | | | | | | board config | | | +-------------------+ | | | | | | | PM config | | | +-------------------+ | | | | | | | RM config | | | +-------------------+ | | | | | | | Secure config | | | +-------------------+ | +-----------------------+hmj hwhh|juh~}r"(jwjxXconsolehhh]h]h]jy}h]h]uhM`hhh]r"hX+-----------------------+ | | | FIT HEADER | | +-------------------+ | | | | | | | sysfw.bin | | | +-------------------+ | | | | | | | board config | | | +-------------------+ | | | | | | | PM config | | | +-------------------+ | | | | | | | RM config | | | +-------------------+ | | | | | | | Secure config | | | +-------------------+ | +-----------------------+r"r"}r"(hlUhmj"ubaubjC)r"}r"(hlX Boot Flowr"hmj hwhh|jGh~}r"(h]r"U k3-boot-flowr"ah]h]h]h]r"h$auhNhhh]r"hX Boot Flowr"r"}r"(hlj"hmj"ubaubh)r"}r"(hlXOn K3 architecture based devices, ROM supports boot only via MCU(R5). This means that bootloader has to run on R5 core. In order to meet this constraint, keeping safety in picture and to have faster boot time, the software boot architecture is designed as below:r"hmj hwhh|hh~}r"(h]h]h]h]h]uhMzhhh]r"hXOn K3 architecture based devices, ROM supports boot only via MCU(R5). This means that bootloader has to run on R5 core. In order to meet this constraint, keeping safety in picture and to have faster boot time, the software boot architecture is designed as below:r"r"}r"(hlj"hmj"ubaubjr)r"}r"(hlX+------------------------------------------------------------------------+ | DMSC | R5 | ARM64 | +------------------------------------------------------------------------+ | +--------+ | | | | | Reset | | | | | +--------+ | | | | : | | | | +--------+ | +-----------+ | | | | *ROM* |----------|-->| Reset rls | | | | +--------+ | +-----------+ | | | | | | : | | | | ROM | | : | | | |services| | : | | | | | | +-------------+ | | | | | | | *R5 ROM* | | | | | | | +-------------+ | | | | |<---------|---|Load and auth| | | | | | | | tiboot3.bin | | | | | | | +-------------+ | | | | | | : | | | | | | : | | | | | | : | | | | | | +-------------+ | | | | | | | *R5 SPL* | | | | | | | +-------------+ | | | | | | | Load | | | | | | | | sysfw.itb | | | | | Start | | +-------------+ | | | | System |<---------|---| Start | | | | |Firmware| | | SYSFW | | | | +--------+ | +-------------+ | | | : | | | | | | +---------+ | | Load | | | | | *SYSFW* | | | system | | | | +---------+ | | Config data | | | | | |<--------|---| | | | | | | | +-------------+ | | | | | | | | | | | | | | | DDR | | | | | | | | config | | | | | | | +-------------+ | | | | | | | | | | | | |<--------|---| Start A53 | | | | | | | | and Reset | | | | | | | +-------------+ | | | | | | | +-----------+ | | | |---------|-----------------------|---->| Reset rls | | | | | | | +-----------+ | | | DMSC | | | : | | |Services | | | +-----------+ | | | |<--------|-----------------------|---->|*ATF/OPTEE*| | | | | | | +-----------+ | | | | | | : | | | | | | +-----------+ | | | |<--------|-----------------------|---->| *A53 SPL* | | | | | | | +-----------+ | | | | | | | Load | | | | | | | | u-boot.img| | | | | | | +-----------+ | | | | | | : | | | | | | +-----------+ | | | |<--------|-----------------------|---->| *U-Boot* | | | | | | | +-----------+ | | | | | | | prompt | | | | | | | +-----------+ | | +---------+ | | | | | | | +------------------------------------------------------------------------+hmj hwhh|juh~}r"(jwjxXconsolehhh]h]h]jy}h]h]uhMhhh]r"hX+------------------------------------------------------------------------+ | DMSC | R5 | ARM64 | +------------------------------------------------------------------------+ | +--------+ | | | | | Reset | | | | | +--------+ | | | | : | | | | +--------+ | +-----------+ | | | | *ROM* |----------|-->| Reset rls | | | | +--------+ | +-----------+ | | | | | | : | | | | ROM | | : | | | |services| | : | | | | | | +-------------+ | | | | | | | *R5 ROM* | | | | | | | +-------------+ | | | | |<---------|---|Load and auth| | | | | | | | tiboot3.bin | | | | | | | +-------------+ | | | | | | : | | | | | | : | | | | | | : | | | | | | +-------------+ | | | | | | | *R5 SPL* | | | | | | | +-------------+ | | | | | | | Load | | | | | | | | sysfw.itb | | | | | Start | | +-------------+ | | | | System |<---------|---| Start | | | | |Firmware| | | SYSFW | | | | +--------+ | +-------------+ | | | : | | | | | | +---------+ | | Load | | | | | *SYSFW* | | | system | | | | +---------+ | | Config data | | | | | |<--------|---| | | | | | | | +-------------+ | | | | | | | | | | | | | | | DDR | | | | | | | | config | | | | | | | +-------------+ | | | | | | | | | | | | |<--------|---| Start A53 | | | | | | | | and Reset | | | | | | | +-------------+ | | | | | | | +-----------+ | | | |---------|-----------------------|---->| Reset rls | | | | | | | +-----------+ | | | DMSC | | | : | | |Services | | | +-----------+ | | | |<--------|-----------------------|---->|*ATF/OPTEE*| | | | | | | +-----------+ | | | | | | : | | | | | | +-----------+ | | | |<--------|-----------------------|---->| *A53 SPL* | | | | | | | +-----------+ | | | | | | | Load | | | | | | | | u-boot.img| | | | | | | +-----------+ | | | | | | : | | | | | | +-----------+ | | | |<--------|-----------------------|---->| *U-Boot* | | | | | | | +-----------+ | | | | | | | prompt | | | | | | | +-----------+ | | +---------+ | | | | | | | +------------------------------------------------------------------------+r"r"}r"(hlUhmj"ubaubh)r"}r"(hlXHere DMSC acts as master and provides all the critical services. R5/ARM64 requests DMSC to get these services done as shown in the above diagram.r"hmj hwhh|hh~}r"(h]h]h]h]h]uhMhhh]r"hXHere DMSC acts as master and provides all the critical services. R5/ARM64 requests DMSC to get these services done as shown in the above diagram.r"r"}r"(hlj"hmj"ubaubeubhn)r"}r"(hlUhmhqhwhh|h}h~}r"(h]h]h]h]r"Uu-boot-environmentr"ah]r"hauhMhhh]r"(h)r"}r"(hlXU-Boot Environmentr"hmj"hwhh|hh~}r"(h]h]h]h]h]uhMhhh]r"hXU-Boot Environmentr"r"}r"(hlj"hmj"ubaubh)r"}r"(hlXCPlease note that on many boards we modify the environment during system start for a variety of variables such as **board\_name** and if unset, **ethaddr**. When we restore defaults some variables will become unset, and this can lead to other things not working such as **findfdt** that rely on these run-time set variables.hmj"hwhh|hh~}r"(h]h]h]h]h]uhMhhh]r"(hXqPlease note that on many boards we modify the environment during system start for a variety of variables such as r"r"}r"(hlXqPlease note that on many boards we modify the environment during system start for a variety of variables such as hmj"ubj)r"}r"(hlX**board\_name**h~}r"(h]h]h]h]h]uhmj"h]r"hX board_namer"r"}r"(hlUhmj"ubah|j'ubhX and if unset, r"r"}r#(hlX and if unset, hmj"ubj)r#}r#(hlX **ethaddr**h~}r#(h]h]h]h]h]uhmj"h]r#hXethaddrr#r#}r#(hlUhmj#ubah|j'ubhXs. When we restore defaults some variables will become unset, and this can lead to other things not working such as r#r #}r #(hlXs. When we restore defaults some variables will become unset, and this can lead to other things not working such as hmj"ubj)r #}r #(hlX **findfdt**h~}r #(h]h]h]h]h]uhmj"h]r#hXfindfdtr#r#}r#(hlUhmj #ubah|j'ubhX+ that rely on these run-time set variables.r#r#}r#(hlX+ that rely on these run-time set variables.hmj"ubeubjC)r#}r#(hlXRestoring defaultsr#hmj"hwhh|jGh~}r#(h]r#Urestoring-defaultsr#ah]h]h]h]r#h>auhNhhh]r#hXRestoring defaultsr#r#}r#(hlj#hmj#ubaubh)r #}r!#(hlX3It is possible to reset the set of U-Boot environment variables to their defaults and if desired, save them to where the environment is stored, if applicable. It is also required to restore the default setting when u-boot version changes from an upgrade or downgrade. To do so, issue the following commands:r"#hmj"hwhh|hh~}r##(h]h]h]h]h]uhMhhh]r$#hX3It is possible to reset the set of U-Boot environment variables to their defaults and if desired, save them to where the environment is stored, if applicable. It is also required to restore the default setting when u-boot version changes from an upgrade or downgrade. To do so, issue the following commands:r%#r&#}r'#(hlj"#hmj #ubaubjr)r(#}r)#(hlX+U-Boot # env default -f -a U-Boot # saveenvhmj"hwhh|juh~}r*#(hhh]h]h]h]h]uhMhhh]r+#hX+U-Boot # env default -f -a U-Boot # saveenvr,#r-#}r.#(hlUhmj(#ubaubjC)r/#}r0#(hlUhmj"hwhh|jZh~}r1#(h]h]h]h]h]uhMhhh]r2#jH)r3#}r4#(hlUjLKhmj/#hwhh|hh~}r5#(h]h]h]h]h]uhKhhh]ubaubjC)r6#}r7#(hlXNetworking Environmentr8#hmj"hwhh|jGh~}r9#(h]r:#Unetworking-environmentr;#ah]h]h]h]r<#hWauhNhhh]r=#hXNetworking Environmentr>#r?#}r@#(hlj8#hmj6#ubaubh)rA#}rB#(hlXWhen using a USB-Ethernet dongle a valid MAC address must be set in the environment. To create a valid address please read `**this page** `__. Then issue the following command:hmj"hwhh|hh~}rC#(h]h]h]h]h]uhMhhh]rD#(hX{When using a USB-Ethernet dongle a valid MAC address must be set in the environment. To create a valid address please read rE#rF#}rG#(hlX{When using a USB-Ethernet dongle a valid MAC address must be set in the environment. To create a valid address please read hmjA#ubh)rH#}rI#(hlXR`**this page** `__h~}rJ#(UnameX **this page**hX>http://www.denx.de/wiki/view/DULG/WhereCanIGetAValidMACAddressh]h]h]h]h]uhmjA#h]rK#hX **this page**rL#rM#}rN#(hlUhmjH#ubah|hubhX#. Then issue the following command:rO#rP#}rQ#(hlX#. Then issue the following command:hmjA#ubeubjr)rR#}rS#(hlX0U-Boot # setenv usbethaddr value:from:link:abovehmj"hwhh|juh~}rT#(hhh]h]h]h]h]uhMhhh]rU#hX0U-Boot # setenv usbethaddr value:from:link:aboverV#rW#}rX#(hlUhmjR#ubaubh)rY#}rZ#(hlXMYou can use the **printenv** command to see if **usbethaddr** is already set.hmj"hwhh|hh~}r[#(h]h]h]h]h]uhMhhh]r\#(hXYou can use the r]#r^#}r_#(hlXYou can use the hmjY#ubj)r`#}ra#(hlX **printenv**h~}rb#(h]h]h]h]h]uhmjY#h]rc#hXprintenvrd#re#}rf#(hlUhmj`#ubah|j'ubhX command to see if rg#rh#}ri#(hlX command to see if hmjY#ubj)rj#}rk#(hlX**usbethaddr**h~}rl#(h]h]h]h]h]uhmjY#h]rm#hX usbethaddrrn#ro#}rp#(hlUhmjj#ubah|j'ubhX is already set.rq#rr#}rs#(hlX is already set.hmjY#ubeubh)rt#}ru#(hlXThen start the USB subsystem:rv#hmj"hwhh|hh~}rw#(h]h]h]h]h]uhMhhh]rx#hXThen start the USB subsystem:ry#rz#}r{#(hljv#hmjt#ubaubjr)r|#}r}#(hlXU-Boot # usb starthmj"hwhh|juh~}r~#(hhh]h]h]h]h]uhMhhh]r#hXU-Boot # usb startr#r#}r#(hlUhmj|#ubaubh)r#}r#(hlXThe default behavior of U-Boot is to utilize all information that a DHCP server passes to us when the user issues the **dhcp** command. This will include the dhcp parameter *next-server* which indicates where to fetch files from via TFTP. There may be times however where the dhcp server on your network provides incorrect information and you are unable to modify the server. In this case the following steps can be helpful:hmj"hwhh|hh~}r#(h]h]h]h]h]uhMhhh]r#(hXvThe default behavior of U-Boot is to utilize all information that a DHCP server passes to us when the user issues the r#r#}r#(hlXvThe default behavior of U-Boot is to utilize all information that a DHCP server passes to us when the user issues the hmj#ubj)r#}r#(hlX**dhcp**h~}r#(h]h]h]h]h]uhmj#h]r#hXdhcpr#r#}r#(hlUhmj#ubah|j'ubhX/ command. This will include the dhcp parameter r#r#}r#(hlX/ command. This will include the dhcp parameter hmj#ubjq )r#}r#(hlX *next-server*h~}r#(h]h]h]h]h]uhmj#h]r#hX next-serverr#r#}r#(hlUhmj#ubah|jy ubhX which indicates where to fetch files from via TFTP. There may be times however where the dhcp server on your network provides incorrect information and you are unable to modify the server. In this case the following steps can be helpful:r#r#}r#(hlX which indicates where to fetch files from via TFTP. There may be times however where the dhcp server on your network provides incorrect information and you are unable to modify the server. In this case the following steps can be helpful:hmj#ubeubjr)r#}r#(hlXbU-Boot # setenv autoload no U-Boot # dhcp U-Boot # setenv serverip correct.server.ip U-Boot # tftphmj"hwhh|juh~}r#(hhh]h]h]h]h]uhM hhh]r#hXbU-Boot # setenv autoload no U-Boot # dhcp U-Boot # setenv serverip correct.server.ip U-Boot # tftpr#r#}r#(hlUhmj#ubaubh)r#}r#(hlXFAnother alternative is to utilize the full syntax of the tftp command:r#hmj"hwhh|hh~}r#(h]h]h]h]h]uhMhhh]r#hXFAnother alternative is to utilize the full syntax of the tftp command:r#r#}r#(hlj#hmj#ubaubjr)r#}r#(hlXVU-Boot # setenv autoload no U-Boot # dhcp U-Boot # tftp ${loadaddr} server.ip:fileNamehmj"hwhh|juh~}r#(hhh]h]h]h]h]uhMhhh]r#hXVU-Boot # setenv autoload no U-Boot # dhcp U-Boot # tftp ${loadaddr} server.ip:fileNamer#r#}r#(hlUhmj#ubaubeubhn)r#}r#(hlUhmhqhwhh|h}h~}r#(h]h]h]h]r#U available-ram-for-image-downloadr#ah]r#hauhMhhh]r#(h)r#}r#(hlX Available RAM for image downloadr#hmj#hwhh|hh~}r#(h]h]h]h]h]uhMhhh]r#hX Available RAM for image downloadr#r#}r#(hlj#hmj#ubaubh)r#}r#(hlXfTo know the amount of RAM available for downloading images or for other usage, use ``bdinfo`` command.hmj#hwhh|hh~}r#(h]h]h]h]h]uhMhhh]r#(hXSTo know the amount of RAM available for downloading images or for other usage, use r#r#}r#(hlXSTo know the amount of RAM available for downloading images or for other usage, use hmj#ubj)r#}r#(hlX ``bdinfo``h~}r#(h]h]h]h]h]uhmj#h]r#hXbdinfor#r#}r#(hlUhmj#ubah|jubhX command.r#r#}r#(hlX command.hmj#ubeubjr)r#}r#(hlX;=> bdinfo arch_number = 0x00000000 boot_params = 0x80000100 DRAM bank = 0x00000000 -> start = 0x80000000 -> size = 0x7F000000 baudrate = 115200 bps TLB addr = 0xFEFF0000 relocaddr = 0xFEF30000 reloc off = 0x7E730000 irq_sp = 0xFCEF8880 sp start = 0xFCEF8870 Early malloc usage: 890 / 2000hmj#hwhh|juh~}r#(hhh]h]h]h]h]uhM!hhh]r#hX;=> bdinfo arch_number = 0x00000000 boot_params = 0x80000100 DRAM bank = 0x00000000 -> start = 0x80000000 -> size = 0x7F000000 baudrate = 115200 bps TLB addr = 0xFEFF0000 relocaddr = 0xFEF30000 reloc off = 0x7E730000 irq_sp = 0xFCEF8880 sp start = 0xFCEF8870 Early malloc usage: 890 / 2000r#r#}r#(hlUhmj#ubaubh)r#}r#(hlXAfter booting, U-Boot relocates itself (along with its various reserved RAM areas) and places itself at end of available RAM (starting at ``relocaddr`` in ``bdinfo`` output above). Only the stack is located just before that area. The address of top of the stack is in ``sp start`` in ``bdinfo`` output and it grows downwards. Users should reserve at least about 1MB for stack, so in the example output above, RAM in the range of ``[0x80000000, 0xFCE00000]`` is safely available for use.hmj#hwhh|hh~}r#(h]h]h]h]h]uhM$hhh]r#(hXAfter booting, U-Boot relocates itself (along with its various reserved RAM areas) and places itself at end of available RAM (starting at r#r#}r#(hlXAfter booting, U-Boot relocates itself (along with its various reserved RAM areas) and places itself at end of available RAM (starting at hmj#ubj)r#}r#(hlX ``relocaddr``h~}r#(h]h]h]h]h]uhmj#h]r#hX relocaddrr#r#}r#(hlUhmj#ubah|jubhX in r#r#}r#(hlX in hmj#ubj)r#}r#(hlX ``bdinfo``h~}r#(h]h]h]h]h]uhmj#h]r#hXbdinfor#r#}r#(hlUhmj#ubah|jubhXg output above). Only the stack is located just before that area. The address of top of the stack is in r#r#}r#(hlXg output above). Only the stack is located just before that area. The address of top of the stack is in hmj#ubj)r#}r#(hlX ``sp start``h~}r#(h]h]h]h]h]uhmj#h]r#hXsp startr#r#}r#(hlUhmj#ubah|jubhX in r#r#}r#(hlX in hmj#ubj)r$}r$(hlX ``bdinfo``h~}r$(h]h]h]h]h]uhmj#h]r$hXbdinfor$r$}r$(hlUhmj$ubah|jubhX output and it grows downwards. Users should reserve at least about 1MB for stack, so in the example output above, RAM in the range of r$r$}r $(hlX output and it grows downwards. Users should reserve at least about 1MB for stack, so in the example output above, RAM in the range of hmj#ubj)r $}r $(hlX``[0x80000000, 0xFCE00000]``h~}r $(h]h]h]h]h]uhmj#h]r $hX[0x80000000, 0xFCE00000]r$r$}r$(hlUhmj $ubah|jubhX is safely available for use.r$r$}r$(hlX is safely available for use.hmj#ubeubeubhn)r$}r$(hlUhmhqhwhh|h}h~}r$(h]h]h]h]r$U device-treesr$ah]r$h auhM.hhh]r$(h)r$}r$(hlX Device Treesr$hmj$hwhh|hh~}r$(h]h]h]h]h]uhM.hhh]r$hX Device Treesr $r!$}r"$(hlj$hmj$ubaubh)r#$}r$$(hlX A note about device trees. Now all supported boards are required to use a device tree to boot. To facilitate this in supported platforms, a command in U-Boot environment **findfdt** is available that will set the **fdtfile** variable to the name of the device tree to use, as found with the kernel sources. In the Keystone-2 family devices (K2H/K/E/L/G), it is specified by **name\_fdt** variable for each platform. The device tree is expected to be loaded from the same media as the kernel, and from the same relative path.hmj$hwhh|hh~}r%$(h]h]h]h]h]uhM0hhh]r&$(hXA note about device trees. Now all supported boards are required to use a device tree to boot. To facilitate this in supported platforms, a command in U-Boot environment r'$r($}r)$(hlXA note about device trees. Now all supported boards are required to use a device tree to boot. To facilitate this in supported platforms, a command in U-Boot environment hmj#$ubj)r*$}r+$(hlX **findfdt**h~}r,$(h]h]h]h]h]uhmj#$h]r-$hXfindfdtr.$r/$}r0$(hlUhmj*$ubah|j'ubhX is available that will set the r1$r2$}r3$(hlX is available that will set the hmj#$ubj)r4$}r5$(hlX **fdtfile**h~}r6$(h]h]h]h]h]uhmj#$h]r7$hXfdtfiler8$r9$}r:$(hlUhmj4$ubah|j'ubhX variable to the name of the device tree to use, as found with the kernel sources. In the Keystone-2 family devices (K2H/K/E/L/G), it is specified by r;$r<$}r=$(hlX variable to the name of the device tree to use, as found with the kernel sources. In the Keystone-2 family devices (K2H/K/E/L/G), it is specified by hmj#$ubj)r>$}r?$(hlX **name\_fdt**h~}r@$(h]h]h]h]h]uhmj#$h]rA$hXname_fdtrB$rC$}rD$(hlUhmj>$ubah|j'ubhX variable for each platform. The device tree is expected to be loaded from the same media as the kernel, and from the same relative path.rE$rF$}rG$(hlX variable for each platform. The device tree is expected to be loaded from the same media as the kernel, and from the same relative path.hmj#$ubeubeubeubhwhh|h}h~}rH$(h]h]h]h]rI$U'build-and-boot-flow-on-32-bit-platformsrJ$ah]rK$h*auhKBhhh]rL$(h)rM$}rN$(hlX'Build and Boot Flow on 32-bit platformsrO$hmhohwhh|hh~}rP$(h]h]h]h]h]uhKBhhh]rQ$hX'Build and Boot Flow on 32-bit platformsrR$rS$}rT$(hljO$hmjM$ubaubh)rU$}rV$(hlX}We strongly recommend the use of separate object directories when building. This is done with O= parameter to make. We also recommend that you use an output directory name that is identical to the configuration target name. That way if you are working with multiple configuration targets it is very easy to know which folder contains the u-boot binaries that you are interested in.rW$hmhohwhh|hh~}rX$(h]h]h]h]h]uhKDhhh]rY$hX}We strongly recommend the use of separate object directories when building. This is done with O= parameter to make. We also recommend that you use an output directory name that is identical to the configuration target name. That way if you are working with multiple configuration targets it is very easy to know which folder contains the u-boot binaries that you are interested in.rZ$r[$}r\$(hljW$hmjU$ubaubjC)r]$}r^$(hlXSetting the tool chain pathr_$hmhohwhh|jGh~}r`$(h]ra$Usetting-the-tool-chain-pathrb$ah]h]h]h]rc$hAauhNhhh]rd$hXSetting the tool chain pathre$rf$}rg$(hlj_$hmj]$ubaubh)rh$}ri$(hlXWe strongly recommend using the toolchain that came with the Linux Core release that corresponds to this U-Boot release. For e.g:rj$hmhohwhh|hh~}rk$(h]h]h]h]h]uhKNhhh]rl$hXWe strongly recommend using the toolchain that came with the Linux Core release that corresponds to this U-Boot release. For e.g:rm$rn$}ro$(hljj$hmjh$ubaubjr)rp$}rq$(hlXMexport PATH=$HOME/gcc-linaro-4.9-2015.05-x86_64_arm-linux-gnueabihf/bin:$PATHhmhohwhh|juh~}rr$(hhh]h]h]h]h]uhK^hhh]rs$hXMexport PATH=$HOME/gcc-linaro-4.9-2015.05-x86_64_arm-linux-gnueabihf/bin:$PATHrt$ru$}rv$(hlUhmjp$ubaubjC)rw$}rx$(hlXCleaning the Sourcesry$hmhohwhh|jGh~}rz$(h]r{$Ucleaning-the-sourcesr|$ah]h]h]h]r}$haauhNhhh]r~$hXCleaning the Sourcesr$r$}r$(hljy$hmjw$ubaubh)r$}r$(hlX/If you did not use a separate object directory:r$hmhohwhh|hh~}r$(h]h]h]h]h]uhKXhhh]r$hX/If you did not use a separate object directory:r$r$}r$(hlj$hmj$ubaubjr)r$}r$(hlX3$ make CROSS_COMPILE=arm-linux-gnueabihf- distcleanhmhohwhh|juh~}r$(hhh]h]h]h]h]uhKghhh]r$hX3$ make CROSS_COMPILE=arm-linux-gnueabihf- distcleanr$r$}r$(hlUhmj$ubaubh)r$}r$(hlX5If you used 'O=am335x\_evm' as your object directory:r$hmhohwhh|hh~}r$(h]h]h]h]h]uhK^hhh]r$hX4If you used 'O=am335x_evm' as your object directory:r$r$}r$(hlX5If you used 'O=am335x\_evm' as your object directory:hmj$ubaubjr)r$}r$(hlX$ rm -rf ./am335x_evmhmhohwhh|juh~}r$(hhh]h]h]h]h]uhKmhhh]r$hX$ rm -rf ./am335x_evmr$r$}r$(hlUhmj$ubaubjC)r$}r$(hlXCompiling MLO and u-bootr$hmhohwhh|jGh~}r$(h]r$Ucompiling-mlo-and-u-bootr$ah]h]h]h]r$h:auhNhhh]r$hXCompiling MLO and u-bootr$r$}r$(hlj$hmj$ubaubh)r$}r$(hlXBuilding of both u-boot and SPL is done at the same time. You must however first configure the build for the board you are working with. Use the following table to determine what defconfig to use to configure with:r$hmhohwhh|hh~}r$(h]h]h]h]h]uhKghhh]r$hXBuilding of both u-boot and SPL is done at the same time. You must however first configure the build for the board you are working with. Use the following table to determine what defconfig to use to configure with:r$r$}r$(hlj$hmj$ubaubj)r$}r$(hlUhmhohwhh|jh~}r$(h]h]h]h]h]uhNhhh]r$j)r$}r$(hlUh~}r$(h]h]h]h]h]UcolsK uhmj$h]r$(j)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthKuhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthKuhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthKuhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthK,uhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthKuhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthKuhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthKuhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthK)uhmj$h]h|j"ubj)r$}r$(hlUh~}r$(h]h]h]h]h]UcolwidthK*uhmj$h]h|j"ubj/)r$}r$(hlUh~}r$(h]h]h]h]h]uhmj$h]r$j4)r$}r$(hlUh~}r$(h]h]h]h]h]uhmj$h]r$(j9)r$}r$(hlUh~}r$(h]h]h]h]h]uhmj$h]r$h)r$}r$(hlXBoardr$hmj$hwhh|hh~}r$(h]h]h]h]h]uhKmh]r$hXBoardr$r$}r$(hlj$hmj$ubaubah|jFubj9)r$}r$(hlUh~}r$(h]h]h]h]h]uhmj$h]r$h)r$}r$(hlXSD Bootr$hmj$hwhh|hh~}r$(h]h]h]h]h]uhKmh]r$hXSD Bootr$r$}r$(hlj$hmj$ubaubah|jFubj9)r$}r$(hlUh~}r$(h]h]h]h]h]uhmj$h]r$h)r$}r$(hlX eMMC Bootr$hmj$hwhh|hh~}r$(h]h]h]h]h]uhKmh]r$hX eMMC Bootr$r%}r%(hlj$hmj$ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj$h]r%h)r%}r%(hlX NAND Bootr%hmj%hwhh|hh~}r %(h]h]h]h]h]uhKmh]r %hX NAND Bootr %r %}r %(hlj%hmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj$h]r%h)r%}r%(hlX UART Bootr%hmj%hwhh|hh~}r%(h]h]h]h]h]uhKmh]r%hX UART Bootr%r%}r%(hlj%hmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj$h]r%h)r%}r%(hlX Ethernet Bootr %hmj%hwhh|hh~}r!%(h]h]h]h]h]uhKmh]r"%hX Ethernet Bootr#%r$%}r%%(hlj %hmj%ubaubah|jFubj9)r&%}r'%(hlUh~}r(%(h]h]h]h]h]uhmj$h]r)%h)r*%}r+%(hlXUSB Ethernet Bootr,%hmj&%hwhh|hh~}r-%(h]h]h]h]h]uhKmh]r.%hXUSB Ethernet Bootr/%r0%}r1%(hlj,%hmj*%ubaubah|jFubj9)r2%}r3%(hlUh~}r4%(h]h]h]h]h]uhmj$h]r5%h)r6%}r7%(hlX USB Host Bootr8%hmj2%hwhh|hh~}r9%(h]h]h]h]h]uhKmh]r:%hX USB Host Bootr;%r<%}r=%(hlj8%hmj6%ubaubah|jFubj9)r>%}r?%(hlUh~}r@%(h]h]h]h]h]uhmj$h]rA%h)rB%}rC%(hlXSPI BootrD%hmj>%hwhh|hh~}rE%(h]h]h]h]h]uhKmh]rF%hXSPI BootrG%rH%}rI%(hljD%hmjB%ubaubah|jFubeh|jwubah|jxubjy)rJ%}rK%(hlUh~}rL%(h]h]h]h]h]uhmj$h]rM%(j4)rN%}rO%(hlUh~}rP%(h]h]h]h]h]uhmjJ%h]rQ%(j9)rR%}rS%(hlUh~}rT%(h]h]h]h]h]uhmjN%h]rU%h)rV%}rW%(hlX AM335x GP EVMrX%hmjR%hwhh|hh~}rY%(h]h]h]h]h]uhKoh]rZ%hX AM335x GP EVMr[%r\%}r]%(hljX%hmjV%ubaubah|jFubj9)r^%}r_%(hlUh~}r`%(h]h]h]h]h]uhmjN%h]ra%h)rb%}rc%(hlXam335x\_evm\_defconfighmj^%hwhh|hh~}rd%(h]h]h]h]h]uhKoh]re%hXam335x_evm_defconfigrf%rg%}rh%(hlXam335x\_evm\_defconfighmjb%ubaubah|jFubj9)ri%}rj%(hlUh~}rk%(h]h]h]h]h]uhmjN%h]h|jFubj9)rl%}rm%(hlUh~}rn%(h]h]h]h]h]uhmjN%h]ro%h)rp%}rq%(hlXam335x\_evm\_defconfighmjl%hwhh|hh~}rr%(h]h]h]h]h]uhKoh]rs%hXam335x_evm_defconfigrt%ru%}rv%(hlXam335x\_evm\_defconfighmjp%ubaubah|jFubj9)rw%}rx%(hlUh~}ry%(h]h]h]h]h]uhmjN%h]rz%h)r{%}r|%(hlXam335x\_evm\_defconfighmjw%hwhh|hh~}r}%(h]h]h]h]h]uhKoh]r~%hXam335x_evm_defconfigr%r%}r%(hlXam335x\_evm\_defconfighmj{%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmjN%h]r%h)r%}r%(hlXam335x\_evm\_defconfighmj%hwhh|hh~}r%(h]h]h]h]h]uhKoh]r%hXam335x_evm_defconfigr%r%}r%(hlXam335x\_evm\_defconfighmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmjN%h]r%h)r%}r%(hlXam335x\_evm\_defconfighmj%hwhh|hh~}r%(h]h]h]h]h]uhKoh]r%hXam335x_evm_defconfigr%r%}r%(hlXam335x\_evm\_defconfighmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmjN%h]h|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmjN%h]h|jFubeh|jwubj4)r%}r%(hlUh~}r%(h]h]h]h]h]uhmjJ%h]r%(j9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]r%h)r%}r%(hlX AM335x EVM-SKr%hmj%hwhh|hh~}r%(h]h]h]h]h]uhKqh]r%hX AM335x EVM-SKr%r%}r%(hlj%hmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]r%h)r%}r%(hlXam335x\_evm\_defconfighmj%hwhh|hh~}r%(h]h]h]h]h]uhKqh]r%hXam335x_evm_defconfigr%r%}r%(hlXam335x\_evm\_defconfighmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]h|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]h|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]r%h)r%}r%(hlXam335x\_evm\_defconfighmj%hwhh|hh~}r%(h]h]h]h]h]uhKqh]r%hXam335x_evm_defconfigr%r%}r%(hlXam335x\_evm\_defconfighmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]h|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]r%h)r%}r%(hlXam335x\_evm\_defconfighmj%hwhh|hh~}r%(h]h]h]h]h]uhKqh]r%hXam335x_evm_defconfigr%r%}r%(hlXam335x\_evm\_defconfighmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]h|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]h|jFubeh|jwubj4)r%}r%(hlUh~}r%(h]h]h]h]h]uhmjJ%h]r%(j9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]r%h)r%}r%(hlX AM335x ICEr%hmj%hwhh|hh~}r%(h]h]h]h]h]uhKsh]r%hX AM335x ICEr%r%}r%(hlj%hmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]r%h)r%}r%(hlXam335x\_evm\_defconfighmj%hwhh|hh~}r%(h]h]h]h]h]uhKsh]r%hXam335x_evm_defconfigr%r%}r%(hlXam335x\_evm\_defconfighmj%ubaubah|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]h|jFubj9)r%}r%(hlUh~}r%(h]h]h]h]h]uhmj%h]h|jFubj9)r%}r&(hlUh~}r&(h]h]h]h]h]uhmj%h]r&h)r&}r&(hlXam335x\_evm\_defconfighmj%hwhh|hh~}r&(h]h]h]h]h]uhKsh]r&hXam335x_evm_defconfigr&r&}r &(hlXam335x\_evm\_defconfighmj&ubaubah|jFubj9)r &}r &(hlUh~}r &(h]h]h]h]h]uhmj%h]h|jFubj9)r &}r&(hlUh~}r&(h]h]h]h]h]uhmj%h]h|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj%h]h|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj%h]h|jFubeh|jwubj4)r&}r&(hlUh~}r&(h]h]h]h]h]uhmjJ%h]r&(j9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlXBeagleBone Blackr &hmj&hwhh|hh~}r!&(h]h]h]h]h]uhKuh]r"&hXBeagleBone Blackr#&r$&}r%&(hlj &hmj&ubaubah|jFubj9)r&&}r'&(hlUh~}r(&(h]h]h]h]h]uhmj&h]r)&h)r*&}r+&(hlXam335x\_evm\_defconfighmj&&hwhh|hh~}r,&(h]h]h]h]h]uhKuh]r-&hXam335x_evm_defconfigr.&r/&}r0&(hlXam335x\_evm\_defconfighmj*&ubaubah|jFubj9)r1&}r2&(hlUh~}r3&(h]h]h]h]h]uhmj&h]r4&h)r5&}r6&(hlXam335x\_evm\_defconfighmj1&hwhh|hh~}r7&(h]h]h]h]h]uhKuh]r8&hXam335x_evm_defconfigr9&r:&}r;&(hlXam335x\_evm\_defconfighmj5&ubaubah|jFubj9)r<&}r=&(hlUh~}r>&(h]h]h]h]h]uhmj&h]h|jFubj9)r?&}r@&(hlUh~}rA&(h]h]h]h]h]uhmj&h]rB&h)rC&}rD&(hlXam335x\_evm\_defconfighmj?&hwhh|hh~}rE&(h]h]h]h]h]uhKuh]rF&hXam335x_evm_defconfigrG&rH&}rI&(hlXam335x\_evm\_defconfighmjC&ubaubah|jFubj9)rJ&}rK&(hlUh~}rL&(h]h]h]h]h]uhmj&h]h|jFubj9)rM&}rN&(hlUh~}rO&(h]h]h]h]h]uhmj&h]h|jFubj9)rP&}rQ&(hlUh~}rR&(h]h]h]h]h]uhmj&h]h|jFubj9)rS&}rT&(hlUh~}rU&(h]h]h]h]h]uhmj&h]h|jFubeh|jwubj4)rV&}rW&(hlUh~}rX&(h]h]h]h]h]uhmjJ%h]rY&(j9)rZ&}r[&(hlUh~}r\&(h]h]h]h]h]uhmjV&h]r]&h)r^&}r_&(hlXBeagleBone Whiter`&hmjZ&hwhh|hh~}ra&(h]h]h]h]h]uhKwh]rb&hXBeagleBone Whiterc&rd&}re&(hlj`&hmj^&ubaubah|jFubj9)rf&}rg&(hlUh~}rh&(h]h]h]h]h]uhmjV&h]ri&h)rj&}rk&(hlXam335x\_evm\_defconfighmjf&hwhh|hh~}rl&(h]h]h]h]h]uhKwh]rm&hXam335x_evm_defconfigrn&ro&}rp&(hlXam335x\_evm\_defconfighmjj&ubaubah|jFubj9)rq&}rr&(hlUh~}rs&(h]h]h]h]h]uhmjV&h]h|jFubj9)rt&}ru&(hlUh~}rv&(h]h]h]h]h]uhmjV&h]h|jFubj9)rw&}rx&(hlUh~}ry&(h]h]h]h]h]uhmjV&h]rz&h)r{&}r|&(hlXam335x\_evm\_defconfighmjw&hwhh|hh~}r}&(h]h]h]h]h]uhKwh]r~&hXam335x_evm_defconfigr&r&}r&(hlXam335x\_evm\_defconfighmj{&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmjV&h]h|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmjV&h]h|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmjV&h]h|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmjV&h]h|jFubeh|jwubj4)r&}r&(hlUh~}r&(h]h]h]h]h]uhmjJ%h]r&(j9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlX AM437x GP EVMr&hmj&hwhh|hh~}r&(h]h]h]h]h]uhKyh]r&hX AM437x GP EVMr&r&}r&(hlj&hmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlXam43xx\_evm\_defconfighmj&hwhh|hh~}r&(h]h]h]h]h]uhKyh]r&hXam43xx_evm_defconfigr&r&}r&(hlXam43xx\_evm\_defconfighmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]h|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlXam43xx\_evm\_defconfighmj&hwhh|hh~}r&(h]h]h]h]h]uhKyh]r&hXam43xx_evm_defconfigr&r&}r&(hlXam43xx\_evm\_defconfighmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlXam43xx\_evm\_defconfighmj&hwhh|hh~}r&(h]h]h]h]h]uhKyh]r&hXam43xx_evm_defconfigr&r&}r&(hlXam43xx\_evm\_defconfighmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlXam43xx\_evm\_defconfighmj&hwhh|hh~}r&(h]h]h]h]h]uhKyh]r&hXam43xx_evm_defconfigr&r&}r&(hlXam43xx\_evm\_defconfighmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlXam43xx\_evm\_defconfighmj&hwhh|hh~}r&(h]h]h]h]h]uhKyh]r&hXam43xx_evm_defconfigr&r&}r&(hlXam43xx\_evm\_defconfighmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlX%am43xx\_evm\_usbhost\_boot\_defconfighmj&hwhh|hh~}r&(h]h]h]h]h]uhKyh]r&hX!am43xx_evm_usbhost_boot_defconfigr&r&}r&(hlX%am43xx\_evm\_usbhost\_boot\_defconfighmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]h|jFubeh|jwubj4)r&}r&(hlUh~}r&(h]h]h]h]h]uhmjJ%h]r&(j9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlX AM437x EVM-Skr&hmj&hwhh|hh~}r&(h]h]h]h]h]uhK{h]r&hX AM437x EVM-Skr&r&}r&(hlj&hmj&ubaubah|jFubj9)r&}r&(hlUh~}r&(h]h]h]h]h]uhmj&h]r&h)r&}r&(hlXam43xx\_evm\_defconfighmj&hwhh|hh~}r&(h]h]h]h]h]uhK{h]r&hXam43xx_evm_defconfigr&r&}r'(hlXam43xx\_evm\_defconfighmj&ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj&h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj&h]h|jFubj9)r'}r'(hlUh~}r '(h]h]h]h]h]uhmj&h]h|jFubj9)r '}r '(hlUh~}r '(h]h]h]h]h]uhmj&h]h|jFubj9)r '}r'(hlUh~}r'(h]h]h]h]h]uhmj&h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj&h]r'h)r'}r'(hlX%am43xx\_evm\_usbhost\_boot\_defconfighmj'hwhh|hh~}r'(h]h]h]h]h]uhK{h]r'hX!am43xx_evm_usbhost_boot_defconfigr'r'}r'(hlX%am43xx\_evm\_usbhost\_boot\_defconfighmj'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj&h]h|jFubeh|jwubj4)r'}r'(hlUh~}r '(h]h]h]h]h]uhmjJ%h]r!'(j9)r"'}r#'(hlUh~}r$'(h]h]h]h]h]uhmj'h]r%'h)r&'}r''(hlX AM437x IDKr('hmj"'hwhh|hh~}r)'(h]h]h]h]h]uhK}h]r*'hX AM437x IDKr+'r,'}r-'(hlj('hmj&'ubaubah|jFubj9)r.'}r/'(hlUh~}r0'(h]h]h]h]h]uhmj'h]r1'h)r2'}r3'(hlXam43xx\_evm\_defconfighmj.'hwhh|hh~}r4'(h]h]h]h]h]uhK}h]r5'hXam43xx_evm_defconfigr6'r7'}r8'(hlXam43xx\_evm\_defconfighmj2'ubaubah|jFubj9)r9'}r:'(hlUh~}r;'(h]h]h]h]h]uhmj'h]h|jFubj9)r<'}r='(hlUh~}r>'(h]h]h]h]h]uhmj'h]h|jFubj9)r?'}r@'(hlUh~}rA'(h]h]h]h]h]uhmj'h]h|jFubj9)rB'}rC'(hlUh~}rD'(h]h]h]h]h]uhmj'h]h|jFubj9)rE'}rF'(hlUh~}rG'(h]h]h]h]h]uhmj'h]h|jFubj9)rH'}rI'(hlUh~}rJ'(h]h]h]h]h]uhmj'h]h|jFubj9)rK'}rL'(hlUh~}rM'(h]h]h]h]h]uhmj'h]rN'h)rO'}rP'(hlX&am43xx\_evm\_qspiboot\_defconfig (XIP)hmjK'hwhh|hh~}rQ'(h]h]h]h]h]uhK}h]rR'hX#am43xx_evm_qspiboot_defconfig (XIP)rS'rT'}rU'(hlX&am43xx\_evm\_qspiboot\_defconfig (XIP)hmjO'ubaubah|jFubeh|jwubj4)rV'}rW'(hlUh~}rX'(h]h]h]h]h]uhmjJ%h]rY'(j9)rZ'}r['(hlUh~}r\'(h]h]h]h]h]uhmjV'h]r]'h)r^'}r_'(hlXAM437x ePOS EVMr`'hmjZ'hwhh|hh~}ra'(h]h]h]h]h]uhKh]rb'hXAM437x ePOS EVMrc'rd'}re'(hlj`'hmj^'ubaubah|jFubj9)rf'}rg'(hlUh~}rh'(h]h]h]h]h]uhmjV'h]ri'h)rj'}rk'(hlXam43xx\_evm\_defconfighmjf'hwhh|hh~}rl'(h]h]h]h]h]uhKh]rm'hXam43xx_evm_defconfigrn'ro'}rp'(hlXam43xx\_evm\_defconfighmjj'ubaubah|jFubj9)rq'}rr'(hlUh~}rs'(h]h]h]h]h]uhmjV'h]h|jFubj9)rt'}ru'(hlUh~}rv'(h]h]h]h]h]uhmjV'h]rw'h)rx'}ry'(hlXam43xx\_evm\_defconfighmjt'hwhh|hh~}rz'(h]h]h]h]h]uhKh]r{'hXam43xx_evm_defconfigr|'r}'}r~'(hlXam43xx\_evm\_defconfighmjx'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmjV'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmjV'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmjV'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmjV'h]r'h)r'}r'(hlX%am43xx\_evm\_usbhost\_boot\_defconfighmj'hwhh|hh~}r'(h]h]h]h]h]uhKh]r'hX!am43xx_evm_usbhost_boot_defconfigr'r'}r'(hlX%am43xx\_evm\_usbhost\_boot\_defconfighmj'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmjV'h]h|jFubeh|jwubj4)r'}r'(hlUh~}r'(h]h]h]h]h]uhmjJ%h]r'(j9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]r'h)r'}r'(hlX AM572x GP EVMr'hmj'hwhh|hh~}r'(h]h]h]h]h]uhKh]r'hX AM572x GP EVMr'r'}r'(hlj'hmj'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]r'h)r'}r'(hlXam57xx\_evm\_defconfighmj'hwhh|hh~}r'(h]h]h]h]h]uhKh]r'hXam57xx_evm_defconfigr'r'}r'(hlXam57xx\_evm\_defconfighmj'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]r'h)r'}r'(hlXam57xx\_evm\_defconfighmj'hwhh|hh~}r'(h]h]h]h]h]uhKh]r'hXam57xx_evm_defconfigr'r'}r'(hlXam57xx\_evm\_defconfighmj'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubeh|jwubj4)r'}r'(hlUh~}r'(h]h]h]h]h]uhmjJ%h]r'(j9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]r'h)r'}r'(hlX AM572x IDKr'hmj'hwhh|hh~}r'(h]h]h]h]h]uhKh]r'hX AM572x IDKr'r'}r'(hlj'hmj'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]r'h)r'}r'(hlXam57xx\_evm\_defconfighmj'hwhh|hh~}r'(h]h]h]h]h]uhKh]r'hXam57xx_evm_defconfigr'r'}r'(hlXam57xx\_evm\_defconfighmj'ubaubah|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubj9)r'}r'(hlUh~}r'(h]h]h]h]h]uhmj'h]h|jFubeh|jwubj4)r'}r'(hlUh~}r((h]h]h]h]h]uhmjJ%h]r((j9)r(}r((hlUh~}r((h]h]h]h]h]uhmj'h]r(h)r(}r((hlX AM571x IDKr(hmj(hwhh|hh~}r ((h]h]h]h]h]uhKh]r (hX AM571x IDKr (r (}r ((hlj(hmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj'h]r(h)r(}r((hlXam57xx\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXam57xx_evm_defconfigr(r(}r((hlXam57xx\_evm\_defconfighmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj'h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj'h]h|jFubj9)r(}r ((hlUh~}r!((h]h]h]h]h]uhmj'h]h|jFubj9)r"(}r#((hlUh~}r$((h]h]h]h]h]uhmj'h]h|jFubj9)r%(}r&((hlUh~}r'((h]h]h]h]h]uhmj'h]h|jFubj9)r((}r)((hlUh~}r*((h]h]h]h]h]uhmj'h]h|jFubj9)r+(}r,((hlUh~}r-((h]h]h]h]h]uhmj'h]h|jFubeh|jwubj4)r.(}r/((hlUh~}r0((h]h]h]h]h]uhmjJ%h]r1((j9)r2(}r3((hlUh~}r4((h]h]h]h]h]uhmj.(h]r5(h)r6(}r7((hlXDRA74x/DRA72x/DRA71x EVMr8(hmj2(hwhh|hh~}r9((h]h]h]h]h]uhKh]r:(hXDRA74x/DRA72x/DRA71x EVMr;(r<(}r=((hlj8(hmj6(ubaubah|jFubj9)r>(}r?((hlUh~}r@((h]h]h]h]h]uhmj.(h]rA(h)rB(}rC((hlXdra7xx\_evm\_defconfighmj>(hwhh|hh~}rD((h]h]h]h]h]uhKh]rE(hXdra7xx_evm_defconfigrF(rG(}rH((hlXdra7xx\_evm\_defconfighmjB(ubaubah|jFubj9)rI(}rJ((hlUh~}rK((h]h]h]h]h]uhmj.(h]rL(h)rM(}rN((hlXdra7xx\_evm\_defconfighmjI(hwhh|hh~}rO((h]h]h]h]h]uhKh]rP(hXdra7xx_evm_defconfigrQ(rR(}rS((hlXdra7xx\_evm\_defconfighmjM(ubaubah|jFubj9)rT(}rU((hlUh~}rV((h]h]h]h]h]uhmj.(h]rW(h)rX(}rY((hlX(dra7xx\_evm\_defconfig (DRA71x EVM only)hmjT(hwhh|hh~}rZ((h]h]h]h]h]uhKh]r[(hX&dra7xx_evm_defconfig (DRA71x EVM only)r\(r](}r^((hlX(dra7xx\_evm\_defconfig (DRA71x EVM only)hmjX(ubaubah|jFubj9)r_(}r`((hlUh~}ra((h]h]h]h]h]uhmj.(h]h|jFubj9)rb(}rc((hlUh~}rd((h]h]h]h]h]uhmj.(h]h|jFubj9)re(}rf((hlUh~}rg((h]h]h]h]h]uhmj.(h]h|jFubj9)rh(}ri((hlUh~}rj((h]h]h]h]h]uhmj.(h]h|jFubj9)rk(}rl((hlUh~}rm((h]h]h]h]h]uhmj.(h]rn(h)ro(}rp((hlXdra7xx\_evm\_defconfig(QSPI)hmjk(hwhh|hh~}rq((h]h]h]h]h]uhKh]rr(hXdra7xx_evm_defconfig(QSPI)rs(rt(}ru((hlXdra7xx\_evm\_defconfig(QSPI)hmjo(ubaubah|jFubeh|jwubj4)rv(}rw((hlUh~}rx((h]h]h]h]h]uhmjJ%h]ry((j9)rz(}r{((hlUh~}r|((h]h]h]h]h]uhmjv(h]r}(h)r~(}r((hlXK2HK EVMr(hmjz(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXK2HK EVMr(r(}r((hlj(hmj~(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]r(h)r(}r((hlXk2hk\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXk2hk_evm_defconfigr(r(}r((hlXk2hk\_evm\_defconfighmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]r(h)r(}r((hlXk2hk\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXk2hk_evm_defconfigr(r(}r((hlXk2hk\_evm\_defconfighmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]r(h)r(}r((hlXk2hk\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXk2hk_evm_defconfigr(r(}r((hlXk2hk\_evm\_defconfighmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmjv(h]r(h)r(}r((hlXk2hk\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXk2hk_evm_defconfigr(r(}r((hlXk2hk\_evm\_defconfighmj(ubaubah|jFubeh|jwubj4)r(}r((hlUh~}r((h]h]h]h]h]uhmjJ%h]r((j9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]r(h)r(}r((hlXK2L EVMr(hmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXK2L EVMr(r(}r((hlj(hmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]r(h)r(}r((hlXk2l\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXk2l_evm_defconfigr(r(}r((hlXk2l\_evm\_defconfighmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]r(h)r(}r((hlXk2l\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXk2l_evm_defconfigr(r(}r((hlXk2l\_evm\_defconfighmj(ubaubah|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]h|jFubj9)r(}r((hlUh~}r((h]h]h]h]h]uhmj(h]r(h)r(}r((hlXk2l\_evm\_defconfighmj(hwhh|hh~}r((h]h]h]h]h]uhKh]r(hXk2l_evm_defconfigr(r(}r((hlXk2l\_evm\_defconfighmj(ubaubah|jFubeh|jwubj4)r(}r((hlUh~}r)(h]h]h]h]h]uhmjJ%h]r)(j9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj(h]r)h)r)}r)(hlXK2E EVMr)hmj)hwhh|hh~}r )(h]h]h]h]h]uhKh]r )hXK2E EVMr )r )}r )(hlj)hmj)ubaubah|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj(h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj(h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj(h]r)h)r)}r)(hlXk2e\_evm\_defconfighmj)hwhh|hh~}r)(h]h]h]h]h]uhKh]r)hXk2e_evm_defconfigr)r)}r)(hlXk2e\_evm\_defconfighmj)ubaubah|jFubj9)r)}r )(hlUh~}r!)(h]h]h]h]h]uhmj(h]r")h)r#)}r$)(hlXk2e\_evm\_defconfighmj)hwhh|hh~}r%)(h]h]h]h]h]uhKh]r&)hXk2e_evm_defconfigr')r()}r))(hlXk2e\_evm\_defconfighmj#)ubaubah|jFubj9)r*)}r+)(hlUh~}r,)(h]h]h]h]h]uhmj(h]h|jFubj9)r-)}r.)(hlUh~}r/)(h]h]h]h]h]uhmj(h]h|jFubj9)r0)}r1)(hlUh~}r2)(h]h]h]h]h]uhmj(h]h|jFubj9)r3)}r4)(hlUh~}r5)(h]h]h]h]h]uhmj(h]r6)h)r7)}r8)(hlXk2e\_evm\_defconfighmj3)hwhh|hh~}r9)(h]h]h]h]h]uhKh]r:)hXk2e_evm_defconfigr;)r<)}r=)(hlXk2e\_evm\_defconfighmj7)ubaubah|jFubeh|jwubj4)r>)}r?)(hlUh~}r@)(h]h]h]h]h]uhmjJ%h]rA)(j9)rB)}rC)(hlUh~}rD)(h]h]h]h]h]uhmj>)h]rE)h)rF)}rG)(hlX K2G GP EVMrH)hmjB)hwhh|hh~}rI)(h]h]h]h]h]uhKh]rJ)hX K2G GP EVMrK)rL)}rM)(hljH)hmjF)ubaubah|jFubj9)rN)}rO)(hlUh~}rP)(h]h]h]h]h]uhmj>)h]rQ)h)rR)}rS)(hlXk2g\_evm\_defconfighmjN)hwhh|hh~}rT)(h]h]h]h]h]uhKh]rU)hXk2g_evm_defconfigrV)rW)}rX)(hlXk2g\_evm\_defconfighmjR)ubaubah|jFubj9)rY)}rZ)(hlUh~}r[)(h]h]h]h]h]uhmj>)h]h|jFubj9)r\)}r])(hlUh~}r^)(h]h]h]h]h]uhmj>)h]h|jFubj9)r_)}r`)(hlUh~}ra)(h]h]h]h]h]uhmj>)h]rb)h)rc)}rd)(hlXk2g\_evm\_defconfighmj_)hwhh|hh~}re)(h]h]h]h]h]uhKh]rf)hXk2g_evm_defconfigrg)rh)}ri)(hlXk2g\_evm\_defconfighmjc)ubaubah|jFubj9)rj)}rk)(hlUh~}rl)(h]h]h]h]h]uhmj>)h]rm)h)rn)}ro)(hlXk2g\_evm\_defconfighmjj)hwhh|hh~}rp)(h]h]h]h]h]uhKh]rq)hXk2g_evm_defconfigrr)rs)}rt)(hlXk2g\_evm\_defconfighmjn)ubaubah|jFubj9)ru)}rv)(hlUh~}rw)(h]h]h]h]h]uhmj>)h]h|jFubj9)rx)}ry)(hlUh~}rz)(h]h]h]h]h]uhmj>)h]h|jFubj9)r{)}r|)(hlUh~}r})(h]h]h]h]h]uhmj>)h]r~)h)r)}r)(hlXk2g\_evm\_defconfighmj{)hwhh|hh~}r)(h]h]h]h]h]uhKh]r)hXk2g_evm_defconfigr)r)}r)(hlXk2g\_evm\_defconfighmj)ubaubah|jFubeh|jwubj4)r)}r)(hlUh~}r)(h]h]h]h]h]uhmjJ%h]r)(j9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]r)h)r)}r)(hlXK2G ICEr)hmj)hwhh|hh~}r)(h]h]h]h]h]uhKh]r)hXK2G ICEr)r)}r)(hlj)hmj)ubaubah|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]r)h)r)}r)(hlXk2g\_evm\_defconfighmj)hwhh|hh~}r)(h]h]h]h]h]uhKh]r)hXk2g_evm_defconfigr)r)}r)(hlXk2g\_evm\_defconfighmj)ubaubah|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubeh|jwubj4)r)}r)(hlUh~}r)(h]h]h]h]h]uhmjJ%h]r)(j9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]r)h)r)}r)(hlXOMAP-L138 LCDKr)hmj)hwhh|hh~}r)(h]h]h]h]h]uhKh]r)hXOMAP-L138 LCDKr)r)}r)(hlj)hmj)ubaubah|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]r)h)r)}r)(hlXomapl138\_lcdk\_defconfighmj)hwhh|hh~}r)(h]h]h]h]h]uhKh]r)hXomapl138_lcdk_defconfigr)r)}r)(hlXomapl138\_lcdk\_defconfighmj)ubaubah|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]r)h)r)}r)(hlXomapl138\_lcdk\_defconfighmj)hwhh|hh~}r)(h]h]h]h]h]uhKh]r)hXomapl138_lcdk_defconfigr)r)}r)(hlXomapl138\_lcdk\_defconfighmj)ubaubah|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubj9)r)}r)(hlUh~}r)(h]h]h]h]h]uhmj)h]h|jFubeh|jwubeh|jubeh|jubaubh)r)}r)(hlXThen:r)hmhohwhh|hh~}r)(h]h]h]h]h]uhKhhh]r)hXThen:r)r)}r)(hlj)hmj)ubaubjr)r)}r)(hlX# Use 'am335x_evm' and 'AM335x GP EVM' in this example $ make CROSS_COMPILE=arm-linux-gnueabihf- O=am335x_evm am335x_evm_defconfig $ make CROSS_COMPILE=arm-linux-gnueabihf- O=am335x_evmhmhohwhh|juh~}r)(hhh]h]h]h]h]uhKhhh]r)hX# Use 'am335x_evm' and 'AM335x GP EVM' in this example $ make CROSS_COMPILE=arm-linux-gnueabihf- O=am335x_evm am335x_evm_defconfig $ make CROSS_COMPILE=arm-linux-gnueabihf- O=am335x_evmr)r)}r)(hlUhmj)ubaubh)r)}r)(hlXiNote that not all possible build targets for a given platform are listed here as the community has additional build targets that are not supported by TI. To find these read the 'boards.cfg' file and look for the build target listed above. And please note that the main config file will leverage other files under include/configs, as seen by #include statements.r)hmhohwhh|hh~}r*(h]h]h]h]h]uhKhhh]r*hXiNote that not all possible build targets for a given platform are listed here as the community has additional build targets that are not supported by TI. To find these read the 'boards.cfg' file and look for the build target listed above. And please note that the main config file will leverage other files under include/configs, as seen by #include statements.r*r*}r*(hlj)hmj)ubaubjC)r*}r*(hlX Boot Flowr*hmhohwhh|jGh~}r*(h]r *U boot-flowr *ah]h]h]h]r *hBauhNhhh]r *hX Boot Flowr *r*}r*(hlj*hmj*ubaubh)r*}r*(hlX!Booting the Linux kernel on an embedded platform is not as simple as simply pointing a program counter to the kernel location and letting the processor run. This section will review the four bootloader software stages that must be run before the kernel can be booted and run on the device.r*hmhohwhh|hh~}r*(h]h]h]h]h]uhKhhh]r*hX!Booting the Linux kernel on an embedded platform is not as simple as simply pointing a program counter to the kernel location and letting the processor run. This section will review the four bootloader software stages that must be run before the kernel can be booted and run on the device.r*r*}r*(hlj*hmj*ubaubh)r*}r*(hlX_Application processors such as the the AM335x are complex pieces of hardware, but have limited internal RAM (e.g., 128KB). Because of this limited amount of RAM, multiple bootloader stages are needed. These bootloader stages systematically unlock the full functionality of the device so that all complexities of the device are available to the kernel.r*hmhohwhh|hh~}r*(h]h]h]h]h]uhKhhh]r*hX_Application processors such as the the AM335x are complex pieces of hardware, but have limited internal RAM (e.g., 128KB). Because of this limited amount of RAM, multiple bootloader stages are needed. These bootloader stages systematically unlock the full functionality of the device so that all complexities of the device are available to the kernel.r*r*}r*(hlj*hmj*ubaubh)r *}r!*(hlX*There are four distinct bootloader stages:r"*hmhohwhh|hh~}r#*(h]h]h]h]h]uhKhhh]r$*hX*There are four distinct bootloader stages:r%*r&*}r'*(hlj"*hmj *ubaubj)r(*}r)*(hlX/.. Image:: /images/U-Boot_Boot_Order_32bit.png hmhohwhh|jh~}r**(UuriX"images/U-Boot_Boot_Order_32bit.pngr+*h]h]h]h]j}r,*U*j+*sh]uhKhhh]ubj)r-*}r.*(hlUhmhohwhh|jh~}r/*(jU.h]h]h]j Uh]h]j j uhKhhh]r0*j )r1*}r2*(hlX ROM Code hmj-*hwhh|jh~}r3*(h]h]h]h]h]uhNhhh]r4*h)r5*}r6*(hlXROM Coder7*hmj1*hwhh|hh~}r8*(h]h]h]h]h]uhKh]r9*hXROM Coder:*r;*}r<*(hlj7*hmj5*ubaubaubaubh)r=*}r>*(hlXfThe first stage bootloader is housed in ROM on the device. The ROM code is the first block of code that is automatically run on device start-up or after power-on reset (POR). The ROM bootloader code is hardcoded into the device and cannot be changed by the user. Because of this, it is important to get an understanding of what exactly the ROM code is doing.r?*hmhohwhh|hh~}r@*(h]h]h]h]h]uhKhhh]rA*hXfThe first stage bootloader is housed in ROM on the device. The ROM code is the first block of code that is automatically run on device start-up or after power-on reset (POR). The ROM bootloader code is hardcoded into the device and cannot be changed by the user. Because of this, it is important to get an understanding of what exactly the ROM code is doing.rB*rC*}rD*(hlj?*hmj=*ubaubh)rE*}rF*(hlX$The ROM code has two main functions:rG*hmhohwhh|hh~}rH*(h]h]h]h]h]uhKhhh]rI*hX$The ROM code has two main functions:rJ*rK*}rL*(hljG*hmjE*ubaubj#)rM*}rN*(hlUhmhohwhh|j&h~}rO*(j(X*h]h]h]h]h]uhKhhh]rP*(j )rQ*}rR*(hlXConfiguration of the device and initialization of primary peripherals such as stack setup, configuring the Watchdog Timer (see TRM for details) as well as the PLL and system clocks configurationhmjM*hwhh|jh~}rS*(h]h]h]h]h]uhNhhh]rT*h)rU*}rV*(hlXConfiguration of the device and initialization of primary peripherals such as stack setup, configuring the Watchdog Timer (see TRM for details) as well as the PLL and system clocks configurationrW*hmjQ*hwhh|hh~}rX*(h]h]h]h]h]uhKh]rY*hXConfiguration of the device and initialization of primary peripherals such as stack setup, configuring the Watchdog Timer (see TRM for details) as well as the PLL and system clocks configurationrZ*r[*}r\*(hljW*hmjU*ubaubaubj )r]*}r^*(hlXReadies the device for next bootloader by checking boot sources for next stage of bootloader (SPL) as well as loading the actual next stage bootloader code into memory and starting it hmjM*hwhh|jh~}r_*(h]h]h]h]h]uhNhhh]r`*h)ra*}rb*(hlXReadies the device for next bootloader by checking boot sources for next stage of bootloader (SPL) as well as loading the actual next stage bootloader code into memory and starting itrc*hmj]*hwhh|hh~}rd*(h]h]h]h]h]uhKh]re*hXReadies the device for next bootloader by checking boot sources for next stage of bootloader (SPL) as well as loading the actual next stage bootloader code into memory and starting itrf*rg*}rh*(hljc*hmja*ubaubaubeubh)ri*}rj*(hlXxThe list of booting devices that the ROM code will search through for the second stage bootloader is configured by the voltage levels set on the devices SYSBOOT pins on startup. These pins also set other boot parameters (i.e. expected crystal frequency, bus width of external memory). For more information on the SYSBOOT pins and associated boot parameters see the device TRM.rk*hmhohwhh|hh~}rl*(h]h]h]h]h]uhKhhh]rm*hXxThe list of booting devices that the ROM code will search through for the second stage bootloader is configured by the voltage levels set on the devices SYSBOOT pins on startup. These pins also set other boot parameters (i.e. expected crystal frequency, bus width of external memory). For more information on the SYSBOOT pins and associated boot parameters see the device TRM.rn*ro*}rp*(hljk*hmji*ubaubj)rq*}rr*(hlUhmhohwhh|jh~}rs*(jU.jsKh]h]h]j Uh]h]j j uhKhhh]rt*j )ru*}rv*(hlX SPL or MLO hmjq*hwhh|jh~}rw*(h]h]h]h]h]uhNhhh]rx*h)ry*}rz*(hlX SPL or MLOr{*hmju*hwhh|hh~}r|*(h]h]h]h]h]uhKh]r}*hX SPL or MLOr~*r*}r*(hlj{*hmjy*ubaubaubaubh)r*}r*(hlXThe second stage bootloader is known as the SPL (Secondary Program Loader), but is sometimes referred to as the MLO (MMC Card Loader). The SPL is the first stage of U-Boot, and must be loaded from one of the boot sources into internal RAM. The SPL has very limited configuration or user interaction, and mainly serves to initialize the external DDR memory and set-up the boot process for the next bootloader stage: U-Boot.r*hmhohwhh|hh~}r*(h]h]h]h]h]uhKhhh]r*hXThe second stage bootloader is known as the SPL (Secondary Program Loader), but is sometimes referred to as the MLO (MMC Card Loader). The SPL is the first stage of U-Boot, and must be loaded from one of the boot sources into internal RAM. The SPL has very limited configuration or user interaction, and mainly serves to initialize the external DDR memory and set-up the boot process for the next bootloader stage: U-Boot.r*r*}r*(hlj*hmj*ubaubj)r*}r*(hlUhmhohwhh|jh~}r*(jU.jsKh]h]h]j Uh]h]j j uhKhhh]r*j )r*}r*(hlXU-Boot hmj*hwhh|jh~}r*(h]h]h]h]h]uhNhhh]r*h)r*}r*(hlXU-Bootr*hmj*hwhh|hh~}r*(h]h]h]h]h]uhKh]r*hXU-Bootr*r*}r*(hlj*hmj*ubaubaubaubh)r*}r*(hlXU-Boot allows for powerful command-based control over the kernel boot environment via a serial terminal. The user has control over a number of parameters such as boot arguments and the kernel boot command. In addition, U-Boot environment variables can be configured. These environment variables are stored in the **uEnv.txt** file on your storage medium or directly in a Flash-based memory if configured such. These environment variables can be viewed, modified, and saved using the **env print**, **env set**, and **env save** commands, respectively. U-Boot is also a very useful tool to program and manipulate a wide range of external memory devices as well as a helpful aid during custom board bringup.hmhohwhh|hh~}r*(h]h]h]h]h]uhKhhh]r*(hX9U-Boot allows for powerful command-based control over the kernel boot environment via a serial terminal. The user has control over a number of parameters such as boot arguments and the kernel boot command. In addition, U-Boot environment variables can be configured. These environment variables are stored in the r*r*}r*(hlX9U-Boot allows for powerful command-based control over the kernel boot environment via a serial terminal. The user has control over a number of parameters such as boot arguments and the kernel boot command. In addition, U-Boot environment variables can be configured. These environment variables are stored in the hmj*ubj)r*}r*(hlX **uEnv.txt**h~}r*(h]h]h]h]h]uhmj*h]r*hXuEnv.txtr*r*}r*(hlUhmj*ubah|j'ubhX file on your storage medium or directly in a Flash-based memory if configured such. These environment variables can be viewed, modified, and saved using the r*r*}r*(hlX file on your storage medium or directly in a Flash-based memory if configured such. These environment variables can be viewed, modified, and saved using the hmj*ubj)r*}r*(hlX **env print**h~}r*(h]h]h]h]h]uhmj*h]r*hX env printr*r*}r*(hlUhmj*ubah|j'ubhX, r*r*}r*(hlX, hmj*ubj)r*}r*(hlX **env set**h~}r*(h]h]h]h]h]uhmj*h]r*hXenv setr*r*}r*(hlUhmj*ubah|j'ubhX, and r*r*}r*(hlX, and hmj*ubj)r*}r*(hlX **env save**h~}r*(h]h]h]h]h]uhmj*h]r*hXenv saver*r*}r*(hlUhmj*ubah|j'ubhX commands, respectively. U-Boot is also a very useful tool to program and manipulate a wide range of external memory devices as well as a helpful aid during custom board bringup.r*r*}r*(hlX commands, respectively. U-Boot is also a very useful tool to program and manipulate a wide range of external memory devices as well as a helpful aid during custom board bringup.hmj*ubeubj)r*}r*(hlUhmhohwhh|jh~}r*(jU.jsKh]h]h]j Uh]h]j j uhKhhh]r*j )r*}r*(hlX Linux Kernel hmj*hwhh|jh~}r*(h]h]h]h]h]uhNhhh]r*h)r*}r*(hlX Linux Kernelr*hmj*hwhh|hh~}r*(h]h]h]h]h]uhKh]r*hX Linux Kernelr*r*}r*(hlj*hmj*ubaubaubaubh)r*}r*(hlX**zImage** is the compressed kernel image wrapped with header info that describes the kernel. This header includes the target architecture, the operating system, kernel size, entry points, etc. The loading of the kernel image is typically performed through the use of scripts stored in the U-Boot environment (all starting with the **bootcmd** ENV variable that gets executed after the autoboot countdown expires or manually by entering the **boot** command at the U-Boot prompt). This also involves passing a board- specific device tree blob (DTB) as an argument to U-Boot's **bootz** command that will extract and start the actual kernel.hmhohwhh|hh~}r*(h]h]h]h]h]uhKhhh]r*(j)r*}r*(hlX **zImage**h~}r*(h]h]h]h]h]uhmj*h]r*hXzImager*r*}r*(hlUhmj*ubah|j'ubhXB is the compressed kernel image wrapped with header info that describes the kernel. This header includes the target architecture, the operating system, kernel size, entry points, etc. The loading of the kernel image is typically performed through the use of scripts stored in the U-Boot environment (all starting with the r*r*}r*(hlXB is the compressed kernel image wrapped with header info that describes the kernel. This header includes the target architecture, the operating system, kernel size, entry points, etc. The loading of the kernel image is typically performed through the use of scripts stored in the U-Boot environment (all starting with the hmj*ubj)r*}r*(hlX **bootcmd**h~}r*(h]h]h]h]h]uhmj*h]r*hXbootcmdr*r*}r*(hlUhmj*ubah|j'ubhXb ENV variable that gets executed after the autoboot countdown expires or manually by entering the r*r*}r*(hlXb ENV variable that gets executed after the autoboot countdown expires or manually by entering the hmj*ubj)r*}r*(hlX**boot**h~}r*(h]h]h]h]h]uhmj*h]r*hXbootr*r*}r*(hlUhmj*ubah|j'ubhX command at the U-Boot prompt). This also involves passing a board- specific device tree blob (DTB) as an argument to U-Boot's r*r*}r*(hlX command at the U-Boot prompt). This also involves passing a board- specific device tree blob (DTB) as an argument to U-Boot's hmj*ubj)r*}r*(hlX **bootz**h~}r*(h]h]h]h]h]uhmj*h]r*hXbootzr*r*}r+(hlUhmj*ubah|j'ubhX7 command that will extract and start the actual kernel.r+r+}r+(hlX7 command that will extract and start the actual kernel.hmj*ubeubeubhwhh|Usystem_messager+h~}r+(h]UlevelKh]h]Usourcehzh]h]UlineKUtypeUINFOr+uhKhhh]r+h)r+}r +(hlX:Enumerated list start value not ordinal-1: "2" (ordinal 2)h~}r +(h]h]h]h]h]uhmhjh]r +hX:Enumerated list start value not ordinal-1: "2" (ordinal 2)r +r +}r+(hlUhmj+ubah|hubaubhi)r+}r+(hlUhmhohwhh|j+h~}r+(h]UlevelKh]h]Usourcehzh]h]UlineKUtypej+uhKhhh]r+h)r+}r+(hlX:Enumerated list start value not ordinal-1: "3" (ordinal 3)h~}r+(h]h]h]h]h]uhmj+h]r+hX:Enumerated list start value not ordinal-1: "3" (ordinal 3)r+r+}r+(hlUhmj+ubah|hubaubhi)r+}r+(hlUhmhohwhh|j+h~}r+(h]UlevelKh]h]Usourcehzh]h]UlineKUtypej+uhKhhh]r+h)r+}r+(hlX:Enumerated list start value not ordinal-1: "4" (ordinal 4)h~}r +(h]h]h]h]h]uhmj+h]r!+hX:Enumerated list start value not ordinal-1: "4" (ordinal 4)r"+r#+}r$+(hlUhmj+ubah|hubaubhi)r%+}r&+(hlUhmj}hwhh|j+h~}r'+(h]UlevelKh]h]Usourcehh]h]UlineMUtypej+uhMhhh]r(+h)r)+}r*+(hlX`Possible incomplete section title. Treating the overline as ordinary text because it's so short.h~}r++(h]h]h]h]h]uhmj%+h]r,+hX`Possible incomplete section title. Treating the overline as ordinary text because it's so short.r-+r.+}r/+(hlUhmj)+ubah|hubaubhi)r0+}r1+(hlUh~}r2+(h]UlevelKh]h]Usourcehh]h]UlineMUtypej+uhmjh]r3+h)r4+}r5+(hlX`Blank line missing before literal block (after the "::")? Interpreted as a definition list item.h~}r6+(h]h]h]h]h]uhmj0+h]r7+hX`Blank line missing before literal block (after the "::")? Interpreted as a definition list item.r8+r9+}r:+(hlUhmj4+ubah|hubah|j+ubhi)r;+}r<+(hlUhmjhwhzh|j+h~}r=+(h]UlevelKh]h]Usourcehzh]h]UlineKUtypej+uhKDhhh]r>+h)r?+}r@+(hlX:Enumerated list start value not ordinal-1: "2" (ordinal 2)h~}rA+(h]h]h]h]h]uhmj;+h]rB+hX:Enumerated list start value not ordinal-1: "2" (ordinal 2)rC+rD+}rE+(hlUhmj?+ubah|hubaubeUcurrent_sourcerF+NU decorationrG+NUautofootnote_startrH+KUnameidsrI+}rJ+(hjhj6hj"h jh j8h j$h jh jxhje hjrhjJhj hjhj hjhjhj hju hhhj#hjhj{hj hjO hj"hjh j h!jp h"jh#jFh$j"h%jhh&jh'jh(jh)j h*jJ$h+jh,j h-j h.j h/j h0hh1jh2jh3jh4j h5j`h6jh7j h8jh9hh:j$h;j hj#h?jh@j !hAjb$hBj *hCjhDj hEjUhFjIhGj hHjhIjhJjhKj hLjhMjG hNjhOjhPj'hQj]hRjhSjhTj hUjhVjIhWj;#hXj>hYjhZjh[j5h\j`h]jh^jh_jh`jhaj|$hbjbhcj hdjTuh]rK+(h)rL+}rM+(hlXBhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_U-Boothmhhwhzh|hh~}rN+(hhh]h]h]h]h]uhKhhh]rO+hXBhttp://processors.wiki.ti.com/index.php/Processor_SDK_Linux_U-BootrP+rQ+}rR+(hlUhmjL+ubaubhuehlUU transformerrS+NU footnote_refsrT+}rU+UrefnamesrV+}rW+Usymbol_footnotesrX+]rY+Uautofootnote_refsrZ+]r[+Usymbol_footnote_refsr\+]r]+U citationsr^+]r_+hhU current_liner`+NUtransform_messagesra+]rb+Ureporterrc+NUid_startrd+KU autofootnotesre+]rf+U citation_refsrg+}rh+Uindirect_targetsri+]rj+Usettingsrk+(cdocutils.frontend Values rl+orm+}rn+(Ufootnote_backlinksro+KUrecord_dependenciesrp+NU rfc_base_urlrq+Uhttps://tools.ietf.org/html/rr+U tracebackrs+Upep_referencesrt+NUstrip_commentsru+NU toc_backlinksrv+jFU language_coderw+Uenrx+U datestampry+NU report_levelrz+KU _destinationr{+NU halt_levelr|+KU strip_classesr}+NhNUerror_encoding_error_handlerr~+Ubackslashreplacer+Udebugr+NUembed_stylesheetr+Uoutput_encoding_error_handlerr+Ustrictr+U sectnum_xformr+KUdump_transformsr+NU docinfo_xformr+KUwarning_streamr+NUpep_file_url_templater+Upep-%04dr+Uexit_status_levelr+KUconfigr+NUstrict_visitorr+NUcloak_email_addressesr+Utrim_footnote_reference_spacer+Uenvr+NUdump_pseudo_xmlr+NUexpose_internalsr+NUsectsubtitle_xformr+U source_linkr+NUrfc_referencesr+NUoutput_encodingr+Uutf-8r+U source_urlr+NUinput_encodingr+U utf-8-sigr+U_disable_configr+NU id_prefixr+UU tab_widthr+KUerror_encodingr+UUTF-8r+U_sourcer+X^/home/gtbldadm/nightlybuilds/processor-sdk-doc/source/linux/Foundational_Components_U-Boot.rstr+Ugettext_compactr+U generatorr+NUdump_internalsr+NU smart_quotesr+U pep_base_urlr+U https://www.python.org/dev/peps/r+Usyntax_highlightr+Ulongr+Uinput_encoding_error_handlerr+j+Uauto_id_prefixr+Uidr+Udoctitle_xformr+Ustrip_elements_with_classesr+NU _config_filesr+]Ufile_insertion_enabledr+U raw_enabledr+KU dump_settingsr+NubUsymbol_footnote_startr+KUidsr+}r+(jjjjhhj6j2j8j4hhjjjjjj|je j` jrjnjJjDjjjjj j jjjp hqjjhhj !j!j j j j jjjjjbj^j j jjjjj>j:j j{ j"j"j`j\jhjcjjjjj j jIjEjj}j{jwj j jjj'j#jhsjjjjjjjjj j jFjBj#j#j j j`j\jjhhuj$j$j j j#j#jjj j jb$j]$j j ju jq j *j*jjjjj|$jw$jO jK j j jjjjjjj jj j| jJ$hojjj]jYj jj"jjxjsjjjIjDj;#j6#jjjjj5j0j"j"jUjPj j j j j j j$j$jG jC jTjPjjjjuUsubstitution_namesr+}r+h|hh~}r+(h]h]h]Usourcej+h]h]uU footnotesr+]r+Urefidsr+}r+ub.