TI OMAP Bootloader Project 关于启动过程

u-boot编译构成之 MLO(1) UBOOT启动过程 SOC内部ROM,依据外部硬件设置的启动跳线,从相应的介质启动系统。启动跳线设置请看芯片手册。 1.系统上电; 2.SOC 内部ROM启动; 3.依据硬件设置的启动方式,从相应的介质下载MLO到soc内部的ram中运行; 4. MLO运行以后再去加载u-boot.img 到RAM中以后; 5.此时MLO退出,U-Boot.img运行; 本文档硬件:Ti J6entry (Dra71x ) Uboot 源码:Ti 官网下载 制作MLO,... 阅读详情

以下wiki详细讲解了启动过程

http://omappedia.org/wiki/Bootloader_Project


http://omappedia.org/wiki/OMAP3_U-Boot_TODO



Bootloader Project

Contents

  [hide]

[edit]OMAP U-boot

Das U-Boot is the bootloader typically used on OMAP development platform.

X-Loader is a tiny first stage minimal bootloader which loads up u-boot as explained by this wiki.

Developer Reference: OMAP3 U-Boot TODO things for mainline U-boot Support.

[edit]OMAP Boot Sequence

The OMAP processor follows a 2 stage boot process. The first stage is loaded into the internal static RAM by the ROM code. Because the internal static RAM is very small (64k), the first stage loader is needed to initialize memory and enough of the peripheral devices to access and load the second stage loader into main memory. It is the job of the second stage loader to initialize the remaining hardware and prepare the system for kernel boot.(detail documentation available from TI, see the Initialization chapter of the Technical Documents/OMAP34xx on this page)


[edit]First Stage Boot

The internal ROM Code will attempt to boot from several different peripherals including but not limited to: Serial(UART3), SD Card(MMC1 and MMC2), Nand and USB. The order in which the peripherals are attempted is determine by a set of GPIO configuration pins referred to as SYS_BOOT. The default SYS_BOOT configuration for the Zoom2 appears to be: USB, Serial(UART3), SD Card(MM1), and NAND flash.

The documentation of SYS_BOOT can be found on TI website -- Technical Documents/OMAP34xx Multimedia Device.

The value can be read from physical address 0x480022f0, either using JTAG, or if you have linux running, use devmem2:

# devmem2 0x480022f0 b                           
/dev/mem opened.
Memory mapped at address 0x40020000.
Value at address 0x480022F0 (0x400202f0): 0x2F

Or use this tool: omap34xx-boot-order

Boot stage1.jpg


Serial Boot

A simple ID is written out of the serial port. If the host responds correctly within a short window of time, the ROM will read from the serial port and transfer the data to the internal sram. Control is passed to the start of sram if no errors are detected. UART3 is the only uart for which the ROM will attempt to load from.

SD Card Boot

Assuming there was no answer from the host during serial boot, the ROM looks for an SD Card on the first MMC controller. If a card is found, the ROM then looks for the first FAT32 partition within the partition table. Once the partition is found, the root directory is scanned for a special signed file called "MLO"(x-load binary with a header containing the memory location to load the file and the size of the file). Assuming all is well with the file, it is transfered into the internal sram and control is passed to it. Both MMC1 and MMC2 can be used for booting.

Nand Boot

Assuming the SD Card boot was unable to complete successfully, the ROM attempts to load the first sector of Nand. If the sector is bad, corrupt, or blank, the ROM will try the next sector (up to 4) before exiting. Once a good sector is found, the ROM transfers the contents to sram and transfers control to it.

[edit]Second Stage Boot

The second stage of the boot is done by the x-loader installed from the first stage. There are different versions of the x-loader corresponding to each of the devices that can be loaded from. It is the job of the x-loader to transfer the 2nd stage loader into main memory. Usually you will use the x-loader that corresponds to the type of boot you are attempting - i.e. you would use the serial x-loader for a serial boot and the nand x-loader for a nand boot. However, you don't have to. For example, you could flash the serial x-loader into the nand. The rom will load from nand and transfer control to the x-loader which will wait for the 2nd stage to be downloaded from the serial port.

Serial Boot

The serial x-loader waits for the host to initiate a kermit connection to reliably transfer large files into main memory. Once the file transfer is completed successfully, control is transfered.


Boot stage2 serial.jpg

SD Card Boot

The SDCard x-loader looks for a FAT32 partition on the first MMC controller and scans the top level directory for a file named "u-boot.bin". It then transfers the file into main memory and transfers control to it.


Boot stage2 SD.jpg


NAND Boot

The nand x-loader expects u-boot to be loaded at the 5th sector (offset 0x00800000). It transfers the image from nand into main memory and transfers control to it.


Boot stage2 NAND.jpg

[edit]Bootloader Overview

Bootloader project contains information regarding the building and flashing procedures for uboot and xloader. These two items are necessary to bring up the zoom2's environment.

Why two bootloaders? The first bootloader, x-loader, is a stripped down version of u-boot designed to run in the on-chip sram of the zoom2. It initializes the main off-chip memory of the system and other necessary device drivers, and then loads the larger bootloader for linux, u-boot. The following steps will build the bootloaders:


  • Ensure that "git" has been installed within the host system. Git is available for download at git-scm.com. For more details on installing and using git please see this wiki page.


[edit]Accessing Uboot source

  • Clone Uboot
# mkdir bootloader
# cd bootloader
# git clone git://git.omapzoom.org/repo/u-boot.git

[edit]Building Uboot

# cd <path_to_u-boot>
# make distclean
# make CROSS_COMPILE=arm-none-linux-gnueabi- omap3430zoom2_config
# make CROSS_COMPILE=arm-none-linux-gnueabi-

Note: If you get "cmd_voltage.c:27: error: inline function 'voltage_info' cannot be declared weak" try an older GCC (CSL 2008q3-72 seems ok) Note: Step above is building for a Zoom2. To build for other boards use respective config from the below table.

U-boot config files

Boardconfig file
4460SDPomap4430sdp_config
4430SDPomap4430sdp_config
3430SDPomap3430sdp_config
3630SDPomap3630sdp_config
3430LDPomap3430labrador_config
Zoom2omap3430zoom2_config
Zoom3omap3630zoom3_config
2430sdpomap2430sdp_config
2420h4omap2420h4_config


  • u-boot.bin is located in <path_to_u-boot>

[edit]Accessing X-loader source

  • Clone X-loader master for OMAP3
# cd bootloader
# git clone  git://git.omapzoom.org/repo/x-loader.git 
  • X-loader for OMAP44xx
# cd bootloader/x-load
# git checkout --track -b omap4_dev origin/omap4_dev
# git pull {to be on latest commit ID } 

[edit]Building Xloader for GP

Warning: u-boot needs to be built before x-loader.

# cd <path_to_x-boot>
# make distclean
# make CROSS_COMPILE=arm-none-linux-gnueabi- omap3430zoom2_config
# make CROSS_COMPILE=arm-none-linux-gnueabi- ift
* Build x-loader for OMAP4460
# cd <path_to_x-boot>
# make sure you are on omap4_dev branch
# make distclean
# make CROSS_COMPILE=arm-none-linux-gnueabi- omap4460sdp_config
# make CROSS_COMPILE=arm-none-linux-gnueabi- ift

Note: Step above is building for Zoom2 and for Zoom1(LDP). For other boards use respective config file from below tables

X-loader config files

Boardconfig file
4460SDPomap4460sdp_config
4430SDPomap4430sdp_config
3430SDPomap3430sdp_config
3630SDPomap3630sdp_config
3630SDP 1GBomap3630sdp_1G_config
3430LDPomap3430labrador_config
Zoom2omap3430zoom2_config
Zoom3omap3630zoom3_config
2430sdpomap2430sdp_config
2420h4omap2420h4_config

To build X-loader to boot over a serial connection, use "omap3430labradordownload_config"

  • MLO is located in <path_to_x-loader>

[edit]Building Xloader for EMU

Warning: Build x-load.bin using correct config file for 4430/4460 .

Warning: Download mshield-dk lite .

  • create x-load.bin for OMAP44xx <same procedure for GP/EMU/HS>
  • For OMAP4430 ES2.0 EMU/HS
# cd mshield-dk-root-folder
# ./generate_MLO OMAP4430 ES2.0 x-load.bin
# MLO will be located in root mshield-dk folder
  • For OMAP4430 ES2.1 EMU/HS
# cd mshield-dk-root-folder
# ./generate_MLO OMAP4430 ES2.1 x-load.bin
# MLO will be located in root mshield-dk folder
  • For OMAP4430 ES2.2 EMU/HS
# cd mshield-dk-root-folder
# ./generate_MLO OMAP4430 ES2.2 x-load.bin
# MLO will be located in root mshield-dk folder
  • For OMAP4430 ES2.3 EMU/HS
# cd mshield-dk-root-folder
# ./generate_MLO OMAP4430 ES2.3 x-load.bin
# MLO will be located in root mshield-dk folder
  • For OMAP4460 ES1.0 EMU/HS
# cd mshield-dk-root-folder
# ./generate_MLO OMAP4460 ES1.0 x-load.bin
# MLO will be located in root mshield-dk folder

[edit]Flashing

Refer to Zoom Flashing to review flashing methods for Zoom1/Zoom2/Zoom3.

Refer to 3630SDP Flashing to review flashing methods for 3630SDP board.

Refer to eMMC Boot to review flashing and boot methods from eMMC device.

Refer to Uimage-flasher which is a combination of uImage+initramfs along with g_file_storage.ko. This solution lets the PandaBoard export its SD card over the USB.

[edit]Upstreaming U-boot

U-boot upstreaming is being carried out as a separate project. Please refer to the following link for more details.

U-boot Upstreaming Project


Windows Mobile 6.5.3嵌入式开发实战:工业系统逆向与驱动定制指南 Windows Mobile虽已退出消费市场,但其内核架构仍是理解现代移动操作系统底层原理的重要范本。它基于Windows CE微内核,采用对象存储、ROM/RAM双区启动和DDI驱动抽象等核心机制,深刻影响了Android Binder、车机OTA及驱动即服务等关键技术演进。作为仍活跃于全球数千个工业现场的存量系统,WM 6.5.3具备可写ROM、设备模拟层(DEL)和CAB签名强制校验等面向嵌入式场景的工程化设计,是学习操作系统如何接管裸机、构建安全可靠固件分发链路的理想教学载体。本文聚焦工业级实操,覆 阅读详情

相关推荐

Windows Embedded CE 6.0 R3:高置信度平台与Silverlight嵌入式UI开发实战

在嵌入式系统开发领域,实时操作系统(RTOS)与图形用户界面(GUI)框架的选择,直接影响着产品的开发效率、硬件控制力与最终用户体验。其核心原理在于,通过成熟的商业平台整合软硬件生态,为开发者提供熟悉的工具链和已验证的组件,从而构建一个“高置信度平台”,显著降低技术门槛与商业风险。这种模式的技术价值在于,它允许开发团队将精力集中于产品核心功能与差异化设计,而非底层通用技术问题的重复解决,尤其适用于对上市周期和成本控制敏感的工业控制、医疗终端、车载信息娱乐等应用场景。本文聚焦的Windows Embedded

weixin_34216107的博客 306

ti-sdk-evm-am335x-05.07 uboot分析(MLO跳转到u-boot之前)

本文主要通过阅读源码及调试揭示了AM335X中u-boot的MLO阶段实现机理。

wuxianglonghaohao的专栏 5956

DSP ti bootloader与在线升级

ti bootloader:SCI/SPI/CAN/I2C等特定的外设引脚,配合ti串口烧录工具(ti官网搜索controlSUITE下载安装,在ti目录下serial_flash_programmer.exe)通过PC cmd指令进行操作下载。 优点:可直接调用flashAPI(),不需额外的协议指令; 缺点:必须通过GPIO跳线使芯片进入对应的引导模式,比如CAN引导是一组电平组合,SCI引导...

debugcc2530的博客 1万+

[uboot]MLO和uboot-spl.bin, uboot.img和uboot.bin

前段時間使用TI的am4378芯片,發現系統在SD卡啟動的時候,啟動文件使用的是MLO和uboot.img;而Norflash和eMMC啟動的時候使用的是 uboot-spl.bin和uboot.bin,有如下疑問: 1.MLO和Uboot-spl.bin有什麽區別?uboot.img和uboot.bin有什麽區別? 2.為什麽後者需要Norflash再配合eMMC,而不是直接eMMC? ...

z1026544682的专栏 1566

【DSP应用开发】TI DSP28377S 二次bootloader开发

本文介绍了 DSP二次bootloader程序的开发注意事项

qq_41443596的博客 3183

TI OMAP平台BSP学习笔记之 - UBOOT(1)

1. Bootloader 和 TI Uboot Bootloader的一种,用来引导系统,通常HLOS如LINUX,WINDOWS等系统的镜像保存在硬盘、EMMC等介质中,Bootloader的主要功能是为这些系统准备硬件环境,然后将HLOS系统加载到RAM中,最后把HLOS给运行起来。通常在IC、特别是嵌入式IC复位后,它会跳转到片内ROM去运行特定的固化代码(也可能是上电后从特定的...

佛系代码阅读家的博客 1308

TI DSP BootLoader技术要点概述

概述 在开发一款产品特别是要装到密闭空间里面的产品的时候,经常要考虑到程序的更新问题,更新程序的方法有使用芯片厂家自带的功能的(通过拉某个引脚,设置芯片启动某块boot程序,然后引导将自己的程序下载进去),有自己写BootLoader程序的,使用厂家自带功能更新程序方便,但必须要用厂家的通讯协议,板卡设计时必须留出程序升级要求的通讯接口,如果这个通讯接口后期使用还好,后期没用就占用了BOM成本,如果板卡对外有自己的通讯口,可以写一个BootLoader程序代替厂家的程序升级功能。TI的DSP在工控领域应用较

qq_27379251的博客 6679

TI Cortex-M3 BootLoader资料

网上收集到的TI Cortex-M3有关BootLoader的资料。

TI的bootloader启动过程——以UART为例

TM4C123G用的是Cortex-M4架构,内存地址如下图,flash起始地址为0x00000000,RAM起始地址为0x20000000。开始debug,PC指针的起始位置是“_c_int00()”函数的入口。在bootloader程序里,_c_int00()这个函数被定义在bl_startup_ccs.s这个汇编文件中,可以看............

Hello.Aaric的博客 2218

TI 6000 DSP bootloader 详解

TI 6000 DSP bootloader 详解

TI DSP TMS320C6678 bootloader开发流程.pdf

TI DSP TMS320C6678 bootloader开发详细说明, 详细介绍了bootloader开发的具体流程,关键点说明。使用前需正确安装TI官方SDK,得到CCS开发环境,CCS使用见对应SDK用户指导。

CCS3.3迁移到CCS10:嵌入式开发范式跃迁实战指南

嵌入式开发中,IDE迁移不仅是工具更换,更是底层构建体系、硬件抽象机制与调试范式的系统性升级。从传统裸机寄存器操作到标准化外设驱动库(PDK),从手工Makefile到CMake自动化构建,从JTAG单步调试到全栈Trace分析,本质是向可移植、可验证、可扩展的现代嵌入式工程实践演进。尤其在TI C6000系列和AMx平台开发中,printf重定向、中断向量管理、HAL封装等关键环节直接决定迁移成败。本文聚焦CCS3.3到CCS10的真实迁移路径,覆盖编译器差异、RTOS集成、多核同步及真机验证等核心挑战,

weixin_33812433的博客 312

TI OMAP4460 DATESHEET

TI OMAP4460 DATESHEET Data Manual

嵌入式芯片工程师能力成长地图:从点亮LED到读懂芯片手册

嵌入式系统是连接物理世界与数字逻辑的枢纽,其核心在于软硬协同的实时控制能力。理解GPIO电平跳变背后的寄存器操作、UART通信中时序与地回路的物理约束、FreeRTOS任务切换涉及的栈指针与PendSV机制,本质是对微控制器底层原理的具象化掌握。这种能力支撑起STM32开发、芯片驱动编写、电源管理(如8205过流保护)及高性能平台(如RK3588 DDR4时序配置)等真实工程场景。它不依赖框架封装,而根植于示波器实测、手册精读与寄存器级调试——唯有将理论锚定在可验证的硬件行为上,才能跨越从‘能跑通’到‘敢设

weixin_34354173的博客 384

国密SSL实战:手把手教你用Wireshark抓包分析GMTLS协议(附证书链验证技巧)

本文提供了一份国密SSL(GMTLS)协议的实战抓包分析指南。通过详细讲解Wireshark的配置、GMTLS握手流程的捕获与筛选,以及双证书机制和证书链的深度解析,帮助工程师和开发人员掌握使用Wireshark排查国密SSL连接问题、进行密评和协议调试的核心技巧。

rgv234567的博客 503

三菱CNC数据采集实战:从SDK安装到C#代码调试全流程(附完整资源包)

本文为C#开发者提供了三菱CNC数据采集的完整实战指南。详细介绍了从获取并安装核心A2协议SDK、配置Visual Studio开发环境,到理解COM接口文档、封装C#通信类,并构建具备多设备连接与定时采集功能的WinForms应用程序的全流程。文章重点分享了网络调试、异常处理及性能优化等关键实战经验,帮助开发者高效打通工业自动化数据采集链路。

oauth7security的博客 710

嵌入式与芯片能力生长地图:从C语言到软硬协同工程实践

嵌入式系统是连接软件逻辑与物理硬件的核心范式,其本质在于对计算过程的时空可控性建模——从C语言内存布局、时序约束,到外设寄存器映射与中断响应机制。技术价值体现在将抽象算法转化为可验证的物理行为,支撑智能终端、工业控制、边缘AI等关键场景。实践中需贯通芯片数据手册解读、STM32底层驱动开发、电源管理芯片(如8205)功能图解分析及USB虚拟串口通信等硬核能力。本文聚焦电子信息本科生四年的能力进阶路径,以‘可交付物’为锚点,构建覆盖硬件抽象、调试直觉与跨域协同的工程成长体系。

weixin_34161029的博客 195

DP3(3D Diffusion Policy)算法详解:从点云感知到扩散动作生成

DP3 的全称是:DP3 = 3D Diffusion Policy\boxed{\text{DP3 = 3D Diffusion Policy}}DP3 = 3D Diffusion Policy​对应论文题目是:3D Diffusion Policy: Generalizable Visuomotor Policy Learning via Simple 3D Representations该工作发表于 Robotics: Science and Systems(RSS)2024。DP3 是一种面向机器

u013250861的博客 360

TI DSP TMS320F28335 Bootloader串口升级资源下载

TI DSP TMS320F28335 Bootloader串口升级资源下载 【下载地址】TIDSPTMS320F28335Bootloader串口升级资源下载 本开源项目为德州仪器TMS320F28335系列DSP芯片提供了完整的Bootloader串口升级解决方案。项目包含Bootloader固件、应用测试固件及上位...

gitblog_06747的博客 479

GPU计算板卡设计原理图:735-基于3U VPX的AGX Xavier GPU计算主板

基于3U VPX的 Jetson AGX Xavier GPU计算主板是LINUX环境下软件开发等理想工具。是用于视频处理,相机信号,支持PCIE、USB、RS422、RS232、网口、SPI、I2C等综合性的信号计算主板。3. 支持外接HDMI连接显示器,并支持键盘,鼠标等外接设备进行调试。8 核 ARM v8.2 64 位 CPU、8 MB L2 + 4 MB L3。4路Gigabit Ethernet (10/100/100)link。1路RS232,1路RS485。1路 NVMe PCIeX4。

982

(二)使用VS2022克隆下载C++自制植物大战僵尸游戏教程

本文将介绍如何使用VS2022克隆下载《植物大战僵尸C++自制版本》。Gitee项目地址:Gitee仓库地址Github项目地址:Github仓库地址游戏官网地址(下载可直接运行)游戏官网。

尔灵尔亿的博客 4956

AM335x启动流程(BootRom->MLO->Uboot)

http://blog.chinaunix.net/uid-28458801-id-3486399.html 参考文件: 1,AM335x ARM Cortex-A8 Microprocessors (MPUs) Technical Reference Manual.pdf; 2,am3359.pdf; 1,am335x的cpu上电后,会跳到哪个地址去执行? 答:

be happy 2万+

按角色定制同一张 Fiori 画面:一篇讲透 SAP Fiori UI Adaptation for Roles 的版本、优先级、视图迁移与安全边界

摘要:SAP Fiori应用中常见的问题并非功能缺失,而是同一应用被不同岗位用于不同工作流时导致界面难以满足各方需求。SAP的"角色适配UI"机制允许在不修改后端逻辑或创建新应用的情况下,为不同角色定制界面呈现。该机制包含多套界面适配方案,按用户角色自动匹配显示,同时保持统一的应用入口。实施时需注意:适配方案与原始应用共享版本管理;需设置"默认界面层";多角色用户通过优先级机制确定显示方案;界面隐藏不等于权限控制,数据安全仍需后端保障。该方案能有效解决跨岗位的界面适配

2007 年 ~ 2025 年,深耕 SAP 技术 18 年 151

OMAP Bootloader

OMAP Boot Sequence  http://www.omapedia.org/wiki/Bootloader_Project 两段式boot方式 First Stage Boot 两段式boot process,第一段由ROM代码load到内部static RAM(比较小,64K)   内部的ROM代码会尝试从不同外设启动,包括Serial(UART3),SD Car

tronteng的专栏 1066

数字电路逻辑与设计实验一 门电路逻辑功能及测试

(1)选二输入四异或门电路 74LS86,按图 1-8 接线,输入端 1、2、4、5 接逻辑开 关(S1~S4),输出端 A、B、Y 接电平显示发光二极管.用六反相器(非门)按图 1-11 接线,输入 80KHz 连续脉冲,用双踪示波器测输入, 输出相位差,计算每个门的平均传输延迟时间的 tpd 值。测试不同的输入组合:对门电路进行全面的测试,尝试不同的输入组合,包括各种可能的逻辑状态。检查门电路的输入:确认门电路的输入是否正确,并且输入信号的电平符合门电路的规格要求。确保输入信号的稳定性和准确性。

欢迎交流学习心得 2万+

R语言使用survminer包的ggcompetingrisks函数可视化竞争风险的累积事件曲线、使用可视化对象的mapping属性自定义修改、配置颜色分组及线条类型

R语言使用survminer包的ggcompetingrisks函数可视化竞争风险的累积事件曲线、使用可视化对象的mapping属性自定义修改、配置颜色分组及线条类型

data+scenario+science+insight 1382
上一篇: 一个简单好用的基于git的代码托管网站
下一篇: 步进电动机的工作原理及驱动方法
YasinLeeX
博客等级 码龄19年 380粉丝 310原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

YasinLeeX

再来一杯西湖龙井。

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值