Hi !
I did wanted to test dvsdk v4.01 on the EVM platform.
Infortunately I flash u-boot and it does not start on platform reset.
I tried to reflash it through flash utility v1.6.
Things get worst when by mustake I erase X-Loader.
Here are the steps I followed :
Fisrt I modified omapflash2nd.txt for nand recognition : CUSTOM_OMAP35XX_BOARD 343007 57 => CUSTOM_OMAP35XX_BOARD 343007 54
Then I modified configuration_evm35xx_micron_512m.txt because its nand address was 0x28000000, and conforming to hardware user guide the nand was at 0x20000000.
I recomplied X-Loader and signed it to get the ift file.
Now I launch the flash utility with config=OMAP35x, ECC Style=HWECC, file = x-load.bin.ift.
At startup the XLoader does not boot .
Worst If I relaunch the flash tool just to erase the x-loader region I get stuck in the middle of the process :
¯ -stdout
¯ -omap 3
¯ -no_force_package_alignment
¯ -com 1
¯ -t 60
¯ -p EVM_MDDR_MICRON_512M
¯ -2
¯ chip_erase NANDINFO1BITBOOT 00080000
¯ Leaving parameter file:temp_script.txt
¯ @temp_script.txt
¯ Looking for device (omap com1)
¯ Please turn off device, then turn it on again
¯ Awaiting ASIC id
¯ Awaiting ASIC id
¯ AsicId items 04
¯ AsicId id 01 05 01 34 30 07 54
What can I do know ?
Are my parameters correct ?