Hi Sir,
Can anyone help me with my serious trouble?
My 1st FMUK66E was bricked with the same issue. I paid my 2nd one again, but it met this problem again!
I extremely carefully followed the guide: https://nxp.gitbook.io/hovergames/developerguide/program-software-using-debugger.
and my bootloader.bin is downloaded here: https://github.com/PX4/PX4-Autopilot/blob/main/boards/nxp/fmuk66-e/extras/nxp_fmuk66-e_bootloader.bi...
I used right click and "save link as" to download the bin file to a folder.
The bin file size is as the attached JPG.
Here is my log.
========================================================
samhblee@samhblee-i9nb:~$ JLinkExe
SEGGER J-Link Commander V7.92o (Compiled Nov 8 2023 15:46:41)
DLL version V7.92o, compiled Nov 8 2023 15:46:18
Connecting to J-Link via USB...O.K.
Firmware: J-Link EDU Mini V1 compiled Oct 30 2023 16:27:48
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 00m 29s
S/N: 801034143
License(s): FlashBP, GDB
USB speed mode: Full speed (12 MBit/s)
VTref=3.299V
Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MK66FN2M0XXX18
Type '?' for selection dialog
Device>?
MKPlease specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MK66FN2M0XXX18" selected.
Connecting to target via SWD
InitTarget()
SWD selected. Executing JTAG -> SWD switching sequence.
Readout protection is set and mass erase is disabled. J-Link cannot unprotect the device.
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x001C0000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
[0][6]: E0042000 CID B105900D PID 003BB907 ETB
[0][7]: E0043000 CID B105900D PID 001BB908 CSTF
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>
==============================================================
Please help me!!
I cannot stop wondering why NXP's FMU behaved so weirdly for 2 weeks.....
