How to recovery RW612 from wrong FW download process

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

How to recovery RW612 from wrong FW download process

164 Views
BeiBei
Contributor I

Hi, NXP team

Recently, I‘m doing a test on Murata 2FR with A0 version RW612 chipset. I'd like to use labtool "MFG-RW610-MF-BRG-U16-WIN-X86-1.0.0.11.0-18.80.2.p32.2 3" to test Wi-Fi function, I modified the FW with internal flash config. Firstly I downloaded successfully, but cannot communicate with labtool properly. When I re-download fw with .bat, it shows error. After that, I can connect RW612 with J-link but cannot erase or program it. below is the log of J-link. Can you help to look at it?

 

---------------------------------------------------------------------------------------------------------------------------

Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link V9 compiled May 7 2021 16:26:12
- Probe/ Programmer S/N: 69603352
- Device "RW612" selected.
- Target interface speed: 4000 kHz (Fixed)
- VTarget = 3.303V
- InitTarget() start
- SWD selected. Executing JTAG -> SWD switching sequence.
- DAP initialized successfully.
- DMAP_REG_ID: DM-AP IDCODE detected: 0x002A0000
- DHCSR: 0x07100000
- InitTarget() end - Took 8.45ms
- Found SW-DP with ID 0x6BA02477
- DPIDR: 0x6BA02477
- CoreSight SoC-400 or earlier
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x84770001)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Core found
- AP[0]: AHB-AP ROM base: 0xE00FF000
- CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
- Feature set: Mainline
- Cache: No cache
- Found Cortex-M33 r0p4, Little endian.
- Cortex-M (ARMv8-M and later): The connected J-Link (S/N 69603352) uses an old firmware module that does not handle I/D-cache correctly. Proper debugging functionality cannot be guaranteed if cache is enabled
- FPUnit: 8 code (BP) slots and 0 literal slots
- Security extension: implemented
- Secure debug: enabled
- CoreSight components:
- ROMTbl[0] @ E00FF000
- [0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
- [0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
- [0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
- [0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
- [0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
- [0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
- Executing init sequence ...
- Initialized successfully
- Target interface speed: 4000 kHz (Fixed)
- Found 1 JTAG device. Core ID: 0x6BA02477 (None)
- Connected successfully
Opening data file [C:\Users\h485324\Desktop\A0\FwImage\A0\uart_wifi_ble_15_4_bridge.bin] ...
- Data file opened successfully (46390 bytes, 1 range, CRC of data = 0x5E5D7AFC, CRC of file = 0x5E5D7AFC)
Auto programming target (46390 bytes, 1 range) ...
- Checking if selected data fits into selected flash sectors.
- Start of determining flash info (Bank 0 @ 0x08000000)
- ERROR: Timeout while preparing target, RAMCode did not respond in time!
- ERROR: Failed to perform RAMCode-sided Prepare()
- ERROR: Error while determining flash info (Bank 0 @ 0x08000000)
- ERROR: Failed to auto program target
Disconnecting ...
- Disconnected

Labels (1)
0 Kudos
0 Replies