Blame - board/ti/am65x/README - platform/external/u-boot

$ make CROSS_COMPILE=aarch64-linux-gnu- ATF=<path to ATF dir>/build/k3/generic/release/bl31.bin TEE=<path to OPTEE OS dir>/out/arm-plat-k3/core/tee-pager_v2.bin O=/tmp/a53

Lokesh Vutla

0911d95

2018-08-27 15:59:06 +0530

[diff] [blame]

Target Images

--------------

Copy the below images to an SD card and boot:

Lokesh Vutla

6418000

2018-11-02 19:51:11 +0530

[diff] [blame]

146

- sysfw.itb from step 1

Lokesh Vutla

0911d95

2018-08-27 15:59:06 +0530

[diff] [blame]

147

- tiboot3.bin from step 4.1

148

- tispl.bin, u-boot.img from 4.2

Lokesh Vutla

6418000

2018-11-02 19:51:11 +0530

[diff] [blame]

Image formats:

--------------

- tiboot3.bin:

+-----------------------+

155

| X.509 |

156

| Certificate |

157

| +-------------------+ |

158

| | | |

159

| | R5 | |

160

| | u-boot-spl.bin | |

161

| | | |

162

| +-------------------+ |

163

| | | |

164

| | FIT header | |

165

| | +---------------+ | |

166

| | | | | |

167

168

| | +---------------+ | |

169

| +-------------------+ |

170

+-----------------------+

171

172

- tispl.bin

173

+-----------------------+

174

| |

175

| FIT HEADER |

176

| +-------------------+ |

177

| | | |

178

| | A53 ATF | |

179

| +-------------------+ |

180

| | | |

181

| | A53 OPTEE | |

182

| +-------------------+ |

183

| | | |

184

| | A53 SPL | |

185

| +-------------------+ |

186

| | | |

187

| | SPL DTB 1...N | |

188

| +-------------------+ |

189

+-----------------------+

190

191

- sysfw.itb

192

+-----------------------+

193

| |

194

| FIT HEADER |

195

| +-------------------+ |

196

| | | |

197

| | sysfw.bin | |

198

| +-------------------+ |

199

| | | |

200

| | board config | |

201

| +-------------------+ |

202

| | | |

203

| | PM config | |

204

| +-------------------+ |

205

| | | |

206

| | RM config | |

207

| +-------------------+ |

208

| | | |

209

| | Secure config | |

210

| +-------------------+ |

211

+-----------------------+

Faiz Abbas

b5d2e29

2019-06-04 17:55:55 -0500

[diff] [blame]

eMMC:

-----

ROM supports booting from eMMC from boot0 partition offset 0x0

216

217

Flashing images to eMMC:

218

219

The following commands can be used to download tiboot3.bin, tispl.bin,

220

u-boot.img, and sysfw.itb from an SD card and write them to the eMMC boot0

221

partition at respective addresses.

222

223

=> mmc dev 0 1

224

=> fatload mmc 1 ${loadaddr} tiboot3.bin

225

=> mmc write ${loadaddr} 0x0 0x400

226

=> fatload mmc 1 ${loadaddr} tispl.bin

227

=> mmc write ${loadaddr} 0x400 0x1000

228

=> fatload mmc 1 ${loadaddr} u-boot.img

229

=> mmc write ${loadaddr} 0x1400 0x2000

230

=> fatload mmc 1 ${loadaddr} sysfw.itb

231

=> mmc write ${loadaddr} 0x3600 0x800

232

233

To give the ROM access to the boot partition, the following commands must be

234

used for the first time:

235

=> mmc partconf 0 1 1 1

236

=> mmc bootbus 0 1 0 0

237

238

To create a software partition for the rootfs, the following command can be

239

used:

240

=> gpt write mmc 0 ${partitions}

eMMC layout:

boot0 partition (8 MB) user partition

245

0x0+----------------------------------+ 0x0+-------------------------+

246

| tiboot3.bin (512 KB) | | |

247

0x400+----------------------------------+ | |

248

| tispl.bin (2 MB) | | |

249

0x1400+----------------------------------+ | rootfs |

250

| u-boot.img (4 MB) | | |

251

0x3400+----------------------------------+ | |

252

| environment (128 KB) | | |

253

0x3500+----------------------------------+ | |

254

| backup environment (128 KB) | | |

255

0x3600+----------------------------------+ | |

256

| sysfw (1 MB) | | |

257

0x3E00+----------------------------------+ +-------------------------+

258

259

Kernel image and DT are expected to be present in the /boot folder of rootfs.

260

To boot kernel from eMMC, use the following commands:

261

=> setenv mmcdev 0

262

=> setenv bootpart 0

263

=> boot

Andreas Dannenberg

bc74163

2019-08-15 15:55:32 -0500

[diff] [blame]

264

Vignesh Raghavendra

29ab5d3

2020-02-04 11:09:57 +0530

[diff] [blame]

265

OSPI:

266

-----

267

ROM supports booting from OSPI from offset 0x0.

268

269

Flashing images to OSPI:

270

271

Below commands can be used to download tiboot3.bin, tispl.bin, u-boot.img,

272

and sysfw.itb over tftp and then flash those to OSPI at their respective

addresses.

=> sf probe

=> tftp ${loadaddr} tiboot3.bin

277

=> sf update $loadaddr 0x0 $filesize

278

=> tftp ${loadaddr} tispl.bin

279

=> sf update $loadaddr 0x80000 $filesize

280

=> tftp ${loadaddr} u-boot.img

281

=> sf update $loadaddr 0x280000 $filesize

282

=> tftp ${loadaddr} sysfw.itb

283

=> sf update $loadaddr 0x6C0000 $filesize

284

285

Flash layout for OSPI:

286

287

0x0 +----------------------------+

288

| ospi.tiboot3(512K) |

289

| |

290

0x80000 +----------------------------+

291

| ospi.tispl(2M) |

292

| |

293

0x280000 +----------------------------+

294

| ospi.u-boot(4M) |

295

| |

296

0x680000 +----------------------------+

297

| ospi.env(128K) |

298

| |

299

0x6A0000 +----------------------------+

300

| ospi.env.backup (128K) |

301

| |

302

0x6C0000 +----------------------------+

303

| ospi.sysfw(1M) |

304

| |

305

0x7C0000 +----------------------------+

306

| padding (256k) |

307

0x800000 +----------------------------+

308

| ospi.rootfs(UBIFS) |

309

| |

310

+----------------------------+

311

312

Kernel Image and DT are expected to be present in the /boot folder of UBIFS

313

ospi.rootfs just like in SD card case. U-Boot looks for UBI volume named

314

"rootfs" for rootfs.

315

316

To boot kernel from OSPI, at the U-Boot prompt:

=> setenv boot ubi

=> boot

Andreas Dannenberg

2019-08-15 15:55:32 -0500

[diff] [blame]

320

UART:

321

-----

322

ROM supports booting from MCU_UART0 via X-Modem protocol. The entire UART-based

323

boot process up to U-Boot (proper) prompt goes through different stages and uses

324

different UART peripherals as follows:

325

326

WHO | Loading WHAT | HW Module | Protocol

327

----------+---------------+-------------+------------

328

Boot ROM | tiboot3.bin | MCU_UART0 | X-Modem(*)

329

R5 SPL | sysfw.itb | MCU_UART0 | Y-Modem(*)

330

R5 SPL | tispl.bin | MAIN_UART0 | Y-Modem

331

A53 SPL | u-boot.img | MAIN_UART0 | Y-Modem

332

333

(*) Note that in addition to X/Y-Modem related protocol timeouts the DMSC

334

watchdog timeout of 3min (typ.) needs to be observed until System Firmware

335

is fully loaded (from sysfw.itb) and started.

336

337

Example bash script sequence for running on a Linux host PC feeding all boot

338

artifacts needed to the device:

339

340

MCU_DEV=/dev/ttyUSB1

341

MAIN_DEV=/dev/ttyUSB0

342

343

stty -F $MCU_DEV 115200 cs8 -cstopb -parenb

344

stty -F $MAIN_DEV 115200 cs8 -cstopb -parenb

345

346

sb --xmodem tiboot3.bin > $MCU_DEV < $MCU_DEV

347

sb --ymodem sysfw.itb > $MCU_DEV < $MCU_DEV

348

sb --ymodem tispl.bin > $MAIN_DEV < $MAIN_DEV

349

sleep 1

350

sb --xmodem u-boot.img > $MAIN_DEV < $MAIN_DEV