• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 100 subscribers
  • Views 1130 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

IPNCv5.1.0 Appro DMVA2 boot hangup random

Charvi Mehta
Intellectual 450 points
Other Parts Discussed in Thread: TMS320DM368, TMS320DM365

Hi,

We are using IPNC DMVA2 kit and IPNCv5.1.0 RDK.

We are experiencing some random behavior in boot up. Few times the board boots properly. The rest of the times it so happens that we get no prints on the console at all or we get the following prints :

TI UBL Base Version: 1.50
Boot Loader BootMode = NAND
Starting NAND Copy...

And then it hangs. A very few times board also hangs while after the kernel is up. But basically seems some issue with NAND/DDR. As a few times we do get the prints and everything works fine we have rules out issue with serial. Does anybody have any idea as to why this happens.

Also we need some inputs on changing the boot mode from NAND to SD card and booting from SD card.

Thanks,

Charvi.

  • 0
    TI__Genius 11000 points

    Hello,

    Can you try with these binaries and check if the issue still persists?

    Regards,

    Raghu2437.Desktop.zip

  • 0 in reply to Raghu Kudva
    Intellectual 450 points

    Hi Raghu,

    First of all thanks for your prompt response.

    We used the ubl_432arm_340ddr_ipnc_dm368.bin from the package you provided above. For a while it worked fine. We got the print IPNC UBL VERSION 2.1.0. But after some time it hanged at Starting Kernel.... Then prints stopped coming altogether for twice and then the famous NAND boot failed prints as mentioned above. We notice that while we get the following prints :

    TI UBL Base Version: 1.50
    Boot Loader BootMode = NAND
    Starting NAND Copy...

    The UBL version again becomes 1.50. Is this some kind of rescue copy in some other block which is accessed when the original copy fails ?

    Thanks,

    Charvi

  • 0 in reply to Charvi Mehta
    Intellectual 450 points

    Hi Raghu,

    As we are having getting board up problem we are trying to connect it to CCS for two things : we can reflash the UBL and UBOOT afetr a nand scrub and we can also run the diagnostic utility provided in the package at <rdk_base_installation_directory>/Binaries/dmva2/diagnostic_ipnc_dm368.bin. We need your support for two things :

    1) We are trying to follow the User Guide for the steps to flash the ubl, uboot through CCS but we are not able to get the target connected message (this is in CCSv4.2.3). In CCSv5.0 we are not getting XDS510 emulator option while creating the Target Configuration File.

    2) We know how to flash the diagnostic through CCS, please guide on how to run the diagnostic.

    We appreciate your help.

    Thanks and Regards,

    Charvi

  • 0 in reply to Charvi Mehta
    TI__Expert 7225 points

    Hi Charvi,

    Have you tried the Nand boot option after reflashing the board (non-ccs way)? 

    One option is if you can use the latest CCS5.4 or so. I also think CCS 5.1 will have the XDS510 option as it is very popular an emulator...May be you can paste the snapshot of the ccs pageview for target config.

    Raghu can provide more inputs here I believe....

    Best Regards

    Feroz

  • 0 in reply to K Md Feroz Irfan
    Intellectual 340 points

    Right now we dont see any messages on the Serail prompt upon startup. At times some messages come .. but they stop with some NAND boot failed message.

    Added image of target config window with CCS 5.0 .. there is no option for XDS510 emulator and no option for DM368 target.

     

  • 0 in reply to Snehal Parmar1
    TI__Expert 7225 points

    Hi Snehal,

     I cannot see the string you entered on the baord or device box.

    What is string you entered? DM368 has 2 options EVMDM368 or TMS320DM368. I see both of them on my PC with CCS 5.2....I suppose you have chosen XDS510USB as the connection???

    Please confirm...

    We will download and share the CCS 5.5 over ftp ...

    Best REgards

    Feroz

    For latest CCS

  • 0 in reply to K Md Feroz Irfan
    Intellectual 450 points

    Hi Feroz,

    According to what I understand from Snehal he isn't getting the XDS510 USB Emulator option in the connection drop down list at all.We don't know why this would happen.

    Thanks for helping to download the CCSv5.5. Do share the location and credentials once you're done.

    I have got the connection with the target working with the CCSv4.2.3. I am able to compile the NANDWriter project successfully (provided in the rdk in flash_utils_dm36x). However when I run the NANDWriter project I do not get any prints on the console to enter any file for flashing etc. The program just shows thread running and hangs ...

    Following are the snaps :

    Following shows the gel file :

    Following is the snap which shows that the program is running but i don't get any other activity :

    The  file is as shown :

    ; Code Composer Project File, Version 2.0 (do not modify or remove this line)

    [Project Settings]
    ProjectDir="C:\Program Files\Texas Instruments\IPNCProjects\flash_utils_dm36x\DM36x\CCS\NANDWriter\"
    ProjectType=Executable
    CPUFamily=TMS470R2X
    Tool="Compiler"
    Tool="CustomBuilder"
    Tool="Linker"
    Config="Release"

    [Source Files]
    Source="..\..\..\Common\ccs\src\debug.c"
    Source="..\..\..\Common\drivers\src\nand.c"
    Source="..\..\..\Common\src\util.c"
    Source="..\..\Common\src\device.c"
    Source="..\..\Common\src\device_nand.c"
    Source="src\nandwriter.c"
    Source="NANDWriter.cmd"

    ["Compiler" Settings: "Release"]
    Options=-o3 -fr"$(Proj_dir)\Release" -i"$(Proj_dir)\include" -i"$(Proj_dir)\..\..\..\Common\ccs\include" -i"$(Proj_dir)\..\..\Common\include" -i"$(Proj_dir)\..\..\..\Common\include" -i"$(Proj_dir)\..\..\..\Common\drivers\include" -d"SKIP_LOW_LEVEL_INIT" -d"IPNC_DM368" -me -mv5e --abi=eabi

    ["Linker" Settings: "Release"]
    Options=-c -m".\nandwriter_ipnc_dm368.map" -o".\nandwriter_ipnc_dm368.out" -w -x

    Or is it due to not getting some runtime pritf library or something ?

    Thanks and Regards,

    Charvi

  • 0 in reply to Charvi Mehta
    Intellectual 450 points

    Hi Feroz,

    Thanks for the ftp credentials. While we are downloading the CCSv5.5 I had the following query for my build as mentioned above.

    When we check the NANDWriter_IPNC368's Build Properties we get the following :

    Here as highlighted in the Device variant field it takes unknown TMS470R2X device. There is no option for TMS320DM365/TMS320DM368. I am able to compile the project but when I connect the target I am not getting any prints, not even from then gel file !

    The device is mentioned in the .pjt file as follows :

    [Project Settings]
    ProjectDir="C:\Program Files\Texas Instruments\IPNCProjects\flash_utils_dm36x\DM36x\CCS\NANDWriter\"
    ProjectType=Executable
    CPUFamily=TMS470R2X
    Tool="Compiler"
    Tool="CustomBuilder"
    Tool="Linker"
    Config="Release"

    [Source Files]
    Source="..\..\..\Common\ccs\src\debug.c"
    Source="..\..\..\Common\drivers\src\nand.c"
    Source="..\..\..\Common\src\util.c"
    Source="..\..\Common\src\device.c"
    Source="..\..\Common\src\device_nand.c"
    Source="src\nandwriter.c"
    Source="NANDWriter.cmd"

    ["Compiler" Settings: "Release"]
    Options=-o3 -fr"$(Proj_dir)\Release" -i"$(Proj_dir)\include" -i"$(Proj_dir)\..\..\..\Common\ccs\include" -i"$(Proj_dir)\..\..\Common\include" -i"$(Proj_dir)\..\..\..\Common\include" -i"$(Proj_dir)\..\..\..\Common\drivers\include" -d"SKIP_LOW_LEVEL_INIT" -d"IPNC_DM368" -me -mv5e --abi=eabi

    ["Linker" Settings: "Release"]
    Options=-c -m".\nandwriter_ipnc_dm368.map" -o".\nandwriter_ipnc_dm368.out" -w -x

    Please give some pointers. As I am completely stuck here.

    Thanks,

    Charvi.

  • 0 in reply to Charvi Mehta
    Intellectual 450 points

    Also when I try to load the nandwriter.out via Target -> Load Program after I connect the target I get the following error 

    I searched the forum and may be this error comes because my DDR is not initialized. This may be because my gel files isn't executed properly as I don't get any prints from the gel file. I have mentioned the gel file gel_ ipnc_dm36x_1.0.0.gel in the Advanced option in the Target Configuration. Please help.

    Thanks and Regards,

    Charvi.