- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2064226_en-US
2064226_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2064226_en-US
2064226_en-US
Hi,
I'm working on a project use HSE APIs using S32K358.
My project requires multiple NVM keyslots.
Before using these keys, the key catalog must be formatted with requested key size, key type, key flags.
I can check those params using HSE_SRV_ID_GET_KEY_INFO service. But it returns zero for size, type, flags after key catalog formatted.
Is there any solution to check the current key catalog information?
Thanks a lot.
Understood.
It seems impossible to format only NVM key catalog.
Thanks.
I can't see such option. Service HSE_SRV_ID_FORMAT_KEY_CATALOGS obviously requires both pointers to hseKeyGroupCfgEntry_t structures (i.e. to NVM and RAM catalog) in hseFormatKeyCatalogsSrv_t.
But I can't see a reason to do that anyway. RAM catalog is empty after each reset, so it's not a big deal to reformat also RAM catalog. Just use the same configuration of RAM catalog when calling HSE_SRV_ID_FORMAT_KEY_CATALOGS.
Regards,
Lukas
Hi,
Is this possible to format only NVM key catalog?
Thanks.
Very clear for now.
Thanks a lot.
Yes, that's what I meant. There's no reason to have a service for this because the catalogs are statically configured and user should know the configuration.
"there no way to read key catalog information from previous software" - you are talking about development phase now. It's responsibility of user to know how the catalogs were formatted. Or the catalogs can be simply formatted again if needed during development.
But in the field, this is not an option - the catalogs can be formatted only in CUST_DEL life cycle. So, if you update the software in field, still the same catalogs must be used. There's no way to update the catalogs in OEM_PROD or IN_FILED life cycle.
Regards,
Lukas
Do you mean if the previous software has already formatted the key catalog with different length but not import the key, there no way to read key catalog information from previous software?
There's no such service which would allow you to read the catalog information. Service HSE_SRV_ID_GET_KEY_INFO works only for loaded keys, not for empty keys.
But because the catalogs are statically configured, you can simply read constant hseKeyGroupCfgEntry_t structures which you have already defined for catalog formatting. Or you can create own data structure (constant in flash) which will contain details about the catalogs and which you can read in runtime if needed.
Regards,
Lukas