• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 33 subscribers
  • Views 265 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWRL1432BOOST: [how to debug sdk example code on this eval board]

ks lim
Prodigy 100 points
Part Number: AWRL1432BOOST
Other Parts Discussed in Thread: MMWAVE-L-SDK, AWRL1432

Hello,

I just received AWRL1432BOOST Eval-board and I tried loading the example code with ccs via connecting to usb.

But hard fault is happened.Could somebody give me advice on this symptom?

Let me explain in more what I did.

I just installed CCS and SDK, and I picked one sdk example, named as "motion_and_presence_detection_demo_xwrl14xx_evm~~"…

I opened the example code on the CCS and build was done automaticcally.

It appears that I wrote binary on the board by pressing the debug icon.

It is in debug mode, so it starts debugging from main.

Among the debug options, I think I selected "texas inst~~xda110 usb debug probe/cortex_M4_0" item.

( I wanted to attach screen-picture, but I can not.)

When I go a few steps from main(), Hard Fault error was occurred on "gMainTask = xTaskCreateStatic..." line from below codes.

What's the reason? how to solve this to debug code?

int main()
{
/* init SOC specific modules */
System_init();
Board_init();

/* This task is created at highest priority, it should create more tasks and then delete itself */
gMainTask = xTaskCreateStatic( freertos_main, /* Pointer to the function that implements the task. */
                                                   "freertos_main", /* Text name for the task. This is to facilitate debugging only. */
                                                   MAIN_TASK_SIZE, /* Stack depth in units of StackType_t typically uint32_t on 32b CPUs */
                                                   NULL, /* We are not using the task parameter. */
                                                   MAIN_TASK_PRI, /* task priority, 0 is lowest priority, configMAX_PRIORITIES-1 is highest */
                                                   gMainTaskStack, /* pointer to stack base */
                                                   &gMainTaskObj ); /* pointer to statically allocated task object memory */
configASSERT(gMainTask != NULL);

....

}

I have one more question on this system.

- When I tried to program binary, where that binary was programmed? mcu ? or Qspi s/f on the baord?

Thanks in advace for your advice & help.

Best Regards,

kslim

  • 0
    TI__Guru*** 141284 points

    Hi,

    Congratulations on purchasing the AWRL1432EVM!

    First, we recommend downloading the latest mmWave L SDK 5.4.0.1: https://www.ti.com/tool/MMWAVE-L-SDK

    After downloading the latest SDK release, we recommend running the oob demo:

    C:\ti\MMWAVE_L_SDK_05_04_00_01\examples\mmw_demo\mmwave_demo

    If you wish to run this demo from CCS,

    Please follow the instructions provided in the following doc to run with CCS

    xWRL1432 MMWAVE-L-SDK: CCS Launch, Load and Run

    What type of debugging are you trying to perform?

    ks lim said:
    - When I tried to program binary, where that binary was programmed? mcu ? or Qspi s/f on the baord?

    The binary is flashed on the external flash available on the board

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 100 points

    Hi, Cesar.

    Thank you for your kind help.

    reply my reply as ks>> below.

    First, we recommend downloading the latest mmWave L SDK 5.4.0.1
    ks> Thanks. I replaced from 5.3.x.x to 5.4.0.1

    xWRL1432 MMWAVE-L-SDK: CCS Launch, Load and Run
    ks> Thanks. I think it was very tricky on me. I tried 7~8 times by guide docs. 

           Finally I got to know my mistake from guide docs and then now I can do it, even if it is very incomfortable.

    What type of debugging are you trying to perform?
    ks>>I am planning to develop 77Ghz signal receiver to detect 77Ghz signals from cars or other radar devices.
    So I thought I have to make it modifying one of sdk-example code.
    At first I need to find a suitable example code to check many things, such as how to control/get adc-data/debug ...etc.(but I heard there is not right example code, but I have to find a way.)

    I have two simple questions.
    1. Is there any way to turn off Tx signal with the other functions all enabled? Becasue I just want to detect 77Ghz signal,so I don't need Tx signal.
    2. Can I adjust sweep range of chirp, such as 100Mhz or 10Mhz or fixed-frequency(no sweep case)? Can I change type of chirp?

    BR

    ks lim

  • 0 in reply to ks lim
    TI__Expert 3665 points

    Hi Ks Lim 

    1. TI does not currently provide such a way. Out of curiosity what kind of application do you need this for?

    2. You can change the parameters of the chirp by changing the cli cfg parameters in the profile. For a better description of all the configurable chirp parameters please see the following section on Sensor front-end parameters under mmwave demo in README_FIRST_xWRL1432.html in the SDK 5.4.0.1

    Thankyou, 

    Zorah

  • 0 in reply to Zorah Ahmad
    Prodigy 100 points

    Hi Zorah,

    I answer for your question above and ask something more.


    Q. What kind of Application do you need ?:
    ks>>
    Application that receives Radar signals coming from 77Ghz source like radar-gun, cars.
    we need to recognizes the type of the received signal's modulation.
    -> I think the frequency sweep range(chirp range) should be adjustable from fixed frequency(ex: 77.5Ghz) to full range.

    ks>>

    I am sorry for asking so many basic questions. -_-;;
    1. do I need to change the configuration parameters in FW? Or is it possible with the visualizer?

    2. Can I output adc buffer data or arbitrary data to the visualizer you provide?

    3. Which programs are written to external qspi s/f? And do we not program to M4 of AWRL1432?
    Is there any information to know the boot sequence?

    BR

    KSLim

  • 0 in reply to ks lim
    TI__Expert 7135 points

    Hey KS Lim,

    I apologize for your post bouncing between a few of our engineers here, but I will answer your questions in order:

    1. Configuration parameters are specified through the CLI commands in the .cfg files sent over UART to a device after it has been flashed with an application image. The CLI commands in these files are used to adjust chirp parameters, the front-end, and what data should be outputted. For the mmWave Demo, a list of all CLI commands used can be found in the documentation Zorah pointed out (<MMWAVE_LSDK_INSTALL_DIR>/docs/api_guide_xwrL14xx/MMWAVE_DEMO.html) in the section "Configuration (.cfg) File Format (CLI INTERFACE)." 

    I'm not sure which visualizer you are using currently, but assuming you are using the SDK visualizer (<MMWAVE_LSDK_INSTALL_DIR>/tools/visualizer/visualizer.exe), you can select the Generate Custom Configuration option in the Configuration Selection panel of the Configuration Dashboard to create a basic .cfg file. However, for finer control and understanding of how configuration parameters affect device performance, I would highly recommend spending some time experimenting with the mmWave Sensing Estimator. 

    2. You cannot output ADC data directly to the SDK visualizer as it only interprets UART TLV data. You would need a DCA1000 and mmWave Studio to capture raw ADC data. If you do have a DCA1000 or end up getting one, you can follow the DCA1000 mmWave Studio User Guide from the Radar Toolbox to get started raw data capture.

    3. The last resource I would like to point you to is the xWRLx432 Technical Reference Manual which contains a lot of great information on device peripherals, initialization, power modes, and architecture. The boot sequence is described in Section 4.4 on p. 187, but for the most part, the M4F RAM and other relevant memories are written to from SFLASH upon boot up from power down. We only ever program directly to RAM in the event that there is no SFLASH device present.

    I know this is a lot of information and resources to parse through, but I hope I was able to answer your questions to some capacity. Take your time to look through the documentation provided, but feel free to reach out for those deeper questions.

    Regards,

    Kristien