topic Re: S32R RSDK Path issue in Other NXP Products

S32R RSDK Path issue

jamesdavis — Tue, 22 Oct 2024 23:05:18 GMT

Hi,

I'm trying to get the tools for the R45 set up and I'm having a few issues. I've got the LAX Toolbox and Radar Toolbox installed in Matlab (together with the Embedded Coder Toolbox). I also have S32DS V3.5 with the Radar extensions, S32R45 development and BBE32 Addon packages, as well as a bunch or GCC Arm compilers installed.

When running mbd_lax_dependencies_path.mlx it is missing the path to RDSK.

Error message:

Error using mbd_lax.nxp.utils.get_rsdk_path
Invalid RSDK path. Edit and run mbd_lax_dependencies_path to configure the toolbox!

The path points to:

rsdkPath = 'C:\Users\my.name\AppData\Roaming\MathWorks\MATLAB Add-Ons\Toolboxes\NXP_MBDToolbox_LAX\mbdtbx_lax\RSDK'

Which doesn't exist. I've downloaded SWS32R45_Radar_SDK_1_2_1_CD_D2405 which contains a subfolder "rdsk", but it's unclear to me what I need to do in order to install it. Manually copying the subfolder doesn't work.

Re: S32R RSDK Path issue

petervlna — Wed, 23 Oct 2024 09:02:06 GMT

Hello,

I have asked RADAR team for feedback here.

Best regards,

Peter

Re: S32R RSDK Path issue

jamesdavis — Mon, 28 Oct 2024 21:25:24 GMT

Hi. The Customer has asked for an update on this one.

Re: S32R RSDK Path issue

jamesdavis — Tue, 29 Oct 2024 14:11:26 GMT

More Customer feedback:

Did you hear back from NXP? I've got another question regarding the toolboxes. I'm currently trying to get the FFT going using the Matlab toolbox and so far see some differences between Matlab and the SPT toolbox that I can't fully explain. There seems to be some documentation around the SPT but I'm not sure if I have all that exists or if there is a reference manual for SPT. I do have the SPT3.X_Toolbox_User_Guide which is very brief.

My specific problem is that I want to do a complex FFT, which I presume to have the call correct, however it looks almost like I'm doing a real FFT (almost because the two halfs don't quite match up).

This is the call:

[out, acc_shift(1), exec_time(1)] = rdx4_mex(complex(Window), input, 'WIN_ENABLED', 'MULTIPLE_COEFF', 0, 'QUAD_EXT', 0, 'NO_ADPTV');

for k = 1:round4 - 1

[out, acc_shift(k+1), exec_time(k+1)] = rdx4_mex(tw, out, 'WIN_DISABLED', 'MULTIPLE_COEFF', k, 'QUAD_EXT', 0, 'NO_ADPTV');

end

if round2

[out, acc_shift(k+2), exec_time(k+2)] = rdx2_mex(tw, out, round4, 'NO_OPERANDS_SPLIT', 'QUAD_EXT', 0, 'NO_ADPTV');

end

[WinFFT, acc_shift(k+3), exec_time(k+3)] = rdx2_mex(tw, out, round4 + round2 - 1, 'OPERANDS_SPLIT', 'QUAD_EXT', 0, 'NO_ADPTV');

(window being a Hann window scaled to 2^15, input a complex 256 entry vector and tw being the twiddle factors copied over from spt3x_FFT1 from example advanced/object_detection)

And this is the result:

(note: the first half of the SPT FFT is flipped)

I can share the example if you want to have a look at it.

Re: S32R RSDK Path issue

petervlna — Thu, 31 Oct 2024 08:31:21 GMT

Hello,

Please see update from RADAR team:

When he says that he has the LAX Toolbox, does he mean the NXP_Support_Package_LAX as well?

Also, I noticed that the "rsdk" folder is not being created when installing the NXP_MBDToolbox_LAX add-on, but you can use the "rsdkPathCustom" to select the RSDK path:

-rsdkPathCustom = fullfile('C:', 'NXP', 'SW32R45_RSDK_1.2.0_D2403', 'rsdk');

The "NXP_MBDToolbox_LAX version 1.2.0" was tested for the RSDK version 1.2.0, try it with the RSDK version: SW32R45_RSDK_1.2.0_D2403, that is the one that worked for me.

best regards,

Peter

Re: S32R RSDK Path issue

jamesdavis — Thu, 31 Oct 2024 12:53:39 GMT

Hi,

Thanks for that. Here is the latest Customer inquiry:

FFT now works as expected; either the example I picked did something different than what I thought, or it had a bug. Windowed and non-windowed transforms match up with Matlab now.

The next step is to understand the execution time, the toolbox returns an execution time variable. I couldn't find any documentation about what the value means but assumed it to be clock cycles. If that is true, the performance I get is about 2.5 times worse than what Andy had in his presentation. These are the numbers I got:

Average FFT(256) execution time 161.00 cycles, 268.33 ns, 3726708.1 FFTs/s
Average windowed FFT(256) execution time 161.00 cycles, 268.33 ns, 3726708.1 FFTs/s

Assuming 600MHz clock and two FFT accelerators this would come out to be about 7.5M FFT/s (instead of the 18.7 mentioned in the presentation)

I've managed to find and install the Radar SDK 1.2.1, however the LAX toolbox still reports errors with the path, so I would need some help sorting that out.

Re: S32R RSDK Path issue

jamesdavis — Thu, 31 Oct 2024 22:17:25 GMT

More Customer feedback:

Another question: The toolbox couldn't write the Linux image to the SD Card, I assume our antivirus is interfering with it. I've used Rufus to write the image to the card and there is a partition "boot_s32r4" showing up with an Image file and s32r45-evb.dtb. I assume this is correct, however the board doesn't seem to boot. There are some garbled characters on the serial port and it doesn't seem to show up on the network. Is there anything else required, e.g. boot mode jumpers?

Re: S32R RSDK Path issue

petervlna — Fri, 01 Nov 2024 07:42:19 GMT

Hello,

Unfortunately supporting of such applications is not in capability of general support.

RADAR is supported directly via FAE.

Please get in touch with your NXP FAE and ask support for this case.

I am not able to help you with it further.

Best regards,

Peter