• State TI Thinks Resolved
  • Locked Locked
  • Replies 24 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 744 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.

Original question:

AWR1642: RFCMOS77GHz

AWR1642: RFCMOS77GHz

SREENATH VIPIN
Intellectual 455 points
Part Number: AWR1642
Other Parts Discussed in Thread: SYSBIOS

Hi,

Is the CAN data continuous or does it stop after giving a certain no of packets? Does it wait for any acknowledgement after sending a packet of data?

Because every time I do get a certain no of data and it stops and an error RED LED light will show in the PCAN USB FD.

Regards

Sreenath

  • 0
    TI__Guru*** 148124 points

    Hi,

    What sw are you running? Are you running the ti demo "labs\lab0005_object_data_over_can"?

    This demo should run continuously, there is no acknowledgement needed

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    hi,

    Yes, I am running the same demo and I am not getting the data continuously. I flashed the program. Made the necessary connections. opened the GUI. Pressed the initialize button on the GUI. and switched on the power to the AWR device. I will get some data and it will stop every time.

    Still didn't get any solution for this issue. this happens in our custom board as well as in AWR1642 Boost.

    BR

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    Hi,

    Our team has not seen this issue before.

    First we need to understand if the issue is on the AWR1642 sensor side or on the PCAN USB FD side.

    There are two ways to check if there is an issue on the sensor AWR1642 side

    1) Connect CCS debugger and let the sensor running, after a few minutes set a breakpoint and make sure the sensor is still running as expected. Run again after the breakpoint.

    2) Connect a oscilloscope and check that there is some activity on the CAN tx line. Even if you can't identify the data, you can still see if the sensor sends something on the CAN line.

    Regarding the PCAN, please contact PCAN support team to identify what the red LED light means

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    In order to debug, do I need to flash a different bin file?

    BR

    Sreenath

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    I am getting this error while I try to debug.

    "Cortex_R4_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x3c: This operation is not supported by this driver
    Cortex_R4_0: File Loader: Verification failed: Target failed to write 0x00000000
    Cortex_R4_0: GEL: File: C:\Users\sreenath\workspace_v10\odoc_16xx_mss\Debug\xwr16xx_odoc_ti_design_mss.xer4f: Load failed."

    Regards

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    Hi,

    In order to use CCS you would need to flash the ccs_debug.bin provided in SDK 2.1

    C:\ti\mmwave_sdk_02_01_00_04\packages\ti\utils\ccsdebug\xwr16xx_ccsdebug.bin

    Then you need to import in CCS the projects by importing

    \labs\lab0005_object_data_over_can\odoc-target\dss\odoc_dss.projectspec

    \labs\lab0005_object_data_over_can\odoc-target\mss\odoc_mss.projectspec

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    I keep getting this error

    Error connecting to the target:
    (Error -1170 @ 0x0)
    Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 9.3.0.00042)

    Can you help me resolve this?

    BR

    Sreenath

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    Cortex_R4_0: GEL: File: C:\Users\sreenath\workspace_v10\odoc_16xx_mss\Debug\xwr16xx_odoc_ti_design_mss.xer4f: Load failed."

    The same error.

    Regards

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    After flashing the ccs_debug.bin please make sure you switch back the jumper to "Functional SOP" setting

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    So what is the debug mode SOP Position used for "011"?

    Regards

    Sreenath

  • 0 in reply to SREENATH VIPIN
    Intellectual 455 points

    Hi,

    [Cortex_R4_0] Exception occurred in ThreadType_Task.
    Task handle: 0x800cd3c.
    Task stack base: 0x800b000.
    Task stack size: 0x800.
    R0 = 0x00000000 R8 = 0xffffffff
    R1 = 0x00000000 R9 = 0xffffffff
    R2 = 0x00000000 R10 = 0xffffffff
    R3 = 0x04c20010 R11 = 0xffffffff
    R4 = 0x00000000 R12 = 0x0000c57d
    R5 = 0x000194d8 SP(R13) = 0x0800b7d0
    R6 = 0xffffffff LR(R14) = 0x0001535c
    R7 = 0xffffffff PC(R15) = 0x000121fc
    PSR = 0x400c019f
    DFSR = 0x00000000 IFSR = 0x00000000
    DFAR = 0x00000000 IFAR = 0x00000000
    ti.sysbios

    .family.arm.exc.Exception: line 209: E_undefinedInstruction: pc = 0x000121fc, lr = 0x0001535c.
    xdc.runtime.Error.raise: terminating execution

    When I tried to debug this error seems to occur!

    regards

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    I think there are some incorrect steps in the process of

    Please follow the instructions provided in this document

    mmwave_automotive_toolbox_#_#_#\labs\lab0004_obstacle_detection\docs\ODSdemo_usersguide.pdf

    Section 3 "Flash the Device" provides instruction on how to flash a binary fine and the position of the SOP jumpers

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    I followed the exact procedure as mentioned in the section

    and this is what i got.

    "[Cortex_R4_0] **********************************************
    [C674X_0] Debug: MMWDemoDSS mmWave Control Initialization succeeded
    [Cortex_R4_0] Debug: Launching the Millimeter Wave Demo
    **********************************************
    Debug: MMWDemoMSS Launched the Initialization Task
    Debug: MMWDemoMSS mmWave Control Initialization was successful
    Debug: CLI is operational
    Sensor has been stopped
    [C674X_0] Debug: MMWDemoDSS Data Path init succeeded
    Debug: MMWDemoDSS initTask exit
    [Cortex_R4_0] Debug: MMWDemoMSS Received CLI sensorStart Event
    [C674X_0] Heap L2_Heap : size 49152 (0xc000), free 47104 (0xb800)
    Heap L1 : size 16384 (0x4000), free 4096 (0x1000)
    Heap L2 : size 49152 (0xc000), free 35368 (0x8a28)
    Heap L3 : size 786432 (0xc0000), free 499712 (0x7a000)
    [Cortex_R4_0] xdc.runtime.Main: "../mss_main.c", line 2289: assertion failure
    xdc.runtime.Error.raise: terminating execution
    [C674X_0] {module#8}: "../dss_main.c", line 345: error {id:0x10000, args:[0x81a444, 0x81a444]}"

    Regards

    Sreenath

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    Still no replay to the post?

    I am getting the same error.

    Regards

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    Hi,

    Sorry for the delay.

    I understand that you have modified the original code.

    I recommend you start with original code and make sure that you can successfully run it from CCS

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

     I have modified the code but I commented on that section and used only the original version of the code to debug.

    Still didn't work.

    Regards

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    Please download the code again from the TI Resource Explorer and try again. This code has been validated that it is working

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    I downloaded the code again and reflashed and tried running. It gave data for some time and again stopped. I tried to debug the code. It is not debugging properly. every time I stop the deggging the code will stop at the function  " MmwDemo_sleep(void)".

    Regards

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    Hi,

    I assume that you have used CCS to load and run the demo binaries.

    How do you stop the code execution?

    Here is what we recommend for debugging with CCS

    1) Identify the file where you would like to set a breakpoint.

    2) In CCS project, set the Optimization level for that file to "no optimization"

        - Right click on project, settings, optimization

    3) Re-build/re-load the code

    4) Set a breakpoint at desired location.

    5) Run the code

    Since this is a multicore application, when you set the breakpoint in the code that runs on one of the cores, the other core will probably time out. This should not be a problem. You should be able to step through the code where you have set the breakpoint.

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    hi,

    I have used ccs to load and run the binaries.

    I did exactly what you have suggested but the results are the same. I have placed breakpoints in multiple places in mss mains. I didn't hit any breakpoints.

    I always go to "void MmwDemo_sleep(void)" function. When I pause the debugging. This is what is happening every time.

    BR

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    Hi,

    When using CCS it is required, as mentioned in the demo UG, to flash the ccs

    C:\ti\mmwave_sdk_02_01_00_04\packages\ti\utils\ccsdebug\xwr16xx_ccsdebug.bin

    Did you flash this file?

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    Yes I have flashed the "xwr16xx_ccsdebug.bin" file

    Regards

    Sreenath

  • 0 in reply to SREENATH VIPIN
    TI__Guru*** 148124 points

    Hi,

    Are you able to run any demo successfully on the board?

    Maybe there are some issues with the board

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 455 points

    Hi,

    I tried running the demo on 2 boards. both of them had the same issue. Not able to successfully debug, in the case of the demo, as I mentioned earlier in the post it will run for like nearly 1 min and then will stop. I think its because of some error flag because in the visualizer it shows something like BRS ESI, then it stops

    Regards

    Sreenath