• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 83 subscribers
  • Views 2451 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.

LAUNCHXL-F28377S: Serial Connection in Simulink (missing header/source file?)

Armin L.
Intellectual 480 points
Part Number: LAUNCHXL-F28377S
Other Parts Discussed in Thread: CONTROLSUITE

Hi all! ;)

I want to establish a serial connection to my F28377S-LaunchPad via “Serial Send” and “Serial Receive” blocks. In a previously created model, I was already able to send commands to a DAC block and receive measured data.
Now I wanted to create a similar model to read the measured shaft speed from an eQEP block using serial connection. But in contrast to the DAC model (where everything worked fine), MATLAB is now showing an error message:

"C:/.../supportpackages/tic2000/src/ext_svr_c2000.c", line 54: fatal error: cannot open source file "multiword_types.h"


However, the model runs properly if I choose external mode and include the Simulink scope in the model which runs on the MCU.
Might this missing source file be a consequence of the “checkEnvSetup” command? Because I only configured it to support my other F28069M-LaunchPad. The board string ‘F28377S’ is simply not supported by the “checkEnvSetup” command.

Best regards,
Armin

  • 0
    Mastermind 9005 points

    checkEnvSetup command applies for interface to CCSv3, CCSv4 and CCSv5. The F28377S requires CCSv6, and therefore does not require using this command. We are working to update and clean up the configuration, as it can be confusing. 

    However, you may not have your MathWorks SW configured correctly for CCSv6 (or need to change it). To reconfigure, type >> targetupdater at the MATLAB command line.

    Note: We added support for F28377S starting in R2015b.If you are using an older version you will likely need to upgrade (and this may explain why you might be missing files).

    -Brian

  • 0 in reply to Brian McKay
    Intellectual 480 points

    Hi Brian,

    In fact I am using a newer MATLAB version together with CCSv6. So the problem should not apply to me.
    But when I use the "targetupdater" command, there is no option to set a certain target hardware, right? The prompt only asks for the path to CCS and controlSUITE.
    But what should I change to work with F28377S? Should I also reset all "checkEnvSetup" options I set for my previous LaunchPad (F28069M)?

    Best regards,
    Armin

  • 0 in reply to Armin L.
    Mastermind 9005 points

    Hi Armin,

    You do 2 things to select the hardware.

    1) Use the library blocks from the corresponding Simulink Block Library (F2837xS). There are multiple levels of blocks; some blocks apply to many/ all C28X devices, and some blocks apply to specific devices (like the DAC for F2837xS). You can see this with the blue notation on the Simulink block and in the documentation.

    2) In the Configuration Parameters ->  Hardware Implementation tab, there are a drop downs to select your device. Make sure they are correct.

    HTH,

    -Brian

  • 0 in reply to Brian McKay
    Intellectual 480 points

    Hi Brian,

    Thank you very much for the help! However, I already set up the whole configuration as you recommended in your post but the model still outputs the above-mentioned error.
    However, today I noticed that there is a warning at the top of the log of the Diagnostic Viewer which states:

    The parameter ExtMode is enabled for model 'eQEP_Test'. However, a deployment build ignores this parameter. If you want to run an External mode simulation, in the model window, select External from the Simulation drop-down menu. Then click the "Play" button. Otherwise, to avoid this warning, disable this parameter by running the command set_param('eQEP_Test', 'ExtMode', 'off').

    So there seemed to be something wrong with the model configuration. To solve this problem, I simply opened the previous model (with the DAC block) that successfully ran on the MCU in "Normal" mode, deleted all blocks, copied the blocks from the eQEP model into this blank model and saved it with a different name. The configuration is fine now and the model runs in both modes.

    Best regards,
    Armin