What is the power supply voltage range over which the S32K144EVB-Q100 can operate?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

What is the power supply voltage range over which the S32K144EVB-Q100 can operate?

1,919 Views
ranulf
Contributor IV

What is the power supply voltage range over which the S32K144EVB-Q100 can safely operate? The quick start guide says 12 V, of course, but is the range known? I can't find a datasheet for the board. 

0 Kudos
6 Replies

1,918 Views
ranulf
Contributor IV

I have a board that got 13.9 V. Now it is not recognized by the Windows 10 PC. I am wondering if the slightly high voltage could have contributed to the failure.

0 Kudos

1,912 Views
Robin_Shen
NXP TechSupport
NXP TechSupport

Hi ranulf,

Although according to the description of Get Started with the S32K144EVB the External Power Supply should be 5-12V. But I don't think 13.9 V will damage the power supply of the board.

External Power Supply (5-12V).png
The UJA1169TK/F seems able to work according to the description of Mini high-speed CAN system basis chip (REV 1.0). Please check the voltage of J107 Pin1(P5V_SBC) is still OK, when using 12V external power supply(connect Pin1-2 of J107).

S32K144EVB-Q100 sch.png

S32K144EVB can also be power through USB port(J7). Connect pin2-3 of J107 and check if it works.

J104.png
Please make the board enter BOOTLOADER mode:
1. Connect Pin 1-2 of J104
2. Hold down RESET Button(SW5)
3. Connect to the USB port and let OpenSDA K20 enter BOOTLOADER mode
4. Release RESET Button(SW5)

Then click "SDA_INFO" in this BOOTLOADER driver, show "Your Hardware Information" of your board to me.

SDA_INFO.png

If there are issue at Installed Application and Application Version, you can drop new application firmware:

5. Drop application firmware into BOOTLOADER drive
6. Remove and replace the USB cable.

 

Although the hardware is slightly different, still you can refer: S32K148EVB Dead after OpenSDA Update. Need help to recover.

 

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.
-------------------------------------------------------------------------------

0 Kudos

1,849 Views
ranulf
Contributor IV

@Robin_Shen Thank you for your helpful response.

 
The voltage at J107 Pin1 when using a 12V external power supply is 5 V.
 
The board is not powered anymore through USB when pins 2-3 of J107 are connected even though the green diode near the Open SDA MCU chip does flash when the USB is plugged in. Also the COM port for the board no longer shows up in Windows Device Manager.  
 
Below is the hardware information
Board Name is: EVB-S32K144
MicroBoot Kernel Version is: 1.08
Bootloader Version is: 1.13
Application Version is: 0.00
DUID is: FBE33938-24BB81A0-3755080C-DABAE678
EUID is: 0381A239-8AA1872E-1853EA17-00C368D6
TUID is: 74823938-47328196-8568DD75-9242986D
TOA is: 86B6E505-14311D24-B33B464C-D5EB8F01
TOA2 is: 86B6E505-DD682D2B-C5FAE810-46DFF349
SUID is: 86B6E505-5B819677-37239804-8003EC65
 
I should add that at the time of failure I was using pins J5-16 (Tx), J5-18 (Rx), and J5-12 (Gnd) for UART at 5 V. I notice that these pins are also used for LIN. Could this have somehow caused the deletion of the OpenSDA firmware?
 
Other pins were connected for BMS application as described in Table 6 on pages 7 and 8 of the document “UM11143 Battery cell controller software driver v1.1".
 
I did download the OpenSDA Firmware Apps as described in your link to "S32K148EVB Dead after OpenSDA Update. Need help to recover". There did not appear to be a perfect match for this board, but I dropped what appeared to be the closest match: "MSD-DEBUG-S32K142EVB-Q100_Pemicro_121.SDA". Is this the best choice? Should I look elsewhere for the correct driver?
 
After dragging and dropping the firmware to the drive BOOTLOADER and unplugging and plugging the USB there were a few changes:
1) the drive name became S32K142EVB, which isn't quite right. (According to the Quick Start Guide the drive name should be EVB-S32K144. This suggests that the download does not contain the right firmware for this board.)
2) The voltage accross pins 3-2 of J107 is now 5.1 V.
3) An OpenSDA COM port is now visible in Device Manager.
 
This exercise has demonstrated to me that the hardware is probably not damaged, even if I may not yet have the right firmware. Do you know where I can get the right firmware for the board? Do you have any ideas about how/why the original firmware was deleted?
 

(Incidentally, I have had to post this message to the thread multiple times because it keeps disappearing!)

0 Kudos

1,837 Views
Robin_Shen
NXP TechSupport
NXP TechSupport

Hi ranulf,

Application Version is: 0.00
It means there is no Application in OpenSDA. So you need to drop OpenSDA Firmware Apps into it.
Please try to use MSD-DEBUG-EVB-S32K144_Pemicro_v119.SDA.

Do you drop other files into MSD or BOOTLOADER driver before? It may caused the original firmware disappear.

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.
-------------------------------------------------------------------------------

0 Kudos

1,832 Views
ranulf
Contributor IV

No, I did not drop other files into MSD or Bootloader. 

0 Kudos

1,778 Views
ranulf
Contributor IV

The voltage at J107 Pin1 when using a 12V external power supply is 5 V.

The board is not powered anymore through USB when pins 2-3 of J107 are connected even though the green diode near the Open SDA MCU chip does flash when the USB is plugged in. Also the COM port for the board no longer shows up in Windows Device Manager.

Below is the hardware information
Board Name is: EVB-S32K144
MicroBoot Kernel Version is: 1.08
Bootloader Version is: 1.13
Application Version is: 0.00
DUID is: FBE33938-24BB81A0-3755080C-DABAE678
EUID is: 0381A239-8AA1872E-1853EA17-00C368D6
TUID is: 74823938-47328196-8568DD75-9242986D
TOA is: 86B6E505-14311D24-B33B464C-D5EB8F01
TOA2 is: 86B6E505-DD682D2B-C5FAE810-46DFF349
SUID is: 86B6E505-5B819677-37239804-8003EC65

I should add that at the time of failure I was using pins J5-16 (Tx), J5-18 (Rx), and J5-12 (Gnd) for UART at 5 V. I notice that these pins are also used for LIN. Could this have somehow caused the deletion of the OpenSDA firmware?

Other pins were connected for BMS application as described in Table 6 on pages 7 and 8 of the document “UM11143 Battery cell controller software driver v1.1".

I did download the OpenSDA Firmware Apps as described in your link to "S32K148EVB Dead after OpenSDA Update. Need help to recover". There did not appear to be a perfect match for this board, but I dropped what appeared to be the closest match: "MSD-DEBUG-S32K142EVB-Q100_Pemicro_121.SDA". Is this the best choice? Should I look elsewhere for the correct driver?

After dragging and dropping the firmware to the drive BOOTLOADER and unplugging and plugging the USB there were a few changes:
1) the drive name became S32K142EVB, which isn't quite right. (According to the Quick Start Guide the drive name should be EVB-S32K144. This suggests that the download does not contain the right firmware for this board.)
2) The voltage accross pins 3-2 of J107 is now 5.1 V.
3) An OpenSDA COM port is now visible in Device Manager.

This exercise has demonstrated to me that the hardware is probably not damaged, even if I may not yet have the right firmware. Do you know where I can get the right firmware for the board? Do you have any ideas about how/why the original firmware was deleted?

(Incidentally, I have had to post this message to the thread multiple times because it keeps disappearing!)

0 Kudos