HotFix_1: CAN extended ID not working properly
Problem: When trying to send with extended ID, it does not set the proper configurations
Root Cause: Coding building error
Workaround: Update the files attached in the following folders
{install_dir}\mbdtbx_s32k14x\mbdtbx_s32k14x\mscripts\fcan\mbd_s32k14_fcan_send_sdk_params.p
Customer Report:
Special thanks to gramirezv for reporting and testing our fix.
Cumulative patch:
Starting from today, all patches will come in the form of self-extracting zips and will contain all the patches, up-to-date. A user can install at any point in time the latest patch and get all the patches from before, regardless if he had or had not installed some previous patch.
Usage:
Run MBDT_cumulative_patch_1.exe and enter the following path when prompted:
{YOUR_INSTALL_DIR}\NXP_MBDToolbox_S32K1xx\code
e.g.: C:\Users\my_user_name\Documents\MATLAB\Add-Ons\Toolboxes\NXP_MBDToolbox_S32K1xx\code
Most likely you will be asked if you want to overwrite some files - just click on 'Yes to All' option.
MBDT_cumulative_patch_1 contains:
MBDT_cumulative_patch_2 contains:
MBDT_cumulative_patch_3 contains:
Hello sparkee,
It is not necessary - these were integrated in the 4.1 version. Furthermore, if you install these updates over v4.1, you'll break some links to our blocks. We'll make another hotfix page when issues are found and fixed for v4.1.
Kind regards,
Razvan.
Thank you for the patch. I have been installing everything in the default method and there is not a \code directory that was used in the referenced path. It seems to line up with this path without the \code folder, which does not exist in my 4.0.0 install on R2018b.
...\MATLAB Add-Ons\Toolboxes\NXP_MBDToolbox_S32K1xx
Hi JesseBeeker,
The existence of the "code" folder is dictated&controlled by the MATLAB version used: for 2018a or smaller the installation of the toolboxes (any) will be placed in "code" folder while on the newer versions of MATLAB that "code" folder is no longer used.
Thanks for bringing this in discussion, and hopefully making this clear for everyone using our toolboxes.
Best regards,
Daniel
HotFix_3: GCC 6.3 compilation error
Problem: Not able to build any model using gcc 6.3 due to missing path to libwinpthread-1.dll missing.
Root Cause: Missing path to .dll
Workaround: Update the files attached in the following folders
{MBDT_ROOT}\mbdtbx_s32k14x\mbdtbx_s32k14x\mbd_s32k14_make_rtw.p [modify]
{MBDT_ROOT}\mbdtbx_s32k\mscripts\utils\mbd_s32k_add_gcc_to_path.p [add]
HotFix_5: GCC makefile error - nosys.specs not finding file
Problem: GCC compilation fails when having spaces in the path
" No such file or directory arm-none-eabi-gcc: error: nosys.specs: No such file or directory"
Root Cause: Paths not taken into account in the template makefile for the -nosys.specs option.
Workaround: Install cumulative patch (minimum version 3)
For this fix, the patch will replace mbd_s32k14.tmf fiile.
HotFix_4: CAN Receive individual masking not working as expected
Problem: When using CAN Receive block, individual masking is not enabled
Root Cause: Reset value of MCR[IRMQ] is 0 - global masking enabled;
Workaround: Update the following file:
{ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x\blocks\fcan\fcan_s32k14_receive.tlc
which enabled individual masking for MBs.
Customer Report:
Special thanks to vinicius.oliveira@enfas.de for reporting this issue and testing our fix!
HotFix_2: SPI Peripheral Chip Select
Problem: Not able to change PCS on every transfer - only from Configuration block; this limits the SPI usage to 1 PCS.
Edit: Not able to select only the PCS pins that you need to use.
Root Cause: Lack of use-cases/examples
Workaround: Update the files attached in the following folders
- lpspi_s32k14_config.tlc move to {TOOLBOX_ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x\blocks\lpspi folder
- lpspi_s32k14_master_transfer.tlc move to {TOOLBOX_ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x\blocks\lpspi folder
- lpspi_s32k14_slave_transfer.tlc move to {TOOLBOX_ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x\blocks\lpspi folder
- mbd_s32k14_ec_toolbox.mdl move to move to {TOOLBOX_ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x folder
- mbd_s32k14_lpspi_get_pin_info.p move to {TOOLBOX_ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x\mscripts\lpspi folder
- mbd_s32k14_lpspi_instance_callback.p move to {TOOLBOX_ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x\mscripts\lpspi folder
- mbd_s32k14_lpspi_transfer_sdk_params.p move to {TOOLBOX_ROOT_DIR}\mbdtbx_s32k14x\mbdtbx_s32k14x\mscripts\lpspi folder
Customer Report:
Special thanks to Gustavo Ramirez for reporting this issue and testing our fix!