I am using S32K148EVB and below are details of the board:
Board Name is: S32K148EVB-Q144
MicroBoot Kernel Version is: 1.08
Bootloader Version is: 1.13
Installed Application: PEMicro S32K148EVB-Q144 Mass Storage/Debug App
Application Version is: 1.21
DUID is: 29233939-4E2081BC-3729F80A-E64EE678
EUID is: 31C1A238-DF3A8752-182ADA1D-045768D6
TUID is: 74823938-47328196-8568E098-E23D9853
TOA is: 86B6E505-E7FF17DE-49FE5217-B058E2F2
TOA2 is: 86B6E505-3734BF21-53A72B5C-0BEFFCDB
SUID is: 86B6E505-5BC18991-37239804-8003EC65
Currently the board is dead and not communicating. I wanted to get continous trace data for SeggerSystemView, which needs JLINK for connection, hence I tried to convert the OpenSDA interface on EVB to JLINK.
I followed the below procedure, after which board doesn't boot-up.
1. Remove the USB connection.
2. Hold the RESET button and plug the USB cable to boot into Bootloader.
3. Downloaded the bin file (https://www.segger.com/downloads/jlink/OpenSDA_V3_2)
4. Followed procedure as per (https://www.segger.com/products/debug-probes/j-link/models/other-j-links/opensda-sda-v2/)
5. After the .bin file is copied to the bootloader drive and power reset, board doesn't bootup.
Kindly help ASAP as I am stuck.
The whole point of the exercise was to switch between OpenSDA and JLINK interfaces to support Debug and Tracing. But since the board is dead, I would need to get the board working first.
Thanks in advance!
Solved! Go to Solution.
Hi Vijay_Arwapally,
P5V_SDA shows 5v on multimeter but POWER_EN is always 0v. It mean OpenSDA firmware issue.
You need to enter BOOTLOADER mode and then drop application firmware into it(OpenSDA_V1.bin or MSD-DEBUG-S32K148EVB-Q144_Pemicro_v122.SDA).
1. Connect Pin2-Pin3 of J22 to select RST Push Button
2. Hold down RST Push Button(SW5)
3. Connect to the USB port and let OpenSDA K20 enter BOOTLOADER mode
4. Release RST Push Button(SW5)
5. Drop application firmware into BOOTLOADER drive
6. Remove and replace the USB cable.
The S32K148EVB Board is now updated to the latest application firmware.
J-Link application firmware:
OpenSDA application firmware:
Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Thanks a ton for the support!
Board is back and working. Thanks for your illustrations, I am now able to switch between JLINK and MSD Debugger.
Few more general questions below:
1. Can we use JLINK firmware for debug/flashing?
2. JLINK seems to be over UART
I suppose these the UART pins of K20, and the interface between K20 and S32K148 internally is still SWD?
What is the speed of UART JLINK CDC? Because when I am trying to record data via Segger SystemView I see data overflow.
Is it possible to switch the below P&E debugger between debug and JLINK?
http://www.pemicro.com/products/product_viewDetails.cfm?product_id=15320143&productTab=1
1. Can we use JLINK firmware for debug/flashing?
A1. yes
A2. It's CDC UART Port, OpenSDA with P&E firmware support it too.
Please download the S32K148EVB-Q176 Evaluation Board – REV B Schematics (REV B ), then you can see the connection between K20(OpenSDA) and S32K148.
Please read "1.4 Understanding the USB/OpenSDA" of GET STARTED
3. What is the speed of UART JLINK CDC? Because when I am trying to record data via Segger SystemView I see data overflow.
A3. You can configure the UART baudrate between K20 and S32K148(by configure LPUART1 of S32K148)
4. Is it possible to switch the below P&E debugger between debug and JLINK?
No. It's P&E Multilink FX
Hi Vijay_Arwapally,
The Bootloader Version is: 1.13
So please download the J-Link OpenSDA - Generic Firmwares for OpenSDA V1 Bootloader.
If J-Link interface is still not recognized, I am afraid you need to switch it back to OpenSDA.
I am not at office today, so I can not test it. If still not work, I will test it tomorrow on my S32K148EBVB.
Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Hello @Robin_Shen ,
The EVB is dead. Nothing is recognized on computer when EVB is connected via USB cable.
Also I dont see any LEDs or activity on the board, when the connection is made. How do I recover the board, to switch between OpenSDA and JLINK.
Are you able to read the S32K148EVB OpenSDA information again?
Enter OpenSDA Bootloader Mode:
And check the power:
Board doesn't power-up, I tried to power using USB connection, it was working prior to the steps I performed. So jumpers are in correct position to power up via USB.
I can perform those OpenSDA steps only if I see some mass storage detection on PC. In this case, no device is detected.
What would be the first step to get board operational?
"Also I dont see any LEDs or activity on the board, when the connection is made."
DS3 is not light, so we can check the P5V0 and VDD.
You can measure the voltage at J7(pin2-pin3).
Since we choose to use OpenSDA port for power supply(J8 pin2-pin3), so we should check the P5V_SDA_PSW.
The P5V_SDA_PSW is output from U24, then we should check P5V_SDA and POWER_EN. The POWER_EN is output from K20(OpenSDA), so it may caused by there is no firmware application running in your OpenSDA K20.
Will DS3 light if you connect J8(pin1-pin2)? This will power the S32K148EVB through an external power supply (J9).
Would you please let me know the version of your S32K148EVB? You need to remove resistor for Rev.A board.
Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Tried debugging the hardware as per your hints, when power via external power supply(12v adapter and setting jumpers as required), I see that micro is booting and board works.
Same is not true when powered via USB connection, when powered via external supply and USB connection is also made, no MSD is detected on computer.
P5V_SDA shows 5v on multimeter but POWER_EN is always 0v. Does that mean OpenSDA firmware issue? How to restore it?
PS: Board is RevB
Hi Vijay_Arwapally,
P5V_SDA shows 5v on multimeter but POWER_EN is always 0v. It mean OpenSDA firmware issue.
You need to enter BOOTLOADER mode and then drop application firmware into it(OpenSDA_V1.bin or MSD-DEBUG-S32K148EVB-Q144_Pemicro_v122.SDA).
1. Connect Pin2-Pin3 of J22 to select RST Push Button
2. Hold down RST Push Button(SW5)
3. Connect to the USB port and let OpenSDA K20 enter BOOTLOADER mode
4. Release RST Push Button(SW5)
5. Drop application firmware into BOOTLOADER drive
6. Remove and replace the USB cable.
The S32K148EVB Board is now updated to the latest application firmware.
J-Link application firmware:
OpenSDA application firmware:
Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------