• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 653 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/IWR1642BOOST: 1642 output 2D FFT data

HAIGANG ZHAO
Intellectual 780 points
Part Number: IWR1642BOOST

Tool/software: Code Composer Studio

I tried to output 1642 2D FFT data from the serial port, but the serial port has no data output, and an error message is printed on the console. What is going on?

  • 0
    TI__Mastermind 28055 points

    Hi ZHG,

    Which demo are you running?  What have you changed to output the 2D FFT data?

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Intellectual 780 points

    Hi Justin,

    I am using the IWR1642BOOST DEMO board.

    The screenshot below is part of my code change.

    Regards,

    ZHG

  • 0 in reply to HAIGANG ZHAO
    TI__Mastermind 28055 points

    Hi ZHG,

    It looks like the mailbox does not recognize the message, so the software is not reaching the UART_writePolling line. You need to set the type of message.  You can see from the error code that the message type is not set when the message is sent - as a result, the message id is different in each version of the error.  Ensure you set message.type, and ensure that the mss has a condition to read that type.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Intellectual 780 points

    Hi Justin,

    I have set the message type.There is still some code that I have not shown, and now I am not sure if I have read the message type. I don't know how to do this. Is there any good advice? Thank you.

    Regards,

    ZHG

  • 0 in reply to HAIGANG ZHAO
    TI__Mastermind 28055 points

    Hi ZHG,

    So there is a file that defines the message types.  This is stored in common, but after importing to CCS, this file is actually duplicated.  So you will need to make sure the message type is defined in both versions of the file.

    When the MSS reads the message, it first reads the type, then does some action based on that message type. First thing to check is to make sure that the message type is the same in each frame to ensure that you are setting the type properly. (This is displayed when it outputs unidentified message type: xxx)  If the message type is the same every frame, you are setting it properly.  Then you just have to make sure that:

    1. The type is defined in the .h file. (Click on a different message type and press F3 to be taken to the file in question)
    2. Ensure there is a case for that message type defined in the mbox task.

    Regards,

    Justin