GitHub - showliu/omap4boot: Tools to boot omap44xx over USB.

This branch is 1 commit ahead of swetland/omap4boot:master.

Name	Name	Last commit message	Last commit date
Latest commit Show Liu Fixed for gcc 4.9 Jan 19, 2015 1f4ba2b · Jan 19, 2015 History 47 Commits
arch	arch	OMAP4: Remove dummy writes to SDRC	Sep 27, 2011
build	build	tidy up the build system a bunch	Apr 25, 2011
include	include	omap4: MA_BASE register definition	Sep 1, 2011
libc	libc	build system overhaul	Dec 19, 2010
tools	tools	usbboot: cleanup, print ASIC ID	Sep 22, 2011
.gitignore	.gitignore	build system overhaul	Dec 19, 2010
Makefile	Makefile	Fixed for gcc 4.9	Jan 19, 2015
README	README	add some minimal documentation	Dec 19, 2010
aboot.c	aboot.c	aboot: verification of third stage	Sep 22, 2011
aboot.lds	aboot.lds	omap4: relocator support to deal with differences in GP/HS/EMU	Apr 13, 2011
agent.c	agent.c	more build system cleanup	Apr 25, 2011
board_blaze.c	board_blaze.c	OMAP4: blaze: Add change to program the MA for 4460	Sep 27, 2011
board_panda.c	board_panda.c	OMAP4: panda: Add change to program the MA for 4460	Sep 27, 2011
board_tuna.c	board_tuna.c	tuna: move board-specific writes out of sdram.c	Sep 27, 2011
boot.c	boot.c	more build system cleanup	Apr 25, 2011
config_blaze.h	config_blaze.h	add omap4 blaze board support	May 23, 2011
config_panda.h	config_panda.h	more build system cleanup	Apr 25, 2011
config_tuna.h	config_tuna.h	tuna: switched from UART4 to UART3, remove dead code	Aug 5, 2011
misc.c	misc.c	cleanup and board files	Apr 14, 2011
trusted.S	trusted.S	Fixed for gcc 4.9	Jan 19, 2015

Repository files navigation

USB downloader and USB second stage bootloader for OMAP44xx
===========================================================

aboot.bin
---------

aboot.bin is a designed to be a second stage USB bootloader (what TI
calls x-loader) for the USB peripheral boot mode of OMAP44xx.

Currently it's somewhat pandaboard-centric, but that should be
easy enough to clean up -- it shouldn't touch any gpiomux config
except (maybe) for the UART.

All it does is send a u32 message (0xaabbccdd) back over the USB link, 
then reads a u32 size from the host.  Then it downloads size bytes
from the host to 0x82000000 and jumps to that address.


usbboot
-------

usage: usbboot <2ndstage> [ <image> ]

- usbboot will poll every 250ms until it locates an OMAP device 
  (VID 0451, PID d00f)
- it then will send the 2ndstage binary to the device 
- if an image was also provided, it will wait for the 2ndstage to
  send the go-ahead response (0xaabbccdd) and then send that image