680 次查看
Contributor II

Hi everyone,

I have just received an MIMXRT1050 EVKB board and I have made the necessary modifications to use the EVKB QSPI flash.   I am running MCUXpressoIDE_10.2.0_759.  Once I programmed the QSPI flash with the manufacturing tool, I was able to load and debug images into flash.  However, the GUI flash tool does not seem to work properly due to not finding the flash file:

Executing flash operation 'Program' (Program file into flash: Bootloader.axf) - Mon Jun 11 07:55:13 CDT 2018
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v10.2 (May 10 2018 18:10:59 - crt_emu_cm_redlink.exe build 510)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/cygwin64/home/mwhite/ImxIntegration/Bootloader/Debug\MIMXRT1052xxxxB.xml
( 5) Remote configuration complete
Reconnected to existing link server
Connecting to probe 1 core 0:0 (using server started externally) gave 'OK'
Probe Firmware: DAPLink CMSIS-DAP (ARM)
Serial Number: 0227000041114e450052300ac204002cdf91000097969900
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#8&348d8f4b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0:0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
debug interface type = Cortex-M7 (DAP DP ID 0BD11477) over SWD TAP 0
processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
number of h/w breakpoints = 8
number of flash patches = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 0BD11477. CpuID: 00000C27. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM dev (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM dev (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM dev (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C ChipIP dev SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 ChipIP dev DWT (type 0x0)

ROM 3 E0002000: CID B105E00D PID 04000BB00E ChipIP dev (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 ChipIP dev ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 ARCH 23B:4A13r0 CoreSight dev type 0x13 Trace Source - core
ROM 2 E0042000: CID B105900D PID 04004BB906 CoreSight dev type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0040000: CID B105900D PID 04000BB9A9 CoreSight dev type 0x11 Trace Sink - TPIU
ROM 1 E0043000: CID B105F00D PID 04001BB101 System dev (type 0x0)
Inspected v.2 External Flash Device on SPI MIMXRT1050-EVK_IS25WP064A.cfx
Image 'MIMXRT1050-EVK_IS25WP064A May 10 2018 18:22:04'
Opening flash driver MIMXRT1050-EVK_IS25WP064A.cfx
Sending VECTRESET to run flash driver
flash variant 'IS25WP064A' detected (8MB = 128*64K at 0x60000000)
Closing flash driver MIMXRT1050-EVK_IS25WP064A.cfx
Non-standard DAP stride detected - 1024 bytes
NXP: MIMXRT1052xxxxB
( 65) Chip Setup Complete
Connected: was_reset=false. was_stopped=false
( 70) License Check Complete
Cannot open ELF file 'Bootloader.axf': Cannot open ELF file for reading: No such file or directory
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

The file "Bootloader.axf" was selected using the "Workspace..." file selector.  The permissions on the file are wide open, i.e. anyone can read the file.  If I try to choose "Bootloader.axf" using "File System..." file selector, the file selector file filter stops me from choosing "Bootloader.axf" or any file except "axf" - not "whatever.axf", but "axf".  If I re-name "Bootloader.axf" to "axf" I can select the file "axf" but I get an error when programming:

Must set -load-base or --area with binary file

If I convert Bootloader.axf to a binary file, rename Bootloader.bin to "bin" (similar to axf, I'm only allowed to select a file named "bin"), only then can I successfully program the QSPI flash via the GUI flash tool.

This seems a bit of a convoluted way to program flash via GUI - what gives?  Is there a command line version that works?


0 项奖励
0 回复数