Hi NXP MBDT team,
I tried several times to generate the code of a basic example "gpio_s32k144.mdl" and download it to the board without success (the code is well generated but the download process did not accomplished: it hangs at the following step
*** Created executable: gpio_s32k144.mot
### Successful completion of build procedure for model: gpio_s32k144
For your information
I use Matlab release 2019a
NXP Model-Based Design Toolbox for S32K1xx – version 4.1.0
The board is well connected and detected
In target connection i tried to refresh the OpenSDA Drive Name => without success
I have selected OpenSDA Drive Name "F:EVB-s32k144 => without success
I tried also to type in the the corresponding Custom OpenSDA Drive Name => without success
I have copied the gpio_s32k144.mot directly to the board => without success
With all the previous steps i can not run any application
Could you please help me to resolve this issue
Thanks in advance for your support
Hi NXP,
The issue is now resolved. I'm able to import the generated code to S32DS and build it.
However, we still have the projects that use Motor Ctrl library not working.
Thank you so match for your support.
Hello mohamed.benderradji@faurecia.com,
Here is a fix for the importer - to work with AMMCLib as well. Could you please confirm that everything works as expected?
You need to replace the following file:
{TOOLBOX_ROOT}/mbdtbx_s32k/mscript/utils/mbd_s32k_ds.p
Kind regards,
Razvan.
Hi,
I have done what you requested
The green led next to the OpenSDA is ON
The LASTSTAT.TXT is empty, I don't know how i can join it as an attached file to the discussion
I still have the issue, i can't flash the board directly from matlab
Thanks in advance for your support
Hello mohamed.benderradji@faurecia.com ,
I have provided a patch here for the importing of projects generated by our toolbox into S32Design Studio (Note: version 2.2 - the latest one available on nxp.com).
For the patch you'll have to update the following files (preferably you should have a backup for them, before overwriting them):
{TOOLBOX_ROOT}/mbdtbx_s32k/mscript/utils/mbd_s32k_copy_required_files.p
{TOOLBOX_ROOT}/mbdtbx_s32k/mscript/utils/mbd_s32k_ds.p
{TOOLBOX_ROOT}/mbdtbx_s32k/mbd_s32k_make_rtw_hook.p
{TOOLBOX_ROOT}/mbdtbx_s32k/mbd_s32k.tmf
Note: projects that need the AMMCLib library is still under investigation - it seems to be an issue with the linking in S32DS. For that you can not import it as is, you can just select the elf file to flash/debug on the target. I will be out of office the next week, but once I return I will continue the investigation and patch that as well.
Kind regards,
Razvan.
Hi,
You find bellow the requested informations:
Hello mohamed.benderradji@faurecia.com,
It seems we have the same version on the OpenSDA.
I attached a generated .mot file from the gpio examples. Please drag and drop in the new mounted disk and after that please send us the LASTSTAT.TXT file content.
Also, please pay attention to the green led next to the OpenSDA because it provides a status, it is explained here https://www.nxp.com/docs/en/user-guide/OPENSDAUG.pdf .
Hope this helps,
Marius
Hi,
You find blow the photo of S32K144EVB jumper setup
Below the content of LASTSTAT.TXT file
Hello mohamed.benderradji@faurecia.com,
The OpenSDA contains an SDA_INFO.HTM. Can you please send me the content displayed under "Your Hardware information" like here:
You can try at the PEmicro website to see if there are any updates for the OpenSDA.
Also, you can try flashing the gpio generated mot file with the S32DS to see if the generated code works as expected. You don;t need to import the project, just flash the generated .mot file.
Hope this helps,
Marius
Hello mohamed.benderradji@faurecia.com,
As far as I understand from your post, the .mot has been successfully generated.
In target connection i tried to refresh the OpenSDA Drive Name => without success
The refresh button will look for all the mounted devices, it will not select the one you need.
I have selected OpenSDA Drive Name "F:EVB-s32k144 => without success
This is how it looks for me.
I tried also to type in the the corresponding Custom OpenSDA Drive Name => without success
For the custom SDA name you need to type only the letter fo the mounted Drive. In my case is D, your case F
I have copied the gpio_s32k144.mot directly to the board => without success
From this reason I assume there is a problem with the board, maybe the jumpers are not right set. Make sure the S32K is powered up. For reset jumper, the J104 must be connected 1-2. If you want to power the CPU from the USB then the J107 must be set 2-3. If you want to power up the controller from external sources the J107 must be set 1-2.
Marius
Hello mohamed.benderradji@faurecia.com ,
When you connect the S32K144EVB to your computer, can you go to the mounted drive (F in the case you described) and share the contents of the following file?
LASTSTAT.TXT
Kind regards,
Razvan.
Hi,
You find blow thea photo of your S32K144EVB jumper setup
And mohamed.benderradji@faurecia.com ,
Can you also share with us a photo of your S32K144EVB jumper setup? And maybe a photo with the revision you have, just so we can replicate the exact scenario you are using.
Kind regards,
Razvan.