This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi experts,
I uses a custom board that is similar to AM64x evm board, the difference is that I uses a bigger flash device to connect to AM64x via OSPI.
When the board runs, the ospi_clock cycles from 133MHz to 166MHz then down to 133MHz and go on.
My config is:
&ospi0 {
pinctrl-names = "default";
pinctrl-0 = <&ospi0_pins_default>;
flash@0{
compatible = "jedec,spi-nor";
reg = <0x0>;
spi-tx-bus-width = <8>;
spi-rx-bus-width = <8>;
spi-max-frequency = <25000000>;
cdns,tshsl-ns = <60>;
cdns,tsd2d-ns = <60>;
cdns,tchsh-ns = <60>;
cdns,tslch-ns = <60>;
cdns,read-delay = <4>;
cdns,phy-mode;
#address-cells = <1>;
#size-cells = <1>;
};
};
My questions are:
1. Does the ospi clock change because I enable phy-mode(cdns,phy-mode;) for tuning?
(When I tried to disable phy-mode the board can not boot anymore)
2. Is there any way to fix the ospi_clk?
Thank you
Hello Nick,
Have a nice day!
1. What boot method are you using?
I boot from OSPI flash.
2. At what point are you seeing the frequency cycling? (e.g., during boot, during Linux runtime, etc)
The cycled ospi_clk is captured when application is running( boot process is finished i think)
3. Is there any applicable terminal output?
I can not get your point. The OSPI pins are connected directly to external flash.
4. What version of Linux are you running?
I uses AM64x Linux SDK version 8.1.0.
Hope that you get needing information.
Thao