Hello,
A project I’m working on requires write capability for a NOR flash device in BL2 (to update a small boot mux partition). I am considering adding this capability to the IO MTD layer (https://github.com/ARM-software/arm-trusted-firmware/blob/master/drivers/io/...), but before doing so wanted to confirm this is in line with the architecture of this subsystem. Can someone confirm if this is an acceptable change?
Regards, Brian
Hi Brian,
I don't think it should be a problem adding a write capability in this structure.
What other framework or driver do you plan to use under this framework?
AFAIK, STM32MP1 is the only platform for the moment to use this framework. Is your project based on this SoC, or is it another platform?
Best regards, Yann
On 6/24/22 17:53, Brian Neely via TF-A wrote:
Hello,
A project I’m working on requires write capability for a NOR flash device in BL2 (to update a small boot mux partition). I am considering adding this capability to the IO MTD layer (https://github.com/ARM-software/arm-trusted-firmware/blob/master/drivers/io/...), but before doing so wanted to confirm this is in line with the architecture of this subsystem. Can someone confirm if this is an acceptable change?
Regards, Brian
Hi Yann,
Thanks for your reply. This is for a new SoC my company is developing. The plan is to hook our custom SPI controller driver to the MTD framework, which will be used to load the FIP from a NOR flash device. I saw some other non-MTD implementations in the TF-A source (e.g. https://github.com/ARM-software/arm-trusted-firmware/blob/master/drivers/brc...), but assumed the correct thing to do going forward was to use MTD. Is that a good assumption?
-Brian
Hi Brian,
You're right, it is better using the MTD framework than a private one. But there is no obligation for older platforms to move to the MTD framework.
Best regards, Yann
On 6/27/22 15:11, Brian Neely via TF-A wrote:
Hi Yann,
Thanks for your reply. This is for a new SoC my company is developing. The plan is to hook our custom SPI controller driver to the MTD framework, which will be used to load the FIP from a NOR flash device. I saw some other non-MTD implementations in the TF-A source (e.g. https://github.com/ARM-software/arm-trusted-firmware/blob/master/drivers/brc...), but assumed the correct thing to do going forward was to use MTD. Is that a good assumption?
-Brian
tf-a@lists.trustedfirmware.org
-
brian.neely＠analog.com -
Yann Gautier