ABOUT

-----
OMAPFlash is a console based program that supports the transfer of a binary imag
e from a host PC to an OMAP based target platform.
See the OMAPFlash user guide for details on how to use OMAPFlash
HISTORY
-------
Legend: * = fixed in later version
Version 4.10
New features
Functionally equivalent to v4.9. Introduction of calls to new signing to
ol for HS/EMU second loader
binaries.
Fixed issues
New known issues
Old known issues
See 4.9
Version 4.9
New features
Functionally equivalent to v4.8. Corrects a problem in the omapflash2nd.
txt file that causes
problems for correct download to OMAP4430 ES2.2 GP based sEVM.
Fixed issues
New known issues
Old known issues
See 4.8
Version 4.8
New features
Interrim support for OMAP4430 ES2.2 EMU/HS. This release is functionally
equivalent to v4.7.
Fixed issues
New known issues
Old known issues
See 4.7
Version 4.7
New features
Addition of 256 Mb SDRAM support on OMAP3 based platforms.
Fixed issues
New known issues
Old known issues
See 4.6
Version 4.6
New features
Support for multiblock write access to eMMC devices in the eMMC driver.
Fixed issues
Failure to allow access to com port above COM32. Now allows com po
rts from 1-64.
New known issues
Old known issues
See 4.5
Version 4.5
New features
Support for OMAP4430 ES2.0. Addition of raw binaries for EMU/HS devices.
Fixed issues
-
New known issues
Old known issues
See 4.4
version 4.4
New features
-
Fixed issues
Removed modifications to the clock control registers for OMAP3 based pla
tforms when executing 'branch' and 'jump' commands
in order to prevent issues after SDRAM download of u-boot and branching
to the executable.
New known issues
Old known issues
See 4.3
version 4.3
New features
Additional parametrization of the OneNAND driver in order to make it mor
e flexible. The driver can now accept a number
of parameters from the board configuration file that will allow the user
to specify the size parameters for a previously
unknown compatible device. Driver remains 16-bit only.
Fixed issues
-
New known issues
Old known issues
See 4.2
version 4.2
New features
Addition of second loader builds and binaries for OMAP3 based platforms
with 1 Gb and 512 Mb SDRAM sizes.
Fixed issues
-
New known issues
Old known issues
See 4.1
version 4.1
New features
Addition of board configuration file for Zoom2 using OMAP3430. Update of
EVM37xx configuration to 200 MHz L3 clock and
1 GHz CPU.
Fixed issues
-
New known issues
Old known issues
See 4.0
version 4.0
New features
Board and OMAP configurations no longer embedded in the second loader. A
ll such configurations are applied through text
based configuration files used by the host.
Board configuration files added for SDP3630 4Gb/8Gb, Zoom3 4Gb/8Gb, SDP4
430/Blaze 4Gb and EVM37xx
Source code release available
Fixed issues
Peek/PeekPoke return values not displayed to user.
New known issues
Old known issues
See 3.4
version 3.4
New features
8G hynix support for 3630SDP and ZOOM3
Fixed issues
added Zoom3 emu
fixed OMAP4 emmc not working properly when OMAPFlash running on certain
machines
New known issues
downloading to emmc over uart on omap4 broken
Old known issues
See 3.3
version 3.3
New features
Some error messages improved
Fixed issues
default UART configuration fixed
timeout crossing midnight did not occur
Zoom3 now supported e.g. OMAPFlash.exe -omap3 -t 600 -p ZOOM3_MDDR_HYNIX
_4G -2 chip_download nand test_data\pattern_1K.bin
New known issues
Zoom3 emu missing
OMAP4 emmc not working properly when OMAPFlash running on certain machin
es
downloading to emmc over uart on omap4 broken
Old known issues
See 3.2
version 3.2
New features
Some error messages improved
Fixed issues
AsicId now only printed in verbose mode (use -v)
chip_upload SDRAM now supported
Zoom3 now supported e.g. OMAPFlash.exe -omap3 -t 600 -p ZOOM3_MDDR_HYNIX
_4G -2 chip_download nand test_data\pattern_1K.bin
New known issues
*default UART configuration broken use option -parity EVENPARITY
*error handling in zoom3 did not work
Old known issues
See 3.1
version 3.1
New features
Fixed issues
Speed of download improved
2.6MByte/s for 10MByte to SDRAM on OMAP4 (*5 improvement)
3.5MByte/s for 10MByte to SDRAM on OMAP3630
96Byte/s for 10MByte to EMMC on OMAP4 (20% improvement)
Other changes
Debug led pattern changed
New known issues
EMMC should be faster
Error "load_file: could not open 'omapflash2nd.txt'" should be fatal
OMAPFlash should try to locate omapflash2nd.txt in exe dir unless e.g. -
config specify otherwise use -config . to obtain old behaviour
Old known issues
See 3.0
version 3.0
New features
Merged 3630 and 4430 support
Added command extern_power_on, extern_power_off and extern_reset to run
external an application that control power and reset of target when needed by th
e peripheral boot (for test automation)
Added small command line application that can control ONTRAK ADU200 rela
y box
Exit code set on communication failure (1: command line error, 2: periph
eral boot error, 3: post boot error)
Fixed issues
Trace of 'eMMC CID PNM' was incorrect
Connecting to downloaded 2nd though USB when dip switch selection includ
ed both USB and UART did not work
Moved sample files to SampleScripts\3630 or SampleScripts\4430 directory
depending on content
New known issues
Erase of complete eMMC by specifying size of zero is not implemented
Giving a non hexdigit size argument to chip_erase is interpretted as 0 i
.e. erase all (should give error message)
When connecting to omap4 over uart proper default values should be used
for boot package size and delay (must currently be specified manual as: -boot_pa
ckage_delay 500 -max_boot_package_size 1024)
*EMMC init error message is sometimes missing (print NULL, if deinit was
called as part of cleanup)
Connecting through UART to 2nd running out of emmc do not work
Missing small command line application that can control SDP mother board
OMAPFlash should have timeout for waiting for power off/on
No OMAP3430 support
EMMC not supported for OMAP3630
Old known issues
See 2.8
version 2.8
Fixed issues
All versions now support 512MB (GP, GP-CH, HS/EMU)
Heap moved to end of 512MB boundary i.e. 0x9FE50000 to 0x9FFFFFFF not av
ailable for ram download
New known issues
winusb.dll missing on some machines use OMAPFlashInstaller-2.7a-winusb p
atch to work around this problem (you dont have to do this for every time though
)
*Error in range check on available ram for download only 0x80000000 to 0
x8FFFFFFF accepted
Old known issues
See 2.7

version 2.7
Fixed issues
emmc_drv.bin now working
Readme instruction updated
New known issues
winusb.dll missing on some machines use OMAPFlashInstaller-2.7a-winusb p
atch to work around this problem
*Missing possibility to dump AsicId (needed for signing HS)
UART disabled for HS/EMU version
CH only supported for GP i.e. only 256MB support for HS/EMU
Old known issues
See 2.6
version 2.6
Fixed issues
emmc_drv.bin was missing
Readme instruction updated
Comments in uboot_emmc.txt and uboot_ram.txt updated
Heap moved to end of 256MB boundary i.e. 0x8FE50000 to 0x8FFFFFF
F not available for ram download
New known issues
*512MB RAM configuration only supported through CH and same heap
as for 256MB
*release emmc_drv.bin not compatible with 2.6
Old known issues
See 2.5
version 2.5
Fixed issues
Readme and various options files (*.txt) corrected with respec t
o minor errors
eMMC erase now handle multiple 512KByte groups correctly
New known issues
*CH version not included
*only 256MByte SDRAM configured (0x80000000 to 0x8FFFFFFF)
*Heap not located at end of RAM i.e. 0x87E50000 to 0x87FFFFFF no
t available for ram download
*emmc_drv.bin missing
Old known issues
*Upload may fail if file already exists (testcase usb_emmc_doubl
e_upload.bat)
eMMC listed as 2GByte but is in reality 32GByte (for 4430 wakeup
board) (area above 2GB not accessible through OMAPFlash)
eMMC image size above 512MByte not tested
no -rxtx_trace for fastboot mode
*No OMAP3XXX support (and installer do not support multiple vers
ion)
Cannot poke value 0xFFFFFFFF
MMC/SD cage not validated
OMAPFlash version should be listed by drivers
Installer fails to install AdbWinApi.DLL (see INTALL section for
proper action)
version 2.4
Fixed issues
eMMC write now work properly
command enable_trace 5 works properly see trace.txt (except if t
racing of comunication is enabled at compile time)
Above instructions corrected
New known issues
Upload may fail if file already exists (testcase usb_emmc_double
_upload.bat)
eMMC listed as 2GByte but is in reality 32GByte (area above 2GB
not accessible through OMAPFlash)
eMMC image size above 512MByte not tested
*eMMC erase will fail if more than one 512KByte group is to be e
rased
no -rxtx_trace for fastboot mode
Old known issues
No OMAP3XXX support (and installer do not support multiple versi
on)
Cannot poke value 0xFFFFFFFF
MMC/SD cage not validated
OMAPFlash version should be listed by drivers
version 2.3
Added
eMMC
Target commands for U-Boot support:
HAL_CM_EnableModuleClocks <module> <instance>
HAL_CTRL_ConfigurePads <module> <instance>
Debug commands
PEEK32 <address>
POKE32 <address> <value>
Known issue
Cannot poke value 0xFFFFFFFF
MMC/SD cage not validated
*only first 1024 bytes written correctly to eMMC
*only first 1024 bytes erased correctly in eMMC
*no progress information for eMMC erase
erase of big areas in eMMC uneccesary slow
command enable_trace 5 hangs
when using usb initial check for power-on may fail (missing requ
est for power-off)
eMMC CSD and Extended CSD registers assumed unchanged (erase gro
upsize assumed 512KB)
non-whole erase groups are over written not erased
version 2.2
Fixed issues
Fixed speed issue concerning USB download now 0.5 MByte / Second
version 2.1
Not released
version 2.0
Initial version supporting OMAP4
Known issue
*DDR wirte only
*No Flash support
*No OMAP3XXX support
*USB download slow (0.1 MByte / Second)