I successfully flashed dm365 board. Rebooted in nand mode and console is stuck for ever
Output when flashing
SD card boot and flashing tool for DM355 and DM365by Constantine Shulyupin http://www.LinuxDriver.co.il/Online manual: http://wiki.davincidsp.com/index.php/SD_card_boot_and_flashing_t5based on TI DM35x FlashAndBootUtils 1.10 SFT, TI flash_utils and SpectrumDigita5Compiled on Jul 2 2011 at 00:55:31 with gcc 4.2.4SYSTEM->DEVICE_ID=0x8B83E02F&EMIFStart=0x02000000nand->devID=0x000000DA nand->dataBytesPerPage=2048 nand->pagesPerBlock=64 nand-6sdcard_initsdcard_read sdc_src=0x00001000 dst=0x80001044 len=0x00000200 dst + len=0x800012 flasher_data=0x000A1C00 sdcard_read sdc_src=0x000A9C00 dst=0x80001044 len=0x00000200 dst + len=0x800012 check_pattern_123 Erasing block 0x00000001 through 0x000007FB.sdcard_install * Flashing UBLsdcard_read sdc_src=0x000B1C00 dst=0x80001248 len=0x00007800 dst + len=0x80008A Writing header data to Block 00000001, Offset 00020000 * Flashing u-boot sdcard_read sdc_src=0x000C1C00 dst=0x81080000 len=0x00028000 dst + len=0x810A80 Assuming GNU UBL UBL_GNU_ENTRY=0x00000100Writing header data to Block 00000019, Offset 00320000 * Flashing kernel sdcard_read sdc_src=0x00101C00 dst=0x80700000 len=0x00300000 dst + len=0x80A000 nand_write dst_nand=0x00400000 block_idx=0x00000020 len=0x00300000 * Flashing Root FS sdcard_read sdc_src=0x004A1C00 dst=0x82000000 len=0x00800000 dst + len=0x828000 nand_write dst_nand=0x00600000 block_idx=0x00000030 len=0x00800000 1 - boot; 2 - install; 3 - erase flash, 4 - nand boot, 5 - test first 16MB of RMu - install ubl only, d - nand flash dump
Powered off at this point, set it to nand mode. Powered on
> DM36x initialization passed! TI UBL Version: 1.50 Booting Catalog Boot Loader BootMode = NAND Starting NAND Copy... Valid magicnum, 0xA1ACED66, found in block 0x00000019. DONE Jumping to entry point at 0x81080000. DM36x initialization passed! TI UBL Version: 1.50 Booting Catalog Boot Loader BootMode = NAND Starting NAND Copy... Valid magicnum, 0xA1ACED66, found in block 0x00000019. DONE Jumping to entry point at 0x81080000.
STUCK AT THIS POINT
used the following image www.ridgerun.com/.../Leo365Eval2011Q2_JFFS2.zip and was able to successfully flashed.
Hi,
I can see that your not using RidgeRun's SDK, RidgeRun's SDK have the ability to create SD card images, so you will be able to create an SD with bootloader, kernel and/or file system.
Also you can download a precompiled image with bootloader, kernel, file system and test RidgeRun's SDK. If you want to try it, I suggest you to download Leo365Eval2011Q2_SD.zip from "www.ridgerun.com/downloadinfo.shtml. This image will not change your NAND data and the Leopard will need to boot from SD (bootselect switch should be configured for this).
Regards.
Carlos AgueroEmbedded Software EngineerRidgeRun
I am following the steps https://www.ridgerun.com/developer/wiki/index.php/DM365_Leopard_SDK_2011Q2_Getting_Started_Guide
I get this error when trying to create a sd boot recover disk
devendra@enemy-needle:~/LeopardBoardDM365sdkEVAL2011Q2$ make sd_boot_recover device=/dev/mmcblk0echo -e "\040" "\033[30mBuilding \033[0m" Building make: *** /home/devendra/LeopardBoardDM365sdkEVAL2011Q2/bsp/mach/dm3xx_sd_boot-6_leopard/: No such file or directory. Stop.make: *** [sd_boot_recover] Error 2
About the sd_boot_recover function, it's going to be removed from the Eval SDK 2011Q2, sd_boot_recover function shouldn't be at the getting started guide.
In order to use and create an SD with RidgeRun's SDK follow this guide:
www.ridgerun.com/.../RidgeRun_2011Q2_SDK_User_Guide