Error l6031u could not open scatter description file

Теги:  Программирование в Кин

Интеллектуальная рекомендация

Вам также может понравиться

[Keil] Learn the .sct file in keil

Recently, the source code of Acfly has been recreated. With a new interesting discovery, of course, the process is not interesting.

cause

CLONE down the code I submitted last year, compile …
😱 Erotic spicy!

linking...
.ObjectsACFly.axf: error: L6031U: Could not open scatter description file ACFly_Prophet.sct: No such file or directory

I found a solution on the Internet. I listened to the words on the CSDN, and I made a modification:

Before

After the change

Obviously, I deleted the LINKER configured in the original project directly, which is not a wise approach.

However, at the time I didn’t realize the seriousness of the problem, continue to operate, compile …
No wrong, but this encountered a very strange problem. I was getting stuck when I used DFU to burn, and then I was ready to re -burn the power. Yes, it is not initialized, and the corresponding COM port is not displayed on the ground station. It fails to directly fail when using DFU burning, and the USB cannot be detected.

DFU failed, I used Jlink to burn again, and the record was successful, but the flight control was still not initialized, like death.

Discovery loopholes

The Bootloader was re -burned, the flight control was successfully initialized, and my code was recorded again. The flight control still failed to initialize it.

At this time, I took a closer look at my only modification. Acfly_prophet.sct. At this time, I remembered the code IGNORE IGNORE I submitted last year, and the ACFLY_PROPHET.SCT is existing in it. I flip out of the ACFLY_PROPHET.SCT from the corner, add, compile, compile, burn, succeed.

What is SCT

The full name of SCT, scatter, is scattered. The .sct file is decentralized loading files. Diversifying loading files can define different positions through this script file. Where is the code, where the data is stored, which specific address is found to find the next function that needs to be run, and so on.

We all know that when the compiler generates executable files, compiles each .c file into a .o file (compiled this process), and then link many .o files to executable files (this process is called link) Essence During the link, a description file is used to specify the behavior when the link is specified. This description file is called link files, such as .ld files under Linux, decentralized loading files (.sct files) in keil.

The default, when compiling the program in the key, it will automatically generate the .sCT file (the default is in the directory of generating .o, .hex files).

Why do you specify SCT files here

Take a look at the SCT file of Acfly

; *************************************************************
; *** Scatter-Loading Description File generated by uVision ***
; *************************************************************

LR_IROM1 0x08100000 0x00100000  {    ; load region size_region
  ER_IROM1 0x08100000 0x00100000  {  ; load address = execution address
   *.o (RESET, +First)
   *(InRoot$$Sections)
   .ANY (+RO)
   .ANY (+XO)
  }
  
  DTCM_IRAM 0x20000000 0x00020000  {  ; RW data
	heap_4.o (+RW +ZI)
	queue.o (+RW +ZI)
	port.o (+RW +ZI)
	tasks.o (+RW +ZI)
	timers.o (+RW +ZI)
	cpu_load.o (+RW +ZI)
	.ANY (HEAP)
    .ANY (STACK)
   *(.DTCM)
  }
  RW_IRAM2 0x24000000 0x00070000  {
   .ANY (+RW +ZI)
   *(.AXI_RAM)
  }
  AXI_DMA_RAM 0x24070000  0x00010000  {  ; RW data
   *(.AXI_DMA_RAM)
  }
  SRAM1 0x30000000  0x00020000  {  ; RW data
   *(.SRAM1)
  }
}

LR_IROM2 0x08040000 0x000c0000  {    ; load region size_region
  RES_IROM 0x08040000 0x000c0000  {  ; load address = execution address
   *(.RES_IROM)
  }
}

Well, I really don’t understand this.

Acfly divides its programs into Bootloader programs and user programs.

A Bootloader program and a user program, then this requires adjusting the decentralized loading file to achieve the purpose of placing two different programs in a Flash at the same time.

Acfly_prophet.sct is a decentralized loading file written by pigs themselves. It is estimated that it is to make the Bootloader program and user programs not conflict.

Reference blog:
https://www.1024sou.com/article/919869.html

https://blog.csdn.net/qq_23274715/article/details/103445958