Skip to content

Add support for INT8 classification models - #38

Open
Jithendar11 wants to merge 2 commits into
Arm-Examples:mainfrom
Jithendar11:br_int8_model_support
Open

Jithendar11 wants to merge 2 commits into
Arm-Examples:mainfrom
Jithendar11:br_int8_model_support

Conversation

@Jithendar11

Copy link
Copy Markdown
Contributor
  • Add CIL library for INT8 model pre-processing and post-processing
  • Add INT8 model_pte header file
  • Add INT8 model report file

- Add CIL library for INT8 model pre-processing and post-processing
- Add INT8 model_pte header file
- Add INT8 model report file
@Jithendar11
Jithendar11 marked this pull request as ready for review September 29, 2026 05:21
// <i> Defines size of RTSS HP application memory region.
// <i> Default: 0x00200000
#define APP_MRAM_HP_SIZE 0x00200000
#define APP_MRAM_HP_SIZE 0x00400000

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Setting 0x00400000 would exceed the available MRAM size as MRAM size is 5.5 MB.
Since 0x00200000 is reserved for HE core it leaves the maximum of 0x00380000 for the HP core.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing this out. We increased this because some models have larger generated model/weight data and the previous HP MRAM allocation was not sufficient.

In this application we are not using the HE core, but I agree that with the current memory map APP_MRAM_HP_BASE starts after the HE-reserved 0x00200000 region, so setting HP size to 0x00400000 would exceed the available 5.5 MB MRAM range.

Updated APP_MRAM_HP_SIZE to 0x00380000, which is the maximum valid HP size with the current base address and HE reservation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants