파일을 올리기 전에
EL 이라고 써있는 External Loaders를 선택해서
stm32h747로 검색하면 나오는 보드가 있는데 해당 보드를 선택후 플래시를 진행하면 정상적으로 구워진다.
플래시를 활성화할수 있는 코드를 external loader에서 실행해주는 것 같고
로더가 먼저 실행된 후 내부 플래시와 외부 NOR flash에 구워지는 것으로 보인다.
757(보안 모듈 있음) 747(보안모듈 없음) 차이므로 보드가 다르다고 하더라도 문제는 없을듯 하다.
| STM32 / no MCU device found (0) | 2024.09.04 |
|---|---|
| STM32CubeIDE alt func (0) | 2024.09.03 |
| stm32cubeide 빌드할 소스 추가하기 (0) | 2024.08.01 |
| STM32H75I-EVAL (0) | 2024.08.01 |
| stm32cubeide 펌웨어 업데이트 이후 자동 재시작 (0) | 2024.07.25 |
core 쪽은 추가하면 바로 빌드되는데
별도의 디렉토리를 추가하고 소스를 넣으면 빌드가 자동으로 안된다.
includes 탭은 include 파일/디렉토리를 추가하고
Source Location 에는 소스 파일/디렉토리를 추가하면 된다.
[링크 : https://mokhwasomssi.tistory.com/198]
드디어 에러가 발생한다아!!!! 만세!!
| STM32CubeIDE alt func (0) | 2024.09.03 |
|---|---|
| stm32h757i-eval 데모 펌웨어 굽기 (0) | 2024.08.07 |
| STM32H75I-EVAL (0) | 2024.08.01 |
| stm32cubeide 펌웨어 업데이트 이후 자동 재시작 (0) | 2024.07.25 |
| stm32cubeide(eclipse) project clean시 빌드 하지 않기 (0) | 2024.07.24 |
한번 새로 프로젝트 만들려고 해보는데
어...라... STM32H7로 검색하니 750까지만 공개(?)되어 있고, 757은 안나온다.
그래서 홈페이지 가서 뒤져보니 데모용 바이너리는 존재한다. 이거 소스는 못 받나?
[링크 : https://www.st.com/en/evaluation-tools/stm32h757i-eval.html#tools-software]
| stm32h757i-eval 데모 펌웨어 굽기 (0) | 2024.08.07 |
|---|---|
| stm32cubeide 빌드할 소스 추가하기 (0) | 2024.08.01 |
| stm32cubeide 펌웨어 업데이트 이후 자동 재시작 (0) | 2024.07.25 |
| stm32cubeide(eclipse) project clean시 빌드 하지 않기 (0) | 2024.07.24 |
| 우분투에서 stm32cubeide 삭제 (0) | 2024.07.24 |
자동 재시작이 안되서 이상하다 싶어 보는데
Reset behavior에 "Connect under reset"이 되어있으면 펌웨어 업데이트 이후 리셋을 눌러줘야 재기동하고
"Software system reset"을 하면 펌웨어 업데이트 이후 자동으로 재시작 된다.
Halt all cores가 체크 가능한건 두 개 뿐이네..
| stm32cubeide 빌드할 소스 추가하기 (0) | 2024.08.01 |
|---|---|
| STM32H75I-EVAL (0) | 2024.08.01 |
| stm32cubeide(eclipse) project clean시 빌드 하지 않기 (0) | 2024.07.24 |
| 우분투에서 stm32cubeide 삭제 (0) | 2024.07.24 |
| STM32H7 디버깅 설정(cubeIDE) (0) | 2024.07.22 |
아무생각없이 무지성으로 clean 하면 매번 빌드되서 짜증났는데
proejct 쪽 메뉴에서 preference 봐도 없길래
clean 메뉴를 다시 보니 가장 아래에
"Start a build immediately"에 체크가 되어있다.
아니.. clean 한다고 왜 빌드 바로 하라는 옵션이 있냐구요.. -_-
| STM32H75I-EVAL (0) | 2024.08.01 |
|---|---|
| stm32cubeide 펌웨어 업데이트 이후 자동 재시작 (0) | 2024.07.25 |
| 우분투에서 stm32cubeide 삭제 (0) | 2024.07.24 |
| STM32H7 디버깅 설정(cubeIDE) (0) | 2024.07.22 |
| STM32H750 operation mode (0) | 2024.07.22 |
버전을 넣어서 삭제하면 끝
| $ sudo apt purge segger-jlink-udev-rules st-stlink-server st-stlink-udev-rules st-stm32cubeide-1.5.0 |
[링크 : https://askubuntu.com/questions/1444347/uninstall-stm32cubeide]
| stm32cubeide 펌웨어 업데이트 이후 자동 재시작 (0) | 2024.07.25 |
|---|---|
| stm32cubeide(eclipse) project clean시 빌드 하지 않기 (0) | 2024.07.24 |
| STM32H7 디버깅 설정(cubeIDE) (0) | 2024.07.22 |
| STM32H750 operation mode (0) | 2024.07.22 |
| STM32 MPU(Memory Protection Unit) (0) | 2024.07.22 |
Halt all cores 를 체크해서
Cortex-M7을 멈추면 Cortex-M4 도 같이 멈추고
Cortex-M4 에는 Halt 옵션이 없으니 M7을 멈출수 없어서 M4만 멈췄나 보다.
| stm32cubeide(eclipse) project clean시 빌드 하지 않기 (0) | 2024.07.24 |
|---|---|
| 우분투에서 stm32cubeide 삭제 (0) | 2024.07.24 |
| STM32H750 operation mode (0) | 2024.07.22 |
| STM32 MPU(Memory Protection Unit) (0) | 2024.07.22 |
| STM32 HSEM (Hardware SEMaphore) (0) | 2024.07.22 |
소스를 뒤져보면서 메뉴얼 찾아보는 중
stm32h7xx_hal_pwr_ex.c 파일에 보면 D3Domain 이라고 PWR_CPUCR_RUN_D3 라고
d3 도메인의 cpu (cortex-m4)를 살리는 녀석으로 보인다.
| void HAL_PWREx_ConfigD3Domain (uint32_t D3State) { /* Check the parameter */ assert_param (IS_D3_STATE (D3State)); /* Keep D3/SRD in run mode */ MODIFY_REG (PWR->CPUCR, PWR_CPUCR_RUN_D3, D3State); } |
| /******************** Bit definition for PWR_CPUCR register *****************/ #define PWR_CPUCR_RUN_D3_Pos (11U) #define PWR_CPUCR_RUN_D3_Msk (0x1UL << PWR_CPUCR_RUN_D3_Pos) /*!< 0x00000800 */ #define PWR_CPUCR_RUN_D3 PWR_CPUCR_RUN_D3_Msk /*!< Keep system D3 domain in RUN mode regardless of the CPU sub-systems modes */ /******************** Bit definition for PWR_CPU2CR register ****************/ #define PWR_CPU2CR_RUN_D3_Pos (11U) #define PWR_CPU2CR_RUN_D3_Msk (0x1UL << PWR_CPU2CR_RUN_D3_Pos) /*!< 0x00000800 */ #define PWR_CPU2CR_RUN_D3 PWR_CPU2CR_RUN_D3_Msk /*!< Keep system D3 domain in RUN mode regardless of the CPU sub-systems modes */ |
stm32h757xi.pdf 데이터 시트 31page
어.. D2 domain에 Cortex-M4 였네..
rm0399-stm32h745755-and-stm32h747757-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
| 7.6.1 Operating modes Several system operating modes are available to tune the system according to the performance required, i.e. when the CPU(s) do not need to execute code and are waiting for an external event. It is up to the user to select the operating mode that gives the best compromise between low power consumption, short startup time and available wakeup sources. The operating modes allow controlling the clock distribution to the different system blocks and powering them. The system operating mode is driven by CPU1 subsystem, CPU2 subsystem and system D3 autonomous wakeup. A CPU subsystem can include multiple domains depending on its peripheral allocation (see Section 9.5.11: Peripheral clock gating control). The following operating modes are available for the different system blocks (see Table 34): • CPU subsystem modes: – CRun CPU and CPU subsystem peripheral allocated via RCC PERxEN bits are clocked. – CSleep: The CPU clocks is stalled and the CPU subsystem allocated peripheral(s) clock operate according to RCC PERxLPEN. – CStop: CPU and CPU subsystem peripheral clocks are stalled. • D1 domain and D2 domain modes: – DRun The domain bus matrix is clocked: - The domain CPU subsystem(a) is in CRun or CSleep mode, or - the other domain CPU subsystem(a) having an allocated peripheral in the domain is in CRun or CSleep mode. – DStop The domain bus matrix clock is stalled: - The domain CPU subsystem is in CStop mode and - The other domain CPU subsystem has no peripheral allocated in the domain. or the other domain CPU subsystem having an allocated peripheral in the domain is also in CStop mode and - At least one PDDS_Dn(b) bit for the domain select DStop. – DStandby The domain is powered down: - The domain CPU subsystem is in CStop mode and - The other domain CPU subsystem has no peripheral allocated in the domain or the other domain CPU subsystem having an allocated peripheral in the domain is also in CStop mode and - All PDDS_Dn(b) bits for the domain select DStandby mode. • System /D3 domain modes – Run/Run* The system clock and D3 domain bus matrix clock are running: - A CPU subsystem is in CRun or CSleep mode or - A wakeup signal is active. (i.e. System D3 autonomous mode) The Run* mode is entered after a POR reset and a wakeup from Standby. In Run* mode, the performance is limited and the system supply configuration shall be programmed in PWR control register 3 (PWR_CR3). The system enters Run mode only when the ACTVOSRDY bit in PWR control status register 1 (PWR_CSR1) is set to 1. – Stop The system clock and D3 domain bus matrix clock is stalled: - both CPU subsystems are in CStop mode. and - all wakeup signals are inactive. and - At least one PDDS_Dn(b) bit for any domain select Stop mode. – Standby The system is powered down: - both CPU subsystems are in CStop mode and - all wakeup signals are inactive. and - All PDDS_Dn(b) bits for all domains select Standby mode. In Run mode, power consumption can be reduced by one of the following means: •Lowering the system performance by slowing down the system clocks and reducing the VCORE supply level through VOS voltage scaling bits. •Gating the clocks to the APBx and AHBx peripherals when they are not used, through PERxEN bits. a. The domain CPU subsystem, for example CPU1 subsystem for D1 domain. a. The other domain CPU subsystem, for example CPU1 subsystem for D2 domain. |
| 9 Reset and Clock Control (RCC) The RCC block manages the clock and reset generation for the whole microcontroller, which embeds two CPUs: an Arm® Cortex®-M7 and an Arm® Cortex®-M4, called CPU1 and CPU2, respectively. The RCC block is located in the D3 domain (refer to Section 7: Power control (PWR) for a detailed description). The operating modes this section refers to are defined in Section 7.6.1: Operating modes of the PWR block. |
cpu1 power 용
cpu2 power 용. 서로 접근하면 되나?
| 우분투에서 stm32cubeide 삭제 (0) | 2024.07.24 |
|---|---|
| STM32H7 디버깅 설정(cubeIDE) (0) | 2024.07.22 |
| STM32 MPU(Memory Protection Unit) (0) | 2024.07.22 |
| STM32 HSEM (Hardware SEMaphore) (0) | 2024.07.22 |
| STM32H757 User configuration (0) | 2024.07.22 |
MMU 처럼 메모리 관리하는건 아니고, 메모리 접근을 관리하는 녀석인듯.
| This application note describes how to manage the memory protection unit (MPU) in the STM32 products The MPU is an optional component for the memory protection. Including the MPU in the STM32 microcontrollers (MCUs) makes them more robust and reliable. The MPU must be programmed and enabled before using it. If the MPU is not enabled, there is no change in the memory system behavior. This application note concerns all the STM32 products listed in Table 1 that include the Cortex®-M0+/M3/M4 and M7 design that supports the MPU. For more details about the MPU, refer to the following documents available on http://www.st.com • Programming manual STM32F7 series and STM32H7 series Cortex®-M7 processor (PM0253) • Programming manual STM32F10xxx/20xxx/21xxx/L1xxxx Cortex®-M3 (PM0056) • Programming manual STM32 Cortex®-M0+ MCUs programming manual (PM0223) • Programming manual STM32 Cortex®-M4 MCUs and MPUs (PM0214) • Programming manual STM32 Cortex®-M33 MCUs (PM0264) Table 1. Applicable products Type Product series Microcontrollers • STM32C0 series • STM32F1 series, STM32F2 series, STM32F3 series, STM32F4 series, STM32F7 series • STM32G0 series, STM32G4 series • STM32H5 series, STM32H7 series • STM32L0 series, STM32L1 series, STM32L4 series, STM32L4+ series, STM32L5 series • STM32U0 series, STM32U5 series • STM32WB series, STM32WB0 series |
MPU는 2개 있고, 각각의 CPU에 대해서 메모리 접근을 확인한다고.
꽤 중요한 녀석인데 데이터시트에 고작 아래의 내용이 전부냐?!
| 3.2 Memory protection unit (MPU) The devices feature two memory protection units. Each MPU manages the CPU access rights and the attributes of the system resources. It has to be programmed and enabled before use. Its main purposes are to prevent an untrusted user program to accidentally corrupt data used by the OS and/or by a privileged task, but also to protect data processes or read-protect memory regions. The MPU defines access rules for privileged accesses and user program accesses. It allows defining up to 16 protected regions that can in turn be divided into up to 8 independent subregions, where region address, size, and attributes can be configured. The protection area ranges from 32 bytes to 4 Gbytes of addressable memory. When an unauthorized access is performed, a memory management exception is generated. |
[링크 : https://www.st.com/resource/en/datasheet/stm32h757ai.pdf]
| STM32H7 디버깅 설정(cubeIDE) (0) | 2024.07.22 |
|---|---|
| STM32H750 operation mode (0) | 2024.07.22 |
| STM32 HSEM (Hardware SEMaphore) (0) | 2024.07.22 |
| STM32H757 User configuration (0) | 2024.07.22 |
| STM32CubeProgrammer (0) | 2024.07.22 |
multi CPU를 위한 하드웨어 세마포어 인듯.
그러니까.. 싱글 코어이거나, 이기종 CPU가 아니라면 달려있는 이유가 없는 모듈
[링크 : https://www.st.com/resource/en/product_training/STM32WB-System-Hardware-Semaphore-HSEM.pdf]
| STM32H750 operation mode (0) | 2024.07.22 |
|---|---|
| STM32 MPU(Memory Protection Unit) (0) | 2024.07.22 |
| STM32H757 User configuration (0) | 2024.07.22 |
| STM32CubeProgrammer (0) | 2024.07.22 |
| stm32h757xi / stm32h757i-eval (0) | 2024.07.19 |
|
