• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 504 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:

IWR1443BOOST: pre-set configuration on boot

IWR1443BOOST: pre-set configuration on boot doesnt allow new parameters

jason Anderson
Expert 1080 points
Part Number: IWR1443BOOST

Hi,

I applied the recommended CLI config for hard-coded on-boot settings and it works fine. However my program won't take new settings anymore, i believe it should with the given code? I tested the visualizer and i get no indication that the board receives the new settings. The output however is processed in the visualizer, the object data. I put some System_printf() statements in the functions that process the parameters. They get called and printed on-boot, but not when i try to apply new settings. Any clue why this is happening?

cheers

  • 0
    TI__Mastermind 21295 points

    Hi Jason,

    Can you clarify which code and GUI you are using?  Is it the code (modified to support hard-coded chirp configuration) and GUI from the High Accuracy Range Measurement - 14xx lab?

    Regards,

    John

  • 0 in reply to JohnH
    Expert 1080 points

    Hi,

    i am using the high accuracy lab and the high accuracy lab visualizer, not the fluid level one.

    The program also doesn't seem to be taking UART input from self-made scripts that i wrote, which DO work with the standard labs. so it seems it shouldnt be a problem with the input method, but the code not taking any input.


    thank you,

  • 0 in reply to jason Anderson
    TI__Genius 11405 points
    Jason,

    It seems the cli command parameters didn't get passed to the register. Could you set break point in the code and see if the value is successfully passed?

    Thanks and Regards,
    Michelle
  • 0 in reply to Michelle Liu
    Expert 1080 points
    I put print s in the function to handle it, But iT only prints on boot, So seems to me the UART doesn’t Pick up anything? I Will Try with breakpoints
    Thnx
  • 0 in reply to jason Anderson
    Expert 1080 points

    Hi,

    Breakpoints seem to get ignored. From my prints i can tell data seems to be received, i get a debug output when i send a file to the board. but the data does not seem to be processed.

    summary: can see data is received as UART receives something according to my printf. but the data doesnt get changed, like the rangeLimit.

    I haven't changed anything from the code i received from TI. Any ideas?

    the code from this thread:

    cheers

  • 0 in reply to jason Anderson
    TI__Genius 11405 points
    Jason,

    To add new cli command, I recommend to modify the mmw_high_accu_14xx_cli.c. In MmwDemo_CLIInit function, cli configuration is defined. You'll need to add your command there. The added command cmdHandlerFxn should also be defined in this file.

    During debug, you can set the breakpoint to the function you added above and see if the cli config is received.

    Thanks and Regards,
    Michelle
  • 0 in reply to Michelle Liu
    Expert 1080 points
    That is exactly what i did. the breakpoints and print statements do not seem to get reached upon re-sending a profile.
    its not only my custom command, its the same for the other parameters. i tested with rangelimit. there is no difference after sending via serial. However the serial data IS noticed by the board. it can tell when i send something, but it cannot process the new parameters. I have no clue where to go from here.

    cheers
  • 0 in reply to jason Anderson
    TI__Genius 11405 points
    Jason,

    Did you mean that the breakpoint is not reached even for the release high accuracy 14xx lab? That is, if you do not modify the code, only re-compile in your PC. If you set the breakpoint, for example, at MmwDemo_CLIInit from main.c, it will be missed? Or you couldn't step into it?

    Thanks and Regards,
    Michelle
  • 0 in reply to Michelle Liu
    Expert 1080 points
    Hi,

    none of my breakpoints seem to get reached. I put several along with print statements before and after the breakpoint. the print statements get printed out but theres nothing happening with the breakpoints while debugging.

    I checked the breakpoint properties, they are set to remain halted. yet nothing happens. No clue how to proceed from here.

    cheers
  • 0 in reply to jason Anderson
    TI__Genius 11405 points

    Jason,

    Something is not right in your debug. Here's what you need to do:

    1. compile the lab on your PC

    2. Flash the SDK ti/unitilty/ccsdebug binary onto BOOST EVM

    3. Start CCS and connect to ARM, load the compiled binary from step1

    4. Set breatpoint at main.c file line 1487 where MmwDemo_CLIInit() is called (I'm using SDK1.2)

    5. Run the project

    6. It'll stop at that breakpoint, press step into, then scroll up to select an CLI function you like to monitor, I just randomly selected adcbuff, set a breakpoint. Then let it run continuously, input cli command in tera term (or visualizer). It'll stop at the 2nd breakpoint (adcbuff). See below snapshot:

    Above is just an example on how to setup breakpoint to do debug. 

    Thanks and Regards,

    Michelle