Permission Control functionalities esp32s3 (IDFGH-14747) #15486
Labels
Comments
github-actions
bot
changed the title
|
Hi @plamendc ,
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Answers checklist.
IDF version.
5.0.7
Espressif SoC revision.
esp32s3
Operating System used.
Windows
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
CMD
Development Kit.
esp32s3
Power Supply used.
USB
What is the expected behavior?
I am trying to implement a memory protection functionally for my project. I have several partitions: SSBL, factory and application. During normal operation the code first goes into SSBL than boots the factory/application.
What is the actual behavior?
It works like that, but when I try to implement the PMS functionality to select partitions and set access control for each of them, I can't boot any partition following SSBL. The memory protection algorithm is located in my SSBL.
Steps to reproduce.
This is my SSBL code:
/*
We arrive here after the ROM bootloader finished loading this second stage bootloader from flash.
The hardware is mostly uninitialized, flash cache is down and the app CPU is in reset.
We do have a stack, so we can do the initialization in C.
/
void attribute((noreturn)) call_start_cpu0(void)
{
tReprogFlag pReprogFlag = (tReprogFlag*) REPROGRAMMING_STRUCT_BASE_ADDR;
esp_image_metadata_t img_meta;
uint32_t calculatedCrcValue = 0;
bool noMainApp = false;
bool verifiedFAC = false;
bool verifiedOTA[2] = {false, false};
/* 1. Hardware initialization */
if (bootloader_init() != ESP_OK) {
bootloader_reset();
}
#ifdef CONFIG_BOOTLOADER_SKIP_VALIDATE_IN_DEEP_SLEEP
// If this boot is a wake up from the deep sleep then go to the short way,
// try to load the application which worked before deep sleep.
// It skips a lot of checks due to it was done before (while first boot).
bootloader_utility_load_boot_image_from_deep_sleep();
// If it is not successful try to load an application as usual.
#endif
}
My hal driver for PMS:
/**
*/
#ifdef __cplusplus
extern "C"
{
#endif
//
/***************** Inclusions **************************/
//
#include <stdint.h>
#include <stdio.h>
#include <string.h>
#include <inttypes.h>
#include "esp_log.h"
#include "HAL_MEM_PROTECT.h"
/************************/
/***************** Local Macros /
//
//write value to register
#define REG_WRITE(_r, _v) do {
(*(volatile uint32_t *)(_r)) = (_v);
} while(0)
//read value from register
#define REG_READ(_r) ({
(*(volatile uint32_t *)(_r));
})
// Correct SYSCON Base Address for Flash
#define SYSCON_BASE 0x60026000
// Flash ACE Registers
#define FLASH_ACE_ATTR_REG(n) (SYSCON_BASE + 0x0028 + (4 * (n))) // Flash ACE Permission Config Register
#define FLASH_ACE_ADDR_REG(n) (SYSCON_BASE + 0x0038 + (4 * (n))) // Flash ACE Starting Address Config Register
#define FLASH_ACE_SIZE_REG(n) (SYSCON_BASE + 0x0048 + (4 * (n))) // Flash ACE Length Config Register
// Define Access Control Attributes (Readable Names for Bits)
#define ATTR_SECURE_READ_ONLY (0b010 << 0) // Secure World: Read-only (W=0, R=1, X=1)
#define ATTR_NON_SECURE_READ_ONLY (0b010 << 3) // Non-Secure World: Read-only (W=0, R=1, X=1)
#define ATTR_SPI1_READ_ONLY (0b01 << 6) // SPI1: Read-only (W=0, R=1)
#define ATTR_FULL_ACCESS (0b11111111) // Full Access (W=1, R=1, X=1)
/*************************/
/***************** Local types /
//
// Memory Map Configuration Macros
#define SSBL_START_ADDR 0x00000000
#define SSBL_SIZE 1 // (48 * 1024) // 48KB
#define OTA_0_START_ADDR 0x00020000
#define OTA_0_SIZE 45 // (3072 * 1024) // 3072KB
#define OTA_1_START_ADDR 0x0312000
#define OTA_1_SIZE 45 // (3072 * 1024) // 3072KB
#define FACTORY_START_ADDR 0x00620000
#define FACTORY_SIZE 15 // (1024 * 1024) // 1024KB
#define PROD_START_ADDR 0x00710000
#define PROD_SIZE 1 // (4 * 1024) // 4KB
// Constants for Active OTA Selection
#define OTA_0_ACTIVE 0
#define OTA_1_ACTIVE 1
/*************************/
/***************** Local types /
//
// Enum for Memory Regions
enum {
SSBL = 0,
OTA_0,
OTA_1,
FACTORY,
PROD,
NUM_REGIONS // Total number of regions
};
// Memory map structure
typedef struct {
uint32_t start_address; // Starting address of the memory region
uint32_t size; // Size of the memory region
} memory_region_t;
/*********************/
/***************** Local variables /
//
// Memory regions defined using macros
const memory_region_t memory_regions[NUM_REGIONS] = {
{SSBL_START_ADDR, SSBL_SIZE}, // SSBL
{OTA_0_START_ADDR, OTA_0_SIZE}, // OTA_0
{OTA_1_START_ADDR, OTA_1_SIZE}, // OTA_1
{FACTORY_START_ADDR, FACTORY_SIZE}, // Factory
{PROD_START_ADDR, PROD_SIZE} // Prod
};
uint8_t counter = 0;
//
/ Local function declarations /
//
//
/***************** Interface functions *****************/
//
// Configures the Flash memory protection
void hal_mem_protect_enable(int active_ota) {
// Iterate through all memory regions
for (int i = 0; i < NUM_REGIONS; i++) {
}
// Enables full access for either SSBL or Factory region
void enable_full_access(int region) {
if (region != SSBL && region != FACTORY) {
ESP_LOGE("PCU", "Invalid region specified. Only SSBL or Factory can be set to full access.");
return;
}
}
//
/ Local function definitions **************/
/*************/
#ifdef __cplusplus
} /* end of extern "C" */
#endif
You can see that I have selected the partitions starting addresses, their size and the access control.
Even if set the access control is set to full access, I can't boot my bootloader or application. Please take a look at the logs.
Debug Logs.
More Information.
I followed the specifications specified in section 15.5 in this document: https://www.espressif.com/sites/default/files/documentation/esp32-s3_technical_reference_manual_en.pdf
The whole idea was to implement memory protection that while I am in one partition in the code, to disable unwanted access to the other partitions. Perhaps, I am doing something wrong during the configuration of the PMS or perhaps, this functionality is not applicable for my use case.
Also, because some of the segments I want to protect are shorter than 64k, which is the shortest segment fraction, I was wondering whether I can have overlapping memory segments in terms of PMS?
The text was updated successfully, but these errors were encountered: