hi,
Currently Planning to flash the demo code into S32G3 evaluation board via serial boot mode.
Connected USB cable to PC and board
Unable to detect the USB port
Also pls help me with the FSL image,Pls share the link for the download
Is FSL is required to detect the serial boot mode?
one more thing,unable to complete the demo code blinking LED.getting the below error.
Hi,
Below will be some comments on regards of your questions/issues:
Q1 >> Unable to detect the USB port
[NXP]: Which Debug Probe are you using? If it is S32 Debug Probe, can you see it under the "Device Manager" as follows (or similar):
If so, was the S32 Debug Probe already connected when you enter the specific window? If not, you need to click the refresh button for the GUI to scan for newly connected devices.
Q2 >> Also pls help me with the FSL image,Pls share the link for the download. Is FSL is required to detect the serial boot mode?
[NXP]: Can you help us elaborate more on regards of what "FSL image" means?
Q3 >> unable to complete the demo code blinking LED.getting the below error.
[NXP]: Which demo are you following? Can you help us elaborate on the different steps you have followed? Which RTD version are you using?
Please, let us know.
Hi @Daniel-Aguirre ,
WHen i connected (Micro USB cable)One side is connected to PC and another side connected to J2(UART0)
Pls find the pic--It is detected as USB serial PORT
2)I just checked flashing via SD card
but this below error message came
3)I have followed this below method as suggested by you
Thanks for the quick reply
Hi,
Below will be some comments on regards of your questions:
Q1 >> WHen i connected (Micro USB cable)One side is connected to PC and another side connected to J2(UART0)
[DA]: This connection is a serial port, not for debugging. UART0 is not a debug port, hence it is not shown under the debug window.
Q2 >> I just checked flashing via SD card. but this below error message came
[DA]: Can you confirm if the referred file is contained under the directory that you are executing the command? You should have the *.sdcard file available under the directory that you are executing the command.
Q3 >> I have followed this below method as suggested by you
[DA]: Which RTD version are you using? Can you help us elaborate on the different steps you have followed? We have done this demo with multiple versions and have not seen this message shown on our side.
Please, let us know.
Hi,
Below will be some comments on regards of your open points:
1)Connected USB cable to J4-USD for debugging
[DA]: We don't see any J4-USD connector under the NXP reference boards. Can you help us elaborate on which specific evaluation board are you using?
2)I dont have idea on SD card
[DA]: An SD card is required to be able to flash the *.sdcard as per the command that you are using.
3)Pls find the RTD version
[DA]: Can you help us elaborate on the different steps you have followed? We have done this demo with RTD v4.0.0 and cannot see this message shown on our side.
Please, let us know.
Hi Daniel,
Board name is S32G-VNP-RDB3.Sorry it is J4 USB
Hi Daniel,
Board name is S32G-VNP-RDB3
Connected Micro USB cable to J4.
Could you give me some information on importance of SD Card.Without SD card ,can i flash code using serial boot mode?
RTD image
Thanks
Hi,
Thanks for your feedback.
As told under the RDB3 Reference Manual, J4 is for USB Host/Device functionality, not for debugging nor flashing.
We might be misunderstanding the overall inquiry, if so we do apologize. We can recommend looking into the SW Enablement Training available under the RDB3 product page (link: S32G3 Vehicle Networking Reference Design | NXP Semiconductors). In there, you should be able to better understand the first steps and the required ports in order to flash your device.
As if SD card is necessary to flash a program, unless you are trying to boot the platform with the SD interface, it is not. You should be able to use the available QSPI flash available under the RDB3. More information on regards of the different boot interfaces for RDB3 can be found under the S32G3 RM [Page 1347, S32G3 Reference Manual, Rev. 4, 02/2024].
Please, let us know.
Hi,
If your account is not enabled, we recommend contacting your local NXP FAE/DFAE/representative, for them to provide you with the required access, if any.
You should also be able to use the Automotive Software Package Manager, steps are explained below:
We can recommend following the below steps, to understand if it helps you get enabled:
- Access the Automotive Software Package Manager available under the Software section of the S32G3 product page (link: S32G3 Safe and Secure Vehicle Network Processor | NXP Semiconductors).
- In there, select under Devices the S32G3 option.
- Once selected, 3 options should be displayed: GoldVIP, Integrated Software Bundle and Integration Reference Examples. Select the Integrated Software Bundle option.
- Once selected, click the Generate Bundle Installer button.
- This action will require NXP approval for generation of the bundle. Can take up-to 48 hours to be approved. This should be noticed under the email linked to the NXP account.
Please, let us know.