• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 758 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.

Terminal can not display via RS-232 from DM368?

YenHung Chen
Prodigy 250 points
Other Parts Discussed in Thread: OMAP3530

I run a command at uboot:

DM365_WebCam>era 0-127

then, the terminal does not display any message from RS-232?

How can I fix this problem?

I tried to re-install uBoot via CCS4.1.2, but the connection was failed, the error message is:

Warning:
0x40002220/-2062 @ marker 13500
Warning during: Execution, OCS, Control,
Cannot halt the processor

Trouble Reading Register IP_TAP_CNTL_0:
Error 0x80002004/-114
Fatal Error during: Register, Control,

My configuration of NewTargetConfiguration.ccxml is as following:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">

<configuration XML_version="1.2" id="AH XDS510PLUS Emulator_0">
        <instance XML_version="1.2" desc="AH XDS510PLUS Emulator_0" href="connections\AH-XDS510PLUS_Connection.xml" id="AH XDS510PLUS Emulator_0" xml="AH-XDS510PLUS_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="AH XDS510PLUS Emulator_0">
            <instance XML_version="1.2" href="drivers\AHxds510plusicepick_c.xml" id="drivers" xml="AHxds510plusicepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers\AHxds510plusarm9.xml" id="drivers" xml="AHxds510plusarm9.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
              
            <instance XML_version="1.2" desc="EVMDM365_0" href="boards\evmdm365.xml" id="EVMDM365_0" xml="evmdm365.xml" xmlpath="boards"/>
                <board XML_version="1.2" description="Spectrum Digital DM365 EVM Board" id="EVMDM365_0">
                    <router HW_revision="1.0" XML_version="1.2" description="ICEPick_C Router" id="IcePick_C_0" isa="ICEPICK_C">
                        <subpath id="subpath_0">
                            <cpu HW_revision="" XML_version="1.2" description="" id="device_2" isa="ARM9">
                                <property Type="filepathfield" Value="D:\projects\vicommtech.com\ccs4\usbwebcam.gel" id="GEL File"/>
                            </cpu>
                        </subpath>
                    </router>
                </board>
            </platform>
        </connection>
    </configuration>
</configurations>

Thanks!

  • 0
    TI__Genius 9510 points

    Regarding the problem with connecting to the target via CCS, have you at any point been able to connect to the target board.

    Please provide the name and model number of your emulator?

  • 0 in reply to Marcus Cooksey
    Prodigy 250 points

    The emulator that I am using is:

    AH XDS510PLUS

    I have tested to connect Beagle board (OMAP3530), it works.

    The DM368 board is bought from LeopardImaging (EUCDK).

    I try to connect this board by J-Link, there is a similar error message:

    "Cannot halt the processor"

     

  • 0 in reply to YenHung Chen
    TI__Genius 9510 points

    Have you be able to obtain support from Leopard Imaging? They may already have a configuration file to allow connect.

    One issue I've seen is that the JTAG clock can be too high at times.  Reducing the JTAG clock from, for example 35MHz to 10MHz, has been know to correct the "Cannot halt the processor" issue.

     

  • 0 in reply to Marcus Cooksey
    Prodigy 250 points

    Dear Marcus,

    Thanks for the information of JTAG clock issues, I have tried to slow down the clock to 10.368MHz, the test result is same.

    I have got the "usbwebcam.gel" file from LeopardImaging, my JTAG connection is failed, too.

     

    I try to use shf_DM36x.exe tool to write u-boot, My test steps is as following:

    ## Step 0.

    Set switch position of BTSEL[2:0] to "011"

    ## Step 1.

    sfh_DM36x.exe -norflash NORWriter.out UBL_eucdk_NOR.bin

    -----------------------------------------------------
       TI Serial Flasher Host Program for DM36x
       (C) 2011, Texas Instruments, Inc.
       Ver. 1.50
    -----------------------------------------------------


    Platform is Windows.
    Flashing NOR with NORWriter.out and UBL_eucdk_NOR.bin.


    Attempting to connect to device COM1...
    Press any key to end this program at any time.


    Waiting for the DM36x...

    ## Step 2.

    Comment out PLL1Init and PLL2Init in the {flash_utils}\DM36x\Common\src\device.c file.

    Rebuild the sfh_DM36x.exe and do test, again.

    The result is same as above:

    Waiting for the DM36x...

    ## Step 3.

    Comment out "BOOTMESEQ" tag and "goto BOOTMESEQ" statement, the test result is as following:

    sfh_DM36x.exe -norflash NORWriter.out UBL_eucdk_NOR.bin

    -----------------------------------------------------
       TI Serial Flasher Host Program for DM36x
       (C) 2011, Texas Instruments, Inc.
       Ver. 1.50
    -----------------------------------------------------


    Platform is Windows.
    Flashing NOR with UBL_eucdk_NOR.bin and u-boot-eucdk.bin.


    Attempting to connect to device COM1...
    Press any key to end this program at any time.


    Waiting for the DM36x...
    ACK command sent. Waiting for BEGIN command...
            Target:

    Is that a normal condition?

    or

    I am missing some important configuration?

    I would appreciate all of your any suggestions!

    Thanks!

  • 0 in reply to YenHung Chen
    TI__Genius 9510 points

     

     

     

     

     

     

     

     

     

     

     

     

    Can you confirm that the baud rate of the set in the  sfh_DM36x tools is set to  ~141800 (per the ROM errata)?  Also SD boot it an option as well (see http://processors.wiki.ti.com/index.php/SD_card_boot_and_flashing_tool_for_DM355_and_DM365)

     

    Revision(s) Affected

     

     

     

     

     

     

     

     

     

     

    1.1 (not present on silicon revision 1.2)

    Details

     

     

     

     

     

     

    The OSM_SEL (Over-Sampling Mode Select) bit in the UART0 MDR (Mode Definition

    Register) should be set to 0. The current boot ROM code sets it to 1.

    OSM_SEL = 0: 16x over sampling => Divisor value = clk/(16*baud_rate)

    OSM_SEL = 1: 13x over sampling=> Divisor value = clk/(13*baud_rate)

    The choice of divisor value for UART is affected by OSM_SEL for a particular baud_rate.

    Workaround(s)

     

    To workaround this issue, use higher baud rate code. The desired baud rate of 115200

    should be increased to 16/13 times (i.e., ~141800).

  • 0 in reply to Marcus Cooksey
    Prodigy 250 points

    Dear Marcus,

    I have solved this issue by using Wintech XDS560V2 + CCS4.2.3.

    Thanks for your help.

    I comment my test about RS-232 communication as following:

    # The baud rate 141800 does not work, it will response wrong parameter while opening the COM port.

    I just wondering why this method does not work?

     

    Best Regards