2179585_en-US

[#1]

Using S32K399A A53 primary core in bare-metal

Hello,

I have just started using a S32G-VNP-RDB3 and I would like to run some benchmark code on its A53 primary core (I may try the M7_0 one later). I intend to run my code without any RTOS or Linux - e.g. by calling my main() directly from U-Boot. I managed to build a project for the A53 core in S32DS but I found no debugging option that permitted me to run the debugger using the USB cable connected in J2 (UART0). Is it mandatory to have an external debugging probe to run my code in S32DS?

Thanks,

Ricardo

Re: Using S32K399A A53 primary core in bare-metal

Hello @ricardofranca,

I am glad you were able to solve your issue and thanks for selecting my reply as a solution.

If you encounter any problems in the future please do not hesitate to create another post. 

Re: Using S32K399A A53 primary core in bare-metalIt turns out I did not notice I had to compile code for AArch64 rather than AArch32... having fixed that, I could finally run my first function. Thanks!Re: Using S32K399A A53 primary core in bare-metal

Hello @alejandro_e ,

Thanks for your advice! As I am unable to acquire a probe at this moment, I am trying to run my code directly over U-Boot. I am able to upload a binary file using Tera Term and the U-Boot "loadb" command, but when I try to run the code using the "go" command, the board crashes ("Synchronous Abort" handler, esr 0x02000000) and resets.

The code I try to run is just a function that writes somewhere in the memory (e.g. 0x34100000) so that I can be sure it worked. I even tried to hard-code "BX LR" in the memory but I still made the board crash. I tried to run code either in the internal SRAM (0x34000000) or the LPDDR4 (0x80000000) and failed in both cases.

What am I doing wrong? Is there anything specific I must do so that I can call my own functions from U-Boot?

Thanks,

Ricardo

Re: Using S32K399A A53 primary core in bare-metal

Hello @ricardofranca,

Thanks for reaching out to us. Regarding your question, no, there is no way to debug the S32G3 cores using the serial port, you need to use an external debugger, for example the S32 Debug Probe or a PowerDebug System. You can check all supported debuggers in the Software section of the S32G3 page and searching for debug in both Public and By Partners sections:

The option to debug using the serial port is only by using serial prints into a console.

As as side note, although we support many debugging options, I would recommend using either the S32 Debug Probe or the Lauterbach option, since those are the ones we, the support team, have access to.

Please let me know if you have more questions