Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Tools to boot omap44xx over USB.
branch: master

OMAP4: Remove dummy writes to SDRC

Remove dummy writes to the SDRC they are causing
4460 panda to lock up.  If a specific board needs
them then they should be added back into the board init.

Signed-off-by: Dan Murphy <dmurphy@ti.com>
latest commit b6c9981131
Dan Murphy murpdj72 authored Brian Swetland committed
Failed to load latest commit information.
arch OMAP4: Remove dummy writes to SDRC
build tidy up the build system a bunch
include omap4: MA_BASE register definition
libc build system overhaul
tools usbboot: cleanup, print ASIC ID
.gitignore build system overhaul
Makefile aboot: verification of third stage
README
aboot.c aboot: verification of third stage
aboot.lds omap4: relocator support to deal with differences in GP/HS/EMU
agent.c more build system cleanup
board_blaze.c OMAP4: blaze: Add change to program the MA for 4460
board_panda.c OMAP4: panda: Add change to program the MA for 4460
board_tuna.c tuna: move board-specific writes out of sdram.c
boot.c more build system cleanup
config_blaze.h tuna: switched from UART4 to UART3, remove dead code
config_panda.h tuna: switched from UART4 to UART3, remove dead code
config_tuna.h tuna: switched from UART4 to UART3, remove dead code
misc.c cleanup and board files
trusted.S aboot: verification of third stage

README

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

Something went wrong with that request. Please try again.