MSS_RESET_N_M2F from MSS takes over 2 seconds to be released after DEVICE_INIT_DONE from PFSOC_INIT_MONITOR is set #502
Replies: 2 comments 1 reply
-
Hey @henryding-emcore sorry for the delayed response. The MSS_RESET_N_M2F is driven from an MSS register, you can set it at any point during the boot process, there is a function in the HAL which can be used for this and you can see its just setting a bit in a register - its here. The reason its being used in the way it is:
Its not mandatory to use and if you have logic that doesn't rely on the MSS and is independent there is no requirement to wait for it to assert, so you could either set it earlier in the boot process or not use it to drive a reset for anything independent. To answer your questions:
|
Beta Was this translation helpful? Give feedback.
-
Thanks for your response, Hugh!
My intention is to find out why MSS takes over 2 seconds to finish the initialization. I'm not sure if it's caused by user codes or factory codes. Is there any document talking about MSS initialization time and the way to short it? My design is bare metal with boot loader in Core 0.
Thanks,
Henry
|
Beta Was this translation helpful? Give feedback.
-
I'm using PolarFire SoC FPGA to implement my design. In MSS, I don't use DDR Memory. However, I measured on the scope and found that MSS_RESET_N_M2F from MSS takes over 2 seconds to be released after DEVICE_INIT_DONE from PFSOC_INIT_MONITOR is set.
I have two questions:
Note: since DDR Memory is UNUSED, I don't see any configuration for DDR Controller.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions