MATLAB Answers

Customized hardware implementation causes a simulink error: Invalid index with 2018b.

19 views (last 30 days)
Johnsee on 24 Nov 2018
Commented: Lars Rosqvist on 15 Feb 2019
I am customizing my own hardware implementation according to the tutorial: using ert.tlc with matlab 2018b.
When I select my customized hardware implementation and ert.tlc(Embedded Coder) as system target file, the simulink 'Build Model' command reports a 'Component:Simulink | Category:Block diagram error: Invalid index' error as shown in the following picture,
When I run the sl_build(gcs) command independently, the detailed error is displayed as,
Error using
Invalid index.
Error in Simulink.filegen.internal.FolderSpecificationTokens/resolveTargetEnvironemntToken
Error in Simulink.filegen.internal.FolderSpecificationTokens
Error in Simulink.filegen.internal.FolderConfiguration
Error in slbuild_private
Error in sl (line 15)
Error in slbuild (line 83)
sl('slbuild_private', mdl, target, varargin{2:end});
My customized script is just as follows without any modifications from the above URL,
function sl_customization(cm)
function thisDev = loc_register_device
thisDev = RTW.HWDeviceRegistry;
thisDev.Vendor = 'MyDevVendor';
thisDev.Type = 'MyDevType';
thisDev.Alias = {};
thisDev.Platform = {'Prod', 'Target'};
thisDev.setWordSizes([8 16 32 32 32]);
thisDev.LargestAtomicInteger = 'Char';
thisDev.LargestAtomicFloat = 'None';
thisDev.Endianess = 'Unspecified';
thisDev.IntDivRoundTo = 'Undefined';
thisDev.ShiftRightIntArith = true;
The Hardware Implementation pane is shown as follows:
By the way, it works correctly in the MATLAB 2017b environment and my computer system version is Windows 10 1809.
How can I customize my own hardware implementation correctly for scientific purposes in 2018b?
Thanks in advance for your answers.

Accepted Answer

Lars Rosqvist
Lars Rosqvist on 29 Nov 2018
Edited: Lars Rosqvist on 30 Nov 2018
The problem is this line:
thisDev.Alias = {};
Set this to something else than empty.
thisDev.Alias = {'MyDev'};
Lars Rosqvist
Lars Rosqvist on 15 Feb 2019
Hi Hankun,
No, in many cases these files are protected by the developer so you cannot access them.
In this case the solution is simple. In the new update of MATLAB R2018b the need of having Alias specified has been fixed, so you do not need to update this file. Just update MATLAB.
I have verified this in update 3 of R2018b and it works.

Sign in to comment.

More Answers (2)

Andrei Vlad
Andrei Vlad on 30 Nov 2018
I am trying to generate code for an STM32 discovery board (STM32L476G) for academic purposes.
I am using matlab 2018 and embedded coder together with the STM32 Mat/Target support package and STM32CubeMx.
I have selecte in Hardware Implementation STM32 as the vendor and device type.
I have generated a .ioc (cubemx config) file which I have then imported and specified the correct cubemx path in matlab.
I have built a simple example to control the LEDs based on the joystick (see attachment).
When trying to generate code I get the following issue: Invalid index.
Current observation: The model itsself is not a problem as i can remove all stm32 specific blocks and leave a very simple logic without solving the issue.
Assumption: The STM32 library which is imported when selecting stm32 in hardware implementation is not imported with a correct index.
Please help me solve this issue!
Many thanks,
  1 Comment
Jonathan Mott
Jonathan Mott on 25 Dec 2018
From your Simulink model, select Model Configuration Parameters. Under the Hardware Implementation menu, select Custom Processor from the Device vendor drop down list. Make sure you configure it so it has the same device details as the STM32 32-bit Cortex-M Device type.

Sign in to comment.

Lars Rosqvist
Lars Rosqvist on 30 Nov 2018
Try to search for a function called loc_createDevice in your STM installation.
If you find it, check if the Alias is empty.
Andrei Vlad
Andrei Vlad on 27 Dec 2018
Sorry for the late reply. Indeed, I have used the same fix (production hardware different from target hardware). I have also contacted STMicroelectronics directly, but they did not offer an answer.
In the meantime I have seen there are many other bugs in the tools STM provides (MAT Target, CubeMx, SW4STM32). Hopefully they will be fixed soon.
Best regards,

Sign in to comment.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!