Skip to content

Conversation

@ricardosalveti
Copy link
Contributor

Only ddr_a/b (ddr training) and persist remains without being zeroed on a clean flash, required in order to be able to always reproduce the same flash state on clean flash.

@ricardosalveti
Copy link
Contributor Author

Tested on rb3gen2, qcs9100-ride-sx and qcs615-adp-air, no clear side effect. Needs more testing as we could see unexpected errors.

@mwasilew this should help getting the devices to a reproducible state, just not erasing ddr (and persist, but it is not yet used) because it implies in a new ddr training on every flash.

Only ddr_a/b (ddr training) and persist remains without being
zeroed on a clean flash, required in order to be able to always
reproduce the same flash state on clean flash.

Signed-off-by: Ricardo Salveti <[email protected]>
@lumag
Copy link
Contributor

lumag commented Oct 31, 2025

My major concern with this is that all of the following partitions types are now very hard to distinguish:

  • parittions, which are unused
  • pariitions, which should be zeroed for the normal operation
  • partitions, which can carry some longer term state, which we destroy flashing them.
    It would be nice to be able to distingush those.

@ricardosalveti
Copy link
Contributor Author

Yup, even identifying the ones we don't need is not easy atm, ideally we should have a clear understanding of each of the individual partitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants