This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM365 TFTP boot problem

Hi,

i have already found other posts that expose a similar problem but no one can't guide me to a solution

When i boot kernel by TFTP, the process stop at "Starting kernel ..."
I obtain the same result with the provided uImage_ipnc_dm365_1.5.0 or my recompiled version

Can someone give me some suggestions?

Thanks


boot output

U-Boot 1.3.4 (Aug  5 2009 - 18:21:12) DM365-IPNC-0.6

I2C:   ready
DRAM:  128 MB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit)
Bad block table found at page 65504, version 0x00
Bad block table found at page 65472, version 0x00
32 MiB
In:    serial
Out:   serial
Err:   serial
ARM Clock :- 297MHz
DDR Clock :- 270MHz
Ethernet PHY: GENERIC @ 0x01
Hit any key to stop autoboot:  8  7  6  5  4  3  2  1  0
TFTP from server 10.0.0.1; our IP address is 10.0.0.2
Filename 'uImage'.
Load address: 0x80700000
Loading: *#################################################################
     ##########################################################
done
Bytes transferred = 1803272 (1b8408 hex)
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.18_pro500-davinci_IPNC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1803208 Bytes =  1.7 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

my printenv output:

baudrate=115200
bootfile="uImage"
bootdelay=8
ethaddr=00:0C:0C:A0:03:64
rootpath=/home/user/workdir/filesys
nfshost=10.0.0.1
filesize=BDC000
fileaddr=82000000
ipaddr=10.0.0.2
serverip=10.0.0.1
bootcmd=tftpboot 0x80700000 uImage; bootm 0x80700000
bootargs=console=ttyS0,115200n8 noinitrd rw ip=$(ipaddr) root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=80M video=davincifb:vid0=0FF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=4
setboot=bootargs $(bootargs) video=dm36x:output=$(videostd)
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.3.4 (Aug  5 2009 - 18:21:12) DM365-IPNC-0.6

  • This typically means your uImage is broken. As you tried diferent kernel images with same result, your u-boot could be broken. Try reinstalling ist.

  • I have just tried to reinstall u-boot but probably i have done something wrong!
    ... after power reset nothing compare in HyperTerminal and the ethernet led doesn't light anymore

    What could have happened? May i have corrupted the NAND?
    W
    hat can i do now?

    Regards

  • how did you reinstall u-boot? using u-boot?

     

    it there is nothing on RS232, then have probably dammaged ubl.

  • I have loaded u-boot-1.3.4_ipnc_dm36x_0.6.0.bin by TFTP
    but probably i have typed a wrong address when i have written u-boot on NAND

    What can i do now? Do i have to use CCS to restore ubl?
    I don't have this software, can i download it for free?

    Regards

  • no you dont need CCS. you can restroe ubl and u-boot using TI serial boot and flash loading utility. follow this link for more information. http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility

     

    another tool you could think about ist Ronetix PEEDI

    http://www.ronetix.at/

    it costs about 1100€ as a flash programmer. It´s not easy to configure, but its a great tool and Ronetix has a great support. I bought it because i will use it for production, but even for development it is great.

  • Hi Josef,
    thanks for your help

    i have read "Serial Boot and Flash Loading Utility" documentation but i am confused. In the section "Flashing DM365 EVM using Serial flash utilities" refer to a switch SW4 configuration. There isn't any switch in my jtag debug board. Am i ignoring something?

    Best Regards

  • sw4 is the switch on the evm from spectrum digital. look at the schematics of your debug board, you can get them from appro. there you will find the settings for uart boot. i do not know whitch switch it is, i only have dm355ipnc.

  • There is only in the EVM board but i haven't it.
    I have got DM365IPNC-MT5 and i think i can't use this way to restore ubl

  • Hi,
    i have searched around documentations and web to find all the way to restore ubl on my DM365IPNC-MT5.

    I concluded that there aren't other ways than use Code Composer Studio and a XDS 510 USB emulator or XDS 560 emulator like is described on User_Guide_IPNC_DM365 document.

    Am i going wrong?
    I am not yet very practical and I do not know what to do ...

    Can i use serial flash utilities with a JTAG emulator or i can use them only with EVM board?

    Is "SD card boot" a practical way in my case?
    http://processors.wiki.ti.com/index.php/SD_card_boot_and_flashing_tool_for_DM355_and_DM365


    Best regards

  • Dear ADC, I hate to bring you the bad news. But here goes: The boot select DIP switches are not present in the IPNC hardware. They are hardwired to a few presets which you can see from the schematics of the device. I can't find a way to boot from UART there. If you can open up the camera and play with possible the jumpers and DIP switches (with the help of schematics), and you see BOOTME messages on your serial console, you can boot and flash via serial. There is a good help page on how to do that in the wiki. Else.... read on.. What you can do is write/flash UBL and U-BOOT using CCS and JTAG. XDS100v2 costs you 70$. CCS is free if you use it only with XDS100v2. But do heck with the vendor if this can be used for DM365IPNC before purchasing. Good luck! best regards, NR
  • Dear ADC,

    One possible approach is to use SD boot mode. There is DIP switch for selecting SD boot mode. But the problem is that IPNC Ref Design, by default does not have SD boot code provided in software package. You would have to modify the currently available solution for SD boot and NAND flashing for EVM. One change that is needed in SD UBL would be to use UART1 instead of UART0 because UART1 is used as the serial terminal port on IPNC.

    Details can be available at http://processors.wiki.ti.com/index.php/SD_card_boot_and_flashing_tool_for_DM355_and_DM365

     

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.