I understand that and I have the switches set the correct way but the board does not seem to enter serial downloader mode as I said in the previous reply. Why is that?
I do have the switches set to:
SW1: 0001 SW2:0000000000.
I have disconnected all power and restarted the board multiple times but the board still does not seem to enter Serial download mode correctly. What is causing this?
When connecting my serial monitor to the usb debug it does connect but the board keeps printing dots like this:
Serial monitor prints:
............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
It looks like the board is restarting over and over, or what’s happening?
When trying to debug an example project from the MCUXpresso I get this error:
LinkServer RedlinkMulti Driver v24.12 (Dec 18 2024 19:35:47 - crt_emu_cm_redlink build 869)
Found chip XML file in /Users/melker/Documents/MCUXpressoIDE_24.12.148/workspace/evkbmimxrt1170_hello_world_primary_core/Debug/MIMXRT1176xxxxx.xml
Reconnected to existing LinkServer process.
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to existing LinkServer process.
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
============= SCRIPT: RT1170_connect_M7_wake_M4.scp =============
RT1170 Connect M7 and Wake M4 Script
Error: Wire Ack Fault - target connected?
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Setting M4 spin code
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Setting M4 clock
Error: Wire not connected
Resetting M4 core
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
View cores on the DAP AP
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire not connected
Error: Wire not connected
============= END SCRIPT ========================================
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
When trying to flash using uart in provisioning tool:
Executing script /Users/melker/secure_provisioning0/gen_scripts/init_flashloader_mac.sh
ERROR: Script failed with return code: [2]ERROR
### SCRIPT: Starting flashloader: /Users/melker/secure_provisioning0/gen_scripts/init_flashloader_mac.sh
### Parse input arguments ###
### Check presence of FlashLoader ###
### FlashLoader is not running yet, download and run it ###
### Check communication with target bootloader ###
/Applications/MCUX_Provi_25.03/MCUXpresso Secure Provisioning 25.03.app/Contents/Frameworks/tools/spsdk /Applications/MCUX_Provi_25.03
/Applications/MCUX_Provi_25.03/MCUXpresso Secure Provisioning 25.03.app/Contents/Frameworks/tools/spsdk/blhost -t 2000 -p /dev/cu.usbmodem1PUQXTTDF5B0Y3,115200 -- get-property 17 0
SpsdkNoDeviceFoundError: No devices for given interface 'uart' and parameters 'port=/dev/cu.usbmodem1PUQXTTDF5B0Y3, baudrate=115200, timeout=2000' was found.
/Applications/MCUX_Provi_25.03
blhost failed
### RESULT of the script `Starting flashloader`: Failure (return code = [2]ERROR)
Status of the operation: Failure: Starting flashloader
ERROR: Write failed: Failed to start the flashloader
Status of the operation: Failure: Write failed: Failed to start the flashloader
In MCUXpresso Secure Provisioning tool the uart port for the debug USB on the board shows up but it's not possible to flash or do a mass erase. Connecting to USB J20 does not work either and the board is not found at all using the usb option.
The problem seem to be that the serial downloader mode is not entered when setting the switches accordingly, how can I fix this or get around the problem to get the board to accept new firmware or a mass erase?
Attaching screenshots of errors in mcu provisioning tool.