nPM1300EK, WARN module_pmic: No response from PMIC.

[mej7000]

nPM1300ek version: 0.9.0

I have both "nPM Controller" and "USB PMC" USB connected. I tried powering USB PMC through the computer and also tried a "Wall Wart USB". 

I have not made any connections to the nrf52840dk board, but I don't believe a dk board is necessary to evaluate the nPM1300ek.

youtu.be/PZqxVZsbqWI

I jumped NTC to 10k as my Battery does not have NTC.

I tried it with and without a battery connected.

No LEDs to light when I plug in USB PMC, but I don't know if an LED is supposed to light

I get a flashing LED (near the nPM Controller USB port) when nPM Controller is USB plugged in.

2024-06-28T16:16:02.938Z INFO Initialising nrfutil module: device
2024-06-28T16:16:02.997Z DEBUG Application data folder: C:\Users\mej\AppData\Roaming\nrfconnect\pc-nrfconnect-npm
2024-06-28T16:16:03.025Z DEBUG App pc-nrfconnect-npm v1.3.0 (official)
2024-06-28T16:16:03.025Z DEBUG App path: C:\Users\mej\.nrfconnect-apps\node_modules\pc-nrfconnect-npm
2024-06-28T16:16:03.025Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-06-28T16:16:03.025Z DEBUG nRFConnect path: C:\Users\mej\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-06-28T16:16:03.025Z DEBUG HomeDir: C:\Users\mej
2024-06-28T16:16:03.025Z DEBUG TmpDir: C:\Users\mej\AppData\Local\Temp
2024-06-28T16:16:08.022Z INFO Using nrfutil-device core version: 7.12.0
2024-06-28T16:16:08.661Z INFO Using nrfutil-device version: 2.1.1
2024-06-28T16:16:08.662Z INFO Using nrf-device-lib version: 0.17.5
2024-06-28T16:16:08.662Z INFO Using nrfjprog DLL version: 10.24.0
2024-06-28T16:16:08.662Z INFO Using JLink version: JLink_V7.94e
2024-06-28T16:16:08.861Z INFO Device Connected SN:001050203102
2024-06-28T16:16:08.861Z INFO Getting serialport options from persistent store 001050203102.pc-nrfconnect-npm
2024-06-28T16:16:08.863Z INFO Device Connected SN:F3CAA24A012CB708
2024-06-28T16:16:08.864Z INFO Getting serialport options from persistent store F3CAA24A012CB708.pc-nrfconnect-npm
2024-06-28T16:16:25.395Z INFO Selected device with s/n F3CAA24A012CB708
2024-06-28T16:16:25.404Z INFO Opened port with options: {"path":"COM6","baudRate":115200}
2024-06-28T16:16:25.492Z INFO Closed port: COM6
2024-06-28T16:16:25.492Z INFO Device setup ready for device with s/n F3CAA24A012CB708
2024-06-28T16:16:25.496Z INFO Opened port with options: {"path":"COM6","baudRate":115200}
2024-06-28T16:16:25.727Z WARN module_pmic: No response from PMIC.
2024-06-28T16:16:25.734Z WARN module_pmic: No response from PMIC.
2024-06-28T16:16:25.753Z WARN module_pmic: No response from PMIC.
2024-06-28T16:16:25.767Z WARN module_pmic: No response from PMIC.

...

# nRFConnect System Report - 2024-06-28T17-02-25.192Z

- System: HP OMEN Laptop 15-ek0xxx
- BIOS: AMI HPQOEM - 1072009
- CPU: 1 x Intel Core i7-10750H 2.6 GHz 12 cores (6 physical)
- Memory: 3.5 GB free of 15.8 GB total
- Filesystem: C: (NTFS) 1.8 TB 34.7% used

- OS: Microsoft Windows 11 Pro (10.0.22631) Windows x64

- Versions
- kernel: 10.0.22631
- git: 2.41.0.windows.3
- node: 20.11.1
- python: 3.12.2
- python3:
- nrfutil-nrfutil-device: 2.1.1
- Connected devices:
- 001050203102 PCA10056: COM49, COM48
- F3CAA24A012CB708 : COM6, COM5

- Current device:
- name: nPM1300 Evaluation Kit
- serialNumber: F3CAA24A012CB708
- cores: Unknown
- website: Unknown

VERBOSE LOGGING:
2024-06-28T17:03:40.509Z INFO Initialising nrfutil module: device
2024-06-28T17:03:40.574Z DEBUG Application data folder: C:\Users\mej\AppData\Roaming\nrfconnect\pc-nrfconnect-npm
2024-06-28T17:03:40.600Z DEBUG App pc-nrfconnect-npm v1.3.0 (official)
2024-06-28T17:03:40.600Z DEBUG App path: C:\Users\mej\.nrfconnect-apps\node_modules\pc-nrfconnect-npm
2024-06-28T17:03:40.600Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-06-28T17:03:40.600Z DEBUG nRFConnect path: C:\Users\mej\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-06-28T17:03:40.600Z DEBUG HomeDir: C:\Users\mej
2024-06-28T17:03:40.600Z DEBUG TmpDir: C:\Users\mej\AppData\Local\Temp
2024-06-28T17:03:45.375Z INFO Using nrfutil-device core version: 7.12.0
2024-06-28T17:03:45.520Z INFO [PID:25064] nrfutil-device (version = 2.1.1, platform = x86_64-pc-windows-msvc) invoked with list --traits mcuBoot,serialPorts --hotplug --json --log-output=stdout --log-level trace
2024-06-28T17:03:45.520Z DEBUG [PID:25064] cargo = false, force_libnrfdl_lookup = false, force_nrfutil_libdir = false
2024-06-28T17:03:45.520Z DEBUG [PID:25064] Creating the nrfdl context via nrfdl_create_context_with_config: Plugin location is assumed to be C:\Users\mej\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.1.1\lib\nrfutil-device
2024-06-28T17:03:45.531Z VERBOSE [PID:25064] [devkit] C API function: get_version_list
2024-06-28T17:03:45.531Z DEBUG [PID:25064] [devkit] Operation get_version_list failed with error code NRFDL_ERR_NOT_SUPPORTED
2024-06-28T17:03:45.648Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] open
2024-06-28T17:03:45.648Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] start
2024-06-28T17:03:45.691Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
2024-06-28T17:03:45.691Z DEBUG [PID:25064] [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
2024-06-28T17:03:45.691Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] open
2024-06-28T17:03:45.691Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] just_check_family
2024-06-28T17:03:45.691Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] open_dll
2024-06-28T17:03:45.691Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
2024-06-28T17:03:45.707Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command open executed for 51 milliseconds with result 0
2024-06-28T17:03:45.707Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] jlink_dll_version
2024-06-28T17:03:45.707Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
2024-06-28T17:03:45.707Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] dll_version
2024-06-28T17:03:45.707Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command open executed for 5 milliseconds with result 0
2024-06-28T17:03:45.722Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command jlink_dll_version executed for 15 milliseconds with result 0
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] dll_version
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] dll_version
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:45.738Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command jlink_dll_version executed for 0 milliseconds with result 0
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] close
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] close
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
2024-06-28T17:03:45.738Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:45.739Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
2024-06-28T17:03:45.739Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
2024-06-28T17:03:45.754Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command close executed for 31 milliseconds with result 0
2024-06-28T17:03:45.754Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command close executed for 13 milliseconds with result 0
2024-06-28T17:03:45.754Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] terminate
2024-06-28T17:03:45.754Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command terminate executed for 0 milliseconds with result 0
2024-06-28T17:03:45.769Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
2024-06-28T17:03:45.769Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 18 milliseconds
2024-06-28T17:03:45.803Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-28T17:03:45.804Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-28T17:03:45.805Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
2024-06-28T17:03:45.805Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Executed 4 commands for 97 milliseconds
2024-06-28T17:03:45.805Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] terminate
2024-06-28T17:03:45.821Z VERBOSE [PID:25064] [boardController] C API function: get_version_list
2024-06-28T17:03:45.821Z DEBUG [PID:25064] [boardController] Operation get_version_list failed with error code NRFDL_ERR_NOT_SUPPORTED
2024-06-28T17:03:45.821Z VERBOSE [PID:25064] DeviceLister::enumerate: Checking future_status of enumerate_task_status
2024-06-28T17:03:45.821Z VERBOSE [PID:25064] DeviceLister::enumerate: Waiting for enumerate task to complete
2024-06-28T17:03:45.821Z VERBOSE [PID:25064] DeviceLister::enumerate::enumerate_task: Start
2024-06-28T17:03:45.821Z VERBOSE [PID:25064] DeviceLister::enumerate::enumerate_task: Before async_lister->enumerate
2024-06-28T17:03:45.821Z DEBUG [PID:25064] USBLister: enumerate
2024-06-28T17:03:45.821Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_8087&PID_0026#5&1e40a320&0&14#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=14
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&21B670C1&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 14, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_8087&PID_0026#5&1e40a320&0&14#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_328F&PID_006D#A230630000114417#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=0BDA, pid=5411, port=3
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0BDA&PID_5411#6&1D8A9E0D&1&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {93DFF25E-7F96-55D7-867E-C0C699C40CBF}
2024-06-28T17:03:45.822Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.824Z DEBUG [PID:25064] USBPlatformAPI::Win32: serial number: A230630000114417
2024-06-28T17:03:45.824Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_328F&PID_006D#A230630000114417#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.824Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {93DFF25E-7F96-55D7-867E-C0C699C40CBF}
2024-06-28T17:03:45.824Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_046D&PID_C408#7&820cb10&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.825Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=0BDA, pid=5411, port=4
2024-06-28T17:03:45.825Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0BDA&PID_5411#6&1D8A9E0D&1&4#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 4, origin: {0A9615C7-0F78-11EF-AFA9-A4B1C1BA6BCE}
2024-06-28T17:03:45.825Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_046D&PID_C408#7&820cb10&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {0A9615C7-0F78-11EF-AFA9-A4B1C1BA6BCE}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_04F2&PID_B6BB#0001#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=6
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&21B670C1&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 6, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_04F2&PID_B6BB#0001#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_045E&PID_0048#7&4b312f8&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=0BDA, pid=5411, port=4
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0BDA&PID_5411#6&1D8A9E0D&1&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 4, origin: {78261D2D-8061-11EE-AF81-A4B1C1BA6BCE}
2024-06-28T17:03:45.827Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.830Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_045E&PID_0048#7&4b312f8&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.830Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {78261D2D-8061-11EE-AF81-A4B1C1BA6BCE}
2024-06-28T17:03:45.830Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_1366&PID_1051#001050203102#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.831Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=0BDA, pid=5411, port=1
2024-06-28T17:03:45.831Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0BDA&PID_5411#6&1D8A9E0D&1&3#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 1, origin: {49AA47CD-D7CC-5AA0-9DF9-5A132EC33008}
2024-06-28T17:03:45.831Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.831Z DEBUG [PID:25064] USBPlatformAPI::Win32: serial number: 001050203102
2024-06-28T17:03:45.831Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_1366&PID_1051#001050203102#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.831Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {49AA47CD-D7CC-5AA0-9DF9-5A132EC33008}
2024-06-28T17:03:45.831Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_046D&PID_0AAF#2103SG00AAS8_888-000313110306#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.832Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=0BDA, pid=5411, port=1
2024-06-28T17:03:45.832Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0BDA&PID_5411#6&1D8A9E0D&1&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 1, origin: {D200AB65-1AEA-52B0-899C-51AE551C18EE}
2024-06-28T17:03:45.832Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: serial number: 2103SG00AAS8_888-000313110306
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_046D&PID_0AAF#2103SG00AAS8_888-000313110306#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {D200AB65-1AEA-52B0-899C-51AE551C18EE}
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_0797&PID_7002#7&2d942c5a&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=0BDA, pid=5411, port=2
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0BDA&PID_5411#6&1D8A9E0D&1&2#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {6828FEA5-34B4-11EF-AFB1-A4B1C1BA6BCE}
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_0797&PID_7002#7&2d942c5a&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {6828FEA5-34B4-11EF-AFB1-A4B1C1BA6BCE}
2024-06-28T17:03:45.833Z DEBUG [PID:25064] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_1915&PID_53AB#F3CAA24A012CB708#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.834Z DEBUG [PID:25064] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=2
2024-06-28T17:03:45.834Z DEBUG [PID:25064] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&21B670C1&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {C905A651-E3EE-5759-97D4-08118B13A120}
2024-06-28T17:03:45.834Z DEBUG [PID:25064] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-28T17:03:45.834Z DEBUG [PID:25064] USBPlatformAPI::Win32: serial number: F3CAA24A012CB708
2024-06-28T17:03:45.834Z DEBUG [PID:25064] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_1915&PID_53AB#F3CAA24A012CB708#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:45.834Z DEBUG [PID:25064] USBPlatformAPI::Win32: containerID: {C905A651-E3EE-5759-97D4-08118B13A120}
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 1 and serial number: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 2 and serial number: 'A230630000114417'
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 3 and serial number: '{0A9615C7-0F78-11EF-AFA9-A4B1C1BA6BCE}'
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 4 and serial number: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 5 and serial number: '{78261D2D-8061-11EE-AF81-A4B1C1BA6BCE}'
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 6 and serial number: '{6828FEA5-34B4-11EF-AFB1-A4B1C1BA6BCE}'
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 7 and serial number: '001050203102'
2024-06-28T17:03:45.835Z DEBUG [PID:25064] USBLister: Adding new device with id 8 and serial number: '2103SG00AAS8_888-000313110306'
2024-06-28T17:03:45.836Z DEBUG [PID:25064] USBLister: Adding new device with id 9 and serial number: 'F3CAA24A012CB708'
2024-06-28T17:03:45.836Z VERBOSE [PID:25064] DeviceLister::enumerate::enumerate_task: After async_lister->enumerate
2024-06-28T17:03:45.836Z VERBOSE [PID:25064] [devkit] C API function: enumerate
2024-06-28T17:03:45.836Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 1
2024-06-28T17:03:45.837Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 2
2024-06-28T17:03:45.839Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 3
2024-06-28T17:03:45.840Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 4
2024-06-28T17:03:45.842Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 5
2024-06-28T17:03:45.843Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 6
2024-06-28T17:03:45.844Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 7
2024-06-28T17:03:45.844Z DEBUG [PID:25064] [devkit] enumerate: Device with ID 7 has board version PCA10056
2024-06-28T17:03:45.844Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 8
2024-06-28T17:03:45.845Z VERBOSE [PID:25064] [devkit] enumerate: Inspecting device with ID 9
2024-06-28T17:03:45.847Z DEBUG [PID:25064] Enumeration for plugin 'devkit' took 11 ms
2024-06-28T17:03:45.847Z VERBOSE [PID:25064] [jlink] JLinkPlugin::enumerate
2024-06-28T17:03:45.957Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] open
2024-06-28T17:03:45.957Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] start
2024-06-28T17:03:45.991Z INFO Using nrfutil-device version: 2.1.1
2024-06-28T17:03:45.991Z INFO Using nrf-device-lib version: 0.17.5
2024-06-28T17:03:45.991Z INFO Using nrfjprog DLL version: 10.24.0
2024-06-28T17:03:45.991Z INFO Using JLink version: JLink_V7.94e
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
2024-06-28T17:03:46.004Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command open executed for 42 milliseconds with result 0
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] open
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] enum_emu_snr
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] just_check_family
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] open_dll
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
2024-06-28T17:03:46.004Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
2024-06-28T17:03:46.005Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] dll_version
2024-06-28T17:03:46.005Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command open executed for 4 milliseconds with result 0
2024-06-28T17:03:46.020Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command enum_emu_snr executed for 15 milliseconds with result 0
2024-06-28T17:03:46.020Z DEBUG [PID:25064] [jlink] Found 1 JLink devices connected
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] enum_emu_snr
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] enum_emu_snr
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] ---just_enum_emu_snr
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] ---just_get_num_emus
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:46.036Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command enum_emu_snr executed for 4 milliseconds with result 0
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] close
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] close
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
2024-06-28T17:03:46.036Z DEBUG [PID:25064] [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
2024-06-28T17:03:46.051Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command close executed for 13 milliseconds with result 0
2024-06-28T17:03:46.051Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command close executed for 30 milliseconds with result 0
2024-06-28T17:03:46.051Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] terminate
2024-06-28T17:03:46.051Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Command terminate executed for 0 milliseconds with result 0
2024-06-28T17:03:46.066Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
2024-06-28T17:03:46.067Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 21 milliseconds
2024-06-28T17:03:46.099Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-28T17:03:46.099Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-28T17:03:46.100Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
2024-06-28T17:03:46.100Z VERBOSE [PID:25064] [jlink] [NRFJPROG][Client][-] Executed 4 commands for 87 milliseconds
2024-06-28T17:03:46.100Z DEBUG [PID:25064] [jlink] [NRFJPROG][Client][-] terminate
2024-06-28T17:03:46.116Z DEBUG [PID:25064] Enumeration for plugin 'jlink' took 268 ms
2024-06-28T17:03:46.116Z VERBOSE [PID:25064] [boardController] C API function: enumerate
2024-06-28T17:03:46.233Z DEBUG [PID:25064] [boardController] Found 15 HID devices.
2024-06-28T17:03:46.233Z DEBUG [PID:25064] Enumeration for plugin 'BOARDCONTROLLER' took 116 ms
2024-06-28T17:03:46.234Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Searching parent device for: \\?\USB#VID_1366&PID_1051&MI_00#8&29FABED8&0&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2024-06-28T17:03:46.234Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device: USB\VID_1366&PID_1051\001050203102
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device has 1 interfaces:
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] - \\?\USB#VID_1366&PID_1051#001050203102#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] serial port \\?\USB#VID_1366&PID_1051&MI_00#8&29FABED8&0&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1366&PID_1051#001050203102#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Searching parent device for: \\?\USB#VID_1366&PID_1051&MI_02#8&29FABED8&0&0002#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device: USB\VID_1366&PID_1051\001050203102
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device has 1 interfaces:
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] - \\?\USB#VID_1366&PID_1051#001050203102#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:46.235Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] serial port \\?\USB#VID_1366&PID_1051&MI_02#8&29FABED8&0&0002#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1366&PID_1051#001050203102#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
2024-06-28T17:03:46.236Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Searching parent device for: \\?\USB#VID_1915&PID_53AB&MI_03#8&36D0DB8A&1&0003#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2024-06-28T17:03:46.236Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device: USB\VID_1915&PID_53AB\F3CAA24A012CB708
2024-06-28T17:03:46.236Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device has 1 interfaces:
2024-06-28T17:03:46.236Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] - \\?\USB#VID_1915&PID_53AB#F3CAA24A012CB708#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:46.236Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] serial port \\?\USB#VID_1915&PID_53AB&MI_03#8&36D0DB8A&1&0003#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1915&PID_53AB#F3CAA24A012CB708#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
2024-06-28T17:03:46.236Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Searching parent device for: \\?\USB#VID_1915&PID_53AB&MI_00#8&36D0DB8A&1&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2024-06-28T17:03:46.237Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device: USB\VID_1915&PID_53AB\F3CAA24A012CB708
2024-06-28T17:03:46.237Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] Parent device has 1 interfaces:
2024-06-28T17:03:46.237Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] - \\?\USB#VID_1915&PID_53AB#F3CAA24A012CB708#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-28T17:03:46.237Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] serial port \\?\USB#VID_1915&PID_53AB&MI_00#8&36D0DB8A&1&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1915&PID_53AB#F3CAA24A012CB708#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
2024-06-28T17:03:46.237Z DEBUG [PID:25064] [SerialPortListerHW::WIN32] try to map FTDI to segger device
2024-06-28T17:03:46.237Z DEBUG [PID:25064] [serialport] serialport enumerate update device: '001050203102'
2024-06-28T17:03:46.237Z DEBUG [PID:25064] [serialport] serialport enumerate update device: 'F3CAA24A012CB708'
2024-06-28T17:03:46.237Z DEBUG [PID:25064] Enumeration for plugin 'serialport' took 3 ms
2024-06-28T17:03:46.237Z DEBUG [PID:25064] Enumeration for plugin 'sdfu' took 0 ms
2024-06-28T17:03:46.238Z DEBUG [PID:25064] Enumeration for plugin 'mcuBoot' took 0 ms
2024-06-28T17:03:46.238Z VERBOSE [PID:25064] [broken] BrokenPlugin::enumerate
2024-06-28T17:03:46.238Z DEBUG [PID:25064] Enumeration for plugin 'broken' took 0 ms
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: 'A230630000114417'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: '{0A9615C7-0F78-11EF-AFA9-A4B1C1BA6BCE}'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: '{78261D2D-8061-11EE-AF81-A4B1C1BA6BCE}'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: '{6828FEA5-34B4-11EF-AFB1-A4B1C1BA6BCE}'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: '001050203102'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: device registered to device list
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: '2103SG00AAS8_888-000313110306'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Found device with serial number: 'F3CAA24A012CB708'
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: device registered to device list
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Finished in 417 ms
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: Completed waiting for enumerate task
2024-06-28T17:03:46.239Z VERBOSE [PID:25064] DeviceLister::enumerate: done
2024-06-28T17:03:46.240Z INFO Device Connected SN:001050203102
2024-06-28T17:03:46.240Z INFO Getting serialport options from persistent store 001050203102.pc-nrfconnect-npm
2024-06-28T17:03:46.241Z INFO Device Connected SN:F3CAA24A012CB708
2024-06-28T17:03:46.242Z INFO Getting serialport options from persistent store F3CAA24A012CB708.pc-nrfconnect-npm
2024-06-28T17:03:48.037Z INFO Selected device with s/n F3CAA24A012CB708
2024-06-28T17:03:48.042Z INFO Opened port with options: {"path":"COM6","baudRate":115200}
2024-06-28T17:03:48.117Z INFO Closed port: COM6
2024-06-28T17:03:48.117Z INFO Device setup ready for device with s/n F3CAA24A012CB708
2024-06-28T17:03:48.120Z INFO Opened port with options: {"path":"COM6","baudRate":115200}
2024-06-28T17:03:48.336Z WARN module_pmic: No response from PMIC.
2024-06-28T17:03:48.348Z WARN module_pmic: No response from PMIC.
2024-06-28T17:03:48.355Z WARN module_pmic: No response from PMIC.
2024-06-28T17:03:48.363Z WARN module_pmic: No response from PMIC.
2024-06-28T17:03:48.373Z WARN module_pmic: No response from PMIC.
2024-06-28T17:03:48.380Z WARN module_pmic: No response from PMIC.
2024-06-28T17:03:48.389Z WARN module_pmic: No response from PMIC.
2024-06-28T17:03:52.826Z WARN module_pmic: No response from PMIC.

[Kazi Afroza Sultana]

Hello,

If you get toggling on an off light that means it is incorrectly powered. Check if PMIC has power, or power cycle nPM Controller. You can try with different cable also.

Which version of nPM1300 EK you are using?

Thanks.

BR

Kazi

[mej7000]

nPM1300ek version: 0.9.0

I'm getting VBUS: 5v,  VBUSOUT: 0.7v Is there something specific you would like me to voltage test?

I already tried multiple power sources and have recycled:  I have both "nPM Controller" and "USB PMC" USB connected. I tried powering USB PMC through the computer and also tried a "Wall Wart USB".

I have tried multiple longer and shorter cables 

I have not made any connections to the nrf52840dk board, but I don't believe a dk board is necessary to evaluate the nPM1300ek. youtu.be/PZqxVZsbqWI

I jumped NTC to 10k as my Battery does not have NTC. I tried it with and without a battery connected.

The only LED that is toggling is the one associated with the host (LD4). I get nothing from LD1, LD2, LD3:  No LEDs to light when I plug in USB PMC, but I don't know if an LED is supposed to light. I get a flashing LED (near the nPM Controller USB port) when nPM Controller is USB plugged in.

[dacr]

Can you measure VOUT2? PMIC needs VDDIO (connected to VOUT2 in your setup) to communicate.

[mej7000]

currently VOUT2 = 0.5v
are so saying to jumper VDDIO(P11) to VOUT2(P15)?

[dacr]

You already have the jumper.

Can you confirm what you have on VSYS? But already, with VBUSOUT=0.7V, and VOUT2=0.5V, and VBUS=5V it looks like the PMIC might be damaged.

[mej7000]

I do have the jumper there already... I will order another one.

I was thinking it just wasn't working, so I had a colleague order one and test it independently... She can't get hers to connect at all. If you have any insight there it would also be appreciated! Thanks, mike

devzone.nordicsemi.com/.../npm1300-won-t-connect-to-computer

[dacr]

Can you try disconnecting the battery, and only have the 2 USB cables as power supply?

[mej7000]

ya, that's how I have been doing it... I noticed the board get very hot at some point (can't remember if the battery was connected or not) but it didn't seem normal.

Also I get no LED lit on the PMIC side, which seems weird to me. Should at least one of those be lit?