Runtime.BootloaderProgrammingSupport is not defined for selected hardware board.

I tried to run this TI PIL example, c2000_model_pil_block, on TI Piccolo F28035 board in MatLab R2021a, but there is a error
“The parameter Runtime.BootloaderProgrammingSupport is not defined for selected hardware board.”

Could you tell me where and how to configure this parameter?

Wei,

I believe that the reason this is failing is that since the F28035 doesn't have a specific HW target board (like LaunchPad), the PIL communication setting may not be correct.  We'll try and do that below.  Note that PIL expects to send/receive data across the SCI comm peripheral of the C2000 MCU.  If you are using a F28035 control CARD, this should be enabled if you are using the XDS100v2 connection on the control CARD dock station.  If you have a custom board you will need to interface one of the SCIs to your PC host.

In you Simulink project click "Hardware Settings" and then Select "HardWare Implementation".  If you scroll down you should see PIL as one of the options, you will need to pick the SCI module that you intend to use here.

Then you will need to go back up to the SCI module itself and set the GPIOs you intend SCI port to be on, so that Simulink can configure this when you build your project.

I think there is a default of SCIA on GPIO28 and GPIO29 when using the Piccolo F2803x HW.

Let me know if this gets us on the right track.

Best,

Matthew

Hi Matthew,

Thank you for your answer!

Follow your instructions, I re-checked all settings and connections, but the problem is still at here. 

I using Matlab R2021a.

please refer to these screenshots for my settings.

Thanks and best regards! 

Ma Wei

Ma Wei,

Thanks for the detailed screen shots, from what I can tell you have configured both the GPIOs and the control CARD switches correctly.

Assuming you are using a Windows OS, can you open the device manager and see if you observe 2 XDS100 devices, one for the emulation and the other as a serial(auxiliary) port?

I've attached the a screenshot of what I'm looking for below.  If we see both, that's great as it means the UART backchannel has enumerated.  I'd like to take note of the COM port associated with the aux port and make sure that this matches the COM port we've selected in Simulink.

If you DON'T see the 2nd port in the device manager, then we will need to re-program the FTDI chip to support it.  Let' see if that is the issue before we proceed.

Best,

Matthew

Hi Matthew,

Thank you for your patient.

I cannot find your screenshot, so I went through my device manager to look for XDS100 devices

is it OK?

thanks and best regards!

Ma Wei

Ma Wei,

Sorry about that, yes this is correctly showing up in Device Manager.  I'm going to loop in the MW team to see if they have some ideas now that we know the HW is good.

Best,

Matthew

I have the same issue with this.

I am using LaunchPad TMS320F28379D, Matlab R2021a version.

I am able to run model "c2000_pil_block.slx" (subsystem using a PIL block) without any issue.

However, with the same environment, when I try to run model "c2000_model_pil_block.slx" (referenced model code using PIL),

the same error occurs.

I believe my driver, settings are all correct because I am able to run run model "c2000_pil_block.slx".

Below is the log when error occurs in my environment.

-----------------------------------------------------------------------------

The model c2000_model_pil_block is configured to simulate flush-to-zero (FTZ) behavior, but is using normal mode simulation. To observe FTZ behavior, simulate the model using an accelerated mode.
Component: Simulink | Category: Model
Updating Model Reference Simulation Targets
Elapsed: 0.367 sec
Updating Model Reference Code Generation Targets 3
Elapsed: 16 sec
### Starting serial model reference code generation build
### Starting build procedure for: c2000_counter
The model c2000_counter is configured to simulate flush-to-zero (FTZ) behavior, but an instance of the model is using normal mode simulation. To observe FTZ behavior, reconfigure the required model instance to simulate using an accelerated mode.
Component: Simulink | Category: Model
### Successful completion of build procedure for: c2000_counter
Build Summary 1
Elapsed: 0.21 sec
Code generation targets built:

Model Action Rebuild Reason
==============================================================================================
c2000_counter Code generated and compiled Code generation information file does not exist.

1 of 1 models built (0 models already up to date)
Build duration: 0h 0m 17.215s
### Connectivity configuration for component "c2000_counter": Texas Instruments C2000 Base ###
### COM port: COM6
### Baud rate: 115200
### Preparing to start PIL simulation ...
Building with 'MinGW64 Compiler (C)'.
MEX completed successfully.
### Updating code generation report with PIL files ...
The model c2000_counter is configured to simulate flush-to-zero (FTZ) behavior, but an instance of the model is using normal mode simulation. To observe FTZ behavior, reconfigure the required model instance to simulate using an accelerated mode.
Component: Simulink | Category: Model
### Starting application: 'slprj\ert\c2000_counter\pil\c2000_counter.out'
Starting PIL simulation
The parameter Runtime.BootloaderProgrammingSupport is not defined for selected hardware board.
Component: Simulink | Category: Model error

Ung,

Thanks for the additional info, I've made the MW team aware of this post.  Will check with in with them tomm to see if this is something they are aware of.

Best,

Matthew

Hi Ung,

Please open the child model from MATLAB command - 'c2000_counter' and configure it for the same hardware as the top model.

Regards,

Venkatesh C

After setting c2000_counter and c2000_model_pil_block the same hardware, there is an error 

The model c2000_model_pil_block is configured to simulate flush-to-zero (FTZ) behavior, but is using normal mode simulation. To observe FTZ behavior, simulate the model using an accelerated mode.
Component: Simulink | Category: Model
Updating Model Reference Simulation Targets
Elapsed: 0.598 sec
Updating Model Reference Code Generation Targets 3
Elapsed: 17 sec
### Starting serial model reference code generation build
### Starting build procedure for: c2000_counter
The model c2000_counter is configured to simulate flush-to-zero (FTZ) behavior, but an instance of the model is using normal mode simulation. To observe FTZ behavior, reconfigure the required model instance to simulate using an accelerated mode.
Component: Simulink | Category: Model
### Successful completion of build procedure for: c2000_counter
Build Summary 1
Elapsed: 0.12 sec
Code generation targets built:

Model Action Rebuild Reason
===========================================================================
c2000_counter Code compiled Code instrumentation settings have changed.

1 of 1 models built (0 models already up to date)
Build duration: 0h 0m 18.175s
### Connectivity configuration for component "c2000_counter": Texas Instruments C2000 Base ###
### Preparing to start PIL simulation ...
### Updating code generation report with PIL files ...
[0x7FFA34B9E0A4] ANOMALY: use of REX.w is meaningless (default operand size is 64)
[0x7FFA34B9E0A4] ANOMALY: use of REX.w is meaningless (default operand size is 64)
The model c2000_counter is configured to simulate flush-to-zero (FTZ) behavior, but an instance of the model is using normal mode simulation. To observe FTZ behavior, reconfigure the required model instance to simulate using an accelerated mode.
Component: Simulink | Category: Model
### Starting application: 'slprj\ert\c2000_counter\pil\c2000_counter.out'
Starting PIL simulation
Downloading program to the target hardware...

Debug Server Scripting (DSS) error: The input line is too long.
The syntax of the command is incorrect.
[0x7FFA34B9E0A4] ANOMALY: use of REX.w is meaningless (default operand size is 64)
.

Hi Ung,

Have you ran the support package setup and provided the path to CCS installation? Ensure you don't have CCS IDE already open and connected to the hardware. That will also create conflict when MATLAB tries to access the hardware.

Regards,

Venkatesh C

Hi Venkatesh C,

Do you mean 3-party tools?

Validation Report for: Texas Instruments Code Composer Studio (C2000)

Toolchain Validation Result: Passed

Validation report:

### Validation of "MATLABSetup"

Validating command: codertarget.tic2000.internal.checkToolChain;

Passed.

### Validation of build tool "C2000 Assembler"

Checking for existence of path: $(TI_TOOLS)

C2000 Assembler: Unable to validate '$(CCSINSTALLDIR)/bin'. It contains unresolved macros.

Checking for tool command: cl2000

C2000 Assembler: Unable to validate '$(CCSINSTALLDIR)\bin\cl2000.exe'. It contains unresolved macros.

### Validation of build tool "C2000 C Compiler"

Checking for existence of path: $(TI_TOOLS)

C2000 C Compiler: Unable to validate '$(CCSINSTALLDIR)/bin'. It contains unresolved macros.

Checking for tool command: cl2000

C2000 C Compiler: Unable to validate '$(CCSINSTALLDIR)\bin\cl2000.exe'. It contains unresolved macros.

### Validation of build tool "C2000 Linker"

Checking for existence of path: $(TI_TOOLS)

C2000 Linker: Unable to validate '$(CCSINSTALLDIR)/bin'. It contains unresolved macros.

Checking for tool command: cl2000

C2000 Linker: Unable to validate '$(CCSINSTALLDIR)\bin\cl2000.exe'. It contains unresolved macros.

### Validation of build tool "C2000 C++ Compiler"

Checking for existence of path: $(TI_TOOLS)

C2000 C++ Compiler: Unable to validate '$(CCSINSTALLDIR)/bin'. It contains unresolved macros.

Checking for tool command: cl2000

C2000 C++ Compiler: Unable to validate '$(CCSINSTALLDIR)\bin\cl2000.exe'. It contains unresolved macros.

### Validation of build tool "C2000 C++ Linker"

Checking for existence of path: $(TI_TOOLS)

C2000 C++ Linker: Unable to validate '$(CCSINSTALLDIR)/bin'. It contains unresolved macros.

Checking for tool command: cl2000

C2000 C++ Linker: Unable to validate '$(CCSINSTALLDIR)\bin\cl2000.exe'. It contains unresolved macros.

### Validation of build tool "C2000 Archiver"

Checking for existence of path: $(TI_TOOLS)

C2000 Archiver: Unable to validate '$(CCSINSTALLDIR)/bin'. It contains unresolved macros.

Checking for tool command: ar2000

C2000 Archiver: Unable to validate '$(CCSINSTALLDIR)\bin\ar2000.exe'. It contains unresolved macros.

### Validation of build tool "MEX Tool"

Checking for existence of path: $(MATLAB_ARCH_BIN)

Passed.

Checking for tool command: mex

Passed.

### Validation of build tool "Hex Converter"

Skipped. No "Hex Converter" build tool is specified.

### Validation of build tool "DWO Converter"

Skipped. No "DWO Converter" build tool is specified.

### Validation of build tool "Download"

Checking for existence of path: $(TARGET_SCRIPTINGTOOLS_INSTALLDIR)/bin

Download: Unable to validate '$(CCSSCRIPTINGDIR)/bin'. It contains unresolved macros.

Checking for tool command: dss.bat

Download: Unable to validate '$(CCSSCRIPTINGDIR)\bin\dss.bat'. It contains unresolved macros.

### Validation of build tool "Execute"

Skipped. "Execute" build tool "$(PRODUCT)" cannot be validated.

### Validation of build tool "GMAKE Utility"

Checking for existence of path: %MATLAB%\bin\win64

Passed.

Checking for tool command: gmake

Passed.

### Checking for undeclared macros ...

Passed.

Thanks and best regards!

Ma Wei

Hi Ma Wei,

Can you download a simple model from MATLAB to this target? Dont do PIL, just build and download a simple model. Can you attach this log file of the successful download here?

Regards,

Venkatesh C

Hi Venkatesh C,

Follows your instructions, I tried this example. c28x_LedBlink_ert, I did not change any settings, but there is an error, please refer to screenshot.

Do you think my hardware is problem? how to check and confirm it?

Thanks and best regards!

Ma Wei

Hi Ma Wei,

Try to connect and download from CCS is successful. Any issue in doing that one would preliminarily point to a hardware issue.

Regards,

Venkatesh C

Hi Venkatesh C,

Thank you for your answer.

Could you tell me how to configure the connection, likes this? I cannot set COM port and Baudrate?

then, pressure Test Connection button, please refer to following for result:

[Start: Texas Instruments XDS100v1 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\70E4945\AppData\Local\TEXASI~1\
CCS\ccs1031\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Apr 29 2021'.
The library build time was '17:49:40'.
The library package version is '9.3.0.00058'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0[0x7FFE9F96E0A4] ANOMALY: use of REX.w is meaningless (default operand size is 64)

All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS100v1 USB Debug Probe_0]

The hardware is problem, right?

thanks and best regards!

Ma Wei

Ma Wei,

Your above output implies that both he emulator and the target HW are OK and can see each other.

Can you load an example project from C2000 Ware and see if you can download/run it on the board?  For example import the project here C:\ti\c2000\C2000Ware_3_04_00_00\device_support\f2803x\examples\c28\cpu_timer and see if you can load it(after build, etc).

Best,
Matthew

Hi MatthewPate,

Thanks you for your patient!

I never found the example you specified. Must I install TI C2000ware if I download this example?

Thanks and best regards!

Ma Wei

Hi MatthewPate,

Thanks you for your patient!

I think I downloaded the example to the hardware board.

Thanks and best regards!

Ma Wei

Ma Wei,

Thanks for this, this confirms that the connection is good from the PC/JTAG/Target, so that is not the issue.  Will see if MW has further guidance here.

Best,

Matthew

Hi MathewPate,

Thank you for your answer!

But there is still this error if I run PIL examples.

Thanks and best regards!

Ma Wei

Hi Ma Wei,

Since you have already contacted our support channel, we will help you solve the issue from there.

We can then come back and update the resolution here.

Regards,

Venkatesh C

Hi Venkatesh C,

At the beginning, I contacted your support team, but they told me to post my problem on E2E!

Anyway, solving my problem is OK!

Thanks and best regards!

Ma Wei

Hi Venkatesh C,

The problem was solved after installation CCS 10.1.

thanks a lot!

Best regards!

Ma Wei