How do I access the QSPI Flash of the module when the system starts normally

[qiaowei]

Hello
I uses the Jetson orin nx module and custom board, and the SDK is Jetson Linux 36.3
I need to read everything in the QSPI, but I can’t access the QSPI flash after the system starts
I see that the QSPI flash can be accessed via /dev/mtd0 at initrd flash
However, when the system starts normally, there is no device tree node: spi@3270000
I added the spi node to the device tree, but it disappeared after startup

spi@3270000 {
			compatible = "nvidia,tegra234-qspi";
			reg = <0x0 0x3270000 0x0 0x1000>;
			interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH>;
			#address-cells = <1>;
			#size-cells = <0>;
			clocks = <&bpmp TEGRA234_CLK_QSPI0_2X_PM>,
				 <&bpmp TEGRA234_CLK_QSPI0_PM>;
			clock-names = "qspi", "qspi_out";
			resets = <&bpmp TEGRA234_RESET_QSPI0>;
			status = "okay";
		};

What should I do, please?

[KevinFFF]

Hi qiaowei,

@qiaowei

I need to read everything in the QSPI,

May I know your use case?
What do you want to read in QSPI?

[qiaowei]

Because I met a problem, the device could not be started after repeated restarts. I speculated that the QSPI data might be damaged. I need to know which data of QSPI has been changed, so I want to read the data and have a look

Jetson orin nx failed to bootup after UEFI updated

I see execution edk2-nvidia/Platform/NVIDIA/Jetson/build.shwill not compile this code,It is not in uefi_jetson.bin,It should be updated tos-optee_t234.img, right? I use the following steps: Apply pathch to edk2-nvidia:r36.3.0-updates Compile in the nvidia-uefi directory:edk2-nvidia/Platform/NVIDIA/StandaloneMmOptee/build.sh cp /data/nvidia-uefi/images/uefi_StandaloneMmOptee_RELEASE.bin /data/EC5000_R36.3.0/Linux_for_Tegra/bootloader/standalonemm_optee_t234.bin mkdir optee && cd optee cp /dat…

[KevinFFF]

You can use backup/restore script to get the QSPI0.img after backup.

For the assertion issue, I’ve updated in another thread you sent.

[qiaowei]

hello
I read the QSPI.img data before and after the two restarts and found that the data in uefi_variables was different
I have already blocked MTC(MonotonicCounter), why will uefi_variables be changed during normal restart
We are concerned that a sudden power outage during the restart will cause damage to the uefi_variables data, so we need to mask the code that modifies the uefi_variables data each restart
I have compared the data binary file twice, and I see that the 3F after AA 55 will become 3C each time. What is this

[KevinFFF]

@qiaowei

have compared the data binary file twice, and I see that the 3F after AA 55 will become 3C each time. What is th

QSPI binary includes all boot-chain not only UEFI but also MB1,MB2, SPE…etc.
Sorry that I’m not aware of the raw data in whole QSPI binary.
If you are trying to solve the assertion issue in UEFI, please just refer to the link I shared in another thread.
There should be the patch and steps to apply the fix.