Ursula
October 16, 2022, 12:51am
1
It seems that on Xavier NX with R35.1, the flashing is a lot slower over USB than with older releases e.g. R32.6.1 and takes at least three minutes longer. In the serial log, I can see that the QSPI clock speed is 1/3 of the speed that it used to be. See timestamps below. Is this expected?
Before:
[0086.309] I> Welcome to TBoot-CPU Recovery
[...]
[0086.568] I> QSPI source rate = 204000 Khz
[0086.571] I> Requested rate for QSPI clock = 34000 Khz
[0086.576] I> BPMP-set rate for QSPI clk = 34000 Khz
[...]
[0241.444] I> Writing APP partition.
After:
[0112.846] I> Welcome to TBoot-CPU Recovery
[...]
[0112.949] I> QSPI source rate = 204000 Khz
[0112.949] I> Requested rate for QSPI clock = 12000 Khz
[0112.954] I> BPMP-set rate for QSPI clk = 12000 Khz
[...]
[0468.474] I> Writing APP partition.
Hi,
This seems to be an issue. Will check.
Hi,
Please try to set the same parameters as rel-32 in your rel-35 config for this file.
tegra19x-mb1-bct-device-qspi-p3668.cfg
Ursula
October 28, 2022, 3:28pm
7
Hi,
The console output looks better and implies the old frequencies have come back, but the flashing process is still slow:
[0212.990] I> Welcome to TBoot-CPU Recovery
[...]
[0213.091] I> QSPI source rate = 204000 Khz
[0213.092] I> Requested rate for QSPI clock = 34000 Khz
[0213.096] I> BPMP-set rate for QSPI clk = 34000 Khz
[...]
[0554.922] I> Writing APP partition.
Just the SPI flash erase alone seems to take much longer, even with the change applied:
R32.6.1:
[0110.835] I> QSPI: Erasing entire device
[0174.841] I> Writing device 3: 0.
R35.1:
[0226.465] I> QSPI: Erasing entire device
[0340.473] I> Writing device 3: 0.
Then this clock has nothing to do with the QSPI speed…
Ursula
November 2, 2022, 1:20am
9
It would seem so. Will a fix for this be investigated?
I think no. Currently there is no plan.
system
Closed
November 23, 2022, 5:20am
12
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.