Talk:Flash v1.5 User Guide

Comments on Flash v1.5 User Guide -

Twanger said ...
Hi,

I just tried to use this software on XP with the LogicPD AM3517EVM. I first tried to erase 0x80000 bytes at offset 0x0 and this appeared to work. However, any other commands that I tried produce the same results: It appears to erase those same bytes. This is true even if I select and download to SDRAM. USB enumeration, 2nd loader downloading, and driver loading all appear to work. It's as if only knows how to do this one thing.

¯ Looking for device (omap usb) ¯ Please turn off device ¯ Please turn on device ¯ Waiting for device (omap usb) ¯ Found device (omap usb) ¯ Awaiting ASIC id ¯ AsicId items 05 ¯ AsicId id       	01 05  01  34 30 07 58 ¯ AsicId secure_mode	13 02 01  00 ¯ AsicId public_id 	12 15 01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ¯ AsicId root_key_hash	14 15 01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ¯ AsicId checksum 	15 09  01  59 DB 63 8B 00 00 00 00 ¯ Searching 2nd for: EVM_MDDR_MICRON_2G_EMIF 343007 58 GP ¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_2g.2nd ¯ Entering parameter file:omapflash2nd.txt at line: 15 ¯    -pheriphalboot_reopen ¯ Reading board configuration file Targets\Configurations\configuration_am35xxevm_micron_2g.txt ¯ Reading definition file .\targets\definitions\definitions_omap3.txt ¯    -board_config Targets\Configurations\configuration_am35xxevm_micron_2g.txt ¯ Leaving parameter file:omapflash2nd.txt ¯ Sending size of second file (0x00006804 bytes) ¯ Transferring second file to target (0x6804 bytes) ¯ Closing boot connection ¯ Found device (omap usb) ¯ Waiting for 2nd ¯ Found 2nd ¯ Looking for a driver for 'NAND' ¯ chip_driver NAND Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin gpmc 0x6E000000 cs 0 address 0x30000000 bberase 0 ¯ Downloading driver ¯ Downloading 'Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin'

¯ Sending data (40768 bytes) ::::::::::::::::.... [32764] ¯ Sending data (40768 bytes) :::::::::::::::::::: [40768] ¯ Sending data (40768 bytes) :::::::::::::::::::: [40768] Interface 'OMAPFLASH DRIVER v5' Driver 'NAND ONFI 16/8 BIT' Driver configuration: gpmc = 0x6E000000 Driver configuration: cs = 0x00000000 Driver configuration: address = 0x30000000 Driver configuration: bberase = 0x00000000 NAND HW ECC NAND BCH Mode = 0 NAND HWECC offset = 2, size = 12 NAND ONFIv2 VENDOR 0x2C MICRON NAND 16 BIT DEVICE 0xBC MT29F4G16ABBDAH4 NAND NAND CYCLES 0x23 (3 ROW, 2 COLUMN) NAND 2048 BYTES/PAGE (SPARE 64) NAND 64 PAGES/BLOCK (131072 BYTES/BLOCK) NAND 4096 BLOCKS/UNIT (536870912 BYTES/UNIT) NAND 4 BIT(S) ECC REQUIRED NAND 512 MB TOTAL SIZE NAND ONFI DRIVER INIT COMPLETE ¯ Downloading complete ¯ Elapsed time: 0:00.500 (81536 bytes/s) ¯ End loading driver ¯ Erasing Erasing 524288 bytes starting at 0x30000000

Erase progress :::::............... [131072]	 Erase progress ::::::::::.......... [262144]	 Erase progress :::::::::::::::..... [393216]	 Erase progress :::::::::::::::::::: [524288] NAND ERASED 524288 BYTES FROM ADDRESS 0x30000000 (0 BAD BLOCKS) ¯ Elapsed time: 0:00.000

Console program success, exit code: 0 ¯    -stdout ¯    -omap 3 ¯    -t 60 ¯    -p EVM_MDDR_MICRON_2G_EMIF ¯    -2 ¯     chip_erase NAND 80000 ¯ Leaving parameter file:temp_script.txt ¯ @temp_script.txt ¯ Looking for device (omap usb) ¯ Please turn on device ¯ Waiting for device (omap usb) ¯ Found device (omap usb) ¯ Awaiting ASIC id ¯ AsicId items 05 ¯ AsicId id       	01 05  01  34 30 07 58 ¯ AsicId secure_mode	13 02 01  00 ¯ AsicId public_id 	12 15 01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ¯ AsicId root_key_hash	14 15 01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ¯ AsicId checksum 	15 09  01  59 DB 63 8B 00 00 00 00 ¯ Searching 2nd for: EVM_MDDR_MICRON_2G_EMIF 343007 58 GP ¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_2g.2nd ¯ Entering parameter file:omapflash2nd.txt at line: 15 ¯    -pheriphalboot_reopen ¯ Reading board configuration file Targets\Configurations\configuration_am35xxevm_micron_2g.txt ¯ Reading definition file .\targets\definitions\definitions_omap3.txt ¯    -board_config Targets\Configurations\configuration_am35xxevm_micron_2g.txt ¯ Leaving parameter file:omapflash2nd.txt ¯ Sending size of second file (0x00006804 bytes) ¯ Transferring second file to target (0x6804 bytes) ¯ Closing boot connection ¯ Found device (omap usb) ¯ Waiting for 2nd ¯ Found 2nd ¯ Looking for a driver for 'NAND' ¯ chip_driver NAND Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin gpmc 0x6E000000 cs 0 address 0x30000000 bberase 0 ¯ Downloading driver ¯ Downloading 'Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin'

¯ Sending data (40768 bytes) ::::::::::::::::.... [32764] ¯ Sending data (40768 bytes) :::::::::::::::::::: [40768] ¯ Sending data (40768 bytes) :::::::::::::::::::: [40768] Interface 'OMAPFLASH DRIVER v5' Driver 'NAND ONFI 16/8 BIT' Driver configuration: gpmc = 0x6E000000 Driver configuration: cs = 0x00000000 Driver configuration: address = 0x30000000 Driver configuration: bberase = 0x00000000 NAND HW ECC NAND BCH Mode = 0 NAND HWECC offset = 2, size = 12 NAND ONFIv2 VENDOR 0x2C MICRON NAND 16 BIT DEVICE 0xBC MT29F4G16ABBDAH4 NAND NAND CYCLES 0x23 (3 ROW, 2 COLUMN) NAND 2048 BYTES/PAGE (SPARE 64) NAND 64 PAGES/BLOCK (131072 BYTES/BLOCK) NAND 4096 BLOCKS/UNIT (536870912 BYTES/UNIT) NAND 4 BIT(S) ECC REQUIRED NAND 512 MB TOTAL SIZE NAND ONFI DRIVER INIT COMPLETE ¯ Downloading complete ¯ Elapsed time: 0:00.484 (84231 bytes/s) ¯ End loading driver ¯ Erasing Erasing 524288 bytes starting at 0x30000000

Erase progress :::::............... [131072]	 Erase progress ::::::::::.......... [262144]	 Erase progress :::::::::::::::..... [393216]	 Erase progress :::::::::::::::::::: [524288] NAND ERASED 524288 BYTES FROM ADDRESS 0x30000000 (0 BAD BLOCKS) ¯ Elapsed time: 0:00.000

Console program success, exit code: 0

--Twanger 16:10, 17 June 2011 (CDT)

Twanger said ...
This was due to a permissions problem. I ran this program as administrator and then logged off and back on as a user. A temporary script was left behind that contained the last commands.

The software should be improved to remove the file properly or detect that one already exists.

--Twanger 19:03, 17 June 2011 (CDT)