• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 80 subscribers
  • Views 640 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.

CCS/MSP432E411Y: SysCFG issue with NDK and "display" undefined

Raymond Mack
Expert 1575 points

Part Number: MSP432E411Y
Other Parts Discussed in Thread: SYSCONFIG

Tool/software: Code Composer Studio

Please let me know if there is another place you want feedback on the SysCFG tool.  So far pretty awesome!! A lot easier to use than the configuration using XCONF with the 1294 Tiva in CCSv6 from 5 years ago!

It is a little disconcerting knowing if the defaults are appropriate for my application. Using the MSP432E401 Launchpad right now but will move this to my real code on the MSP432E411 soon. I'll know if defaults are the right stuff soon!!

So, here is the feedback:

I added the IP, TCP, and UDP packages because I want to be able to hard code the MAC and IP for my application.  This necessitated removing ndk_tirtos.c from the out of the box demo directory. I am struggling to find where the "display" handle gets created.  It is presently unresolved. I have grep'ed but haven't found where it gets set.

You might want to add instructions somewhere (perhaps when IP gets added in SysCFG) that board.c replaces ndk_tirtos.c. Of course, you also need instructions on the "display" handle!

I noticed that the NDK config file is where the unresolved reference occurs and the calls to Display_printf are commented out in the main ndk_tirtos.c file.  Guessing there is some issue that has not been resolved for this.

  • 0
    TI__Mastermind 22640 points
    Hello Raymond,

    I will look into this and get back.

    Thanks,
    Sai
  • 0
    TI__Mastermind 22640 points

    Hello Raymond,

    Apologize for the delay in response!

    Thanks for the detailed feedback on sysconfig!

    Raymond Mack said:
    I added the IP, TCP, and UDP packages because I want to be able to hard code the MAC and IP for my application.  This necessitated removing ndk_tirtos.c from the out of the box demo directory.

    Looks like Sysconfig integration for the Out of Box Demo example is broken. As you have mentioned, the ndk_<rtos>.c file should not be included in the sysconfig based project. Thanks for bringing this to our notice! I will file a bug so that we can fix this in the next release.

    Raymond Mack said:
    I am struggling to find where the "display" handle gets created.

    The Out of Box demo does not use "display" driver as the example is designed to use a command line like interface for users to interact with the out of box demo.  The access to UART is managed by a gatekeeper task called "commandTask" in the file "command_task.c" and it uses APIs from UART TI-Driver.

    If all you need is using the IP, TCP and UDP protocols along with "Display" then please review examples in the folder ./examples/syscfg_preview/rtos/MSP_EXP432E401Y/ns/. They are simpler than the out of box example and use "Display".

    Raymond Mack said:
    You might want to add instructions somewhere (perhaps when IP gets added in SysCFG) that board.c replaces ndk_tirtos.c.

    ndk_tirtos.c file is replaced by ./debug/syscfg/ti_ndk_config.c file. The Board.h, MSP_EXP432E401Y.c and MSP_EXP432E401Y.h files are replaced by Board.h and Board.c files.

    Hope this information helps!

    Regards,

    Sai

  • 0 in reply to Sai Reddy
    Expert 1575 points
    Sai:

    Thanks for the reply. After I hit send, I noticed that the Sysconfig tool automatically generates the file that has the Display calls. That means that you cannot go in and comment out those lines. It will just get overwritten when the file gets generated again! If you look at the Out of the Box demo files in the CCS part of the tree, you will see that those lines are commented out in the example files.

    So, I presume that is another bug report you need to forward.

    With the exception of these small issues, the tool looks to work pretty well. It sure helped me figure out what to do in my project!

    Ray
  • 0 in reply to Raymond Mack
    TI__Mastermind 22640 points
    Thanks Raymond for all the feedback!

    Are you talking about the commented out "Display_printf" calls in "outofboxhooks.c" file? If so, that file is not touched by Sysconfig. So the commented out lines should not be altered.

    Thanks,
    Sai

**Attention** This is a public forum