Stm32 flash layout and access #16678
Replies: 4 comments 8 replies
-
The USB mass storage has access to a FAT32 formatted filesystem if you allow it by certain settings, e.g. in |
Beta Was this translation helpful? Give feedback.
-
Not sure if you really got my point. It's not about the mass storage. It's about splitting the mass storage into two parts like one which is acting like it is now fat32 fs accessible via USB and another part like two 16KB blocks only via direct flash read write NOT provided over USB so it can be locked with rop and not accessible outside the stm board. I can change the linker file to reduce the fs flash size but I'm unable to write the removed blocks afterwards. If you have some links please share |
Beta Was this translation helpful? Give feedback.
-
Seems like your problem is discussed and solved in the docs here (referring to section Hybrid (STM32). The solution in the docs above makes the FAT FS automatically accessible to e.g. Windows/Linux because the FAT FS with all drivers is available there by default. |
Beta Was this translation helpful? Give feedback.
-
OK for now disabling MSC is fine for my situation. |
Beta Was this translation helpful? Give feedback.
-
I'm trying to take some part from the flash_fs used by an f405 weact board away from the fs.
This is working by modifying the linker but how can I write the flash blocks afterwards?
The issue is that via pyb.Flash it seems that I can only access the blocks that are added to FLASH_FS. I can read the flash blocks by using mem8,16,32 but didn't find out how to write them.
The use behind is that I want to have some blocks of the internal flash that are read out protected and therefore are not allowed to.be part of the USB mass storage and just used internal.
Beta Was this translation helpful? Give feedback.
All reactions