Hi Jorge,
Thanks for the response. So one purpose of the DDR tool is to generate code that properly initializes DRAM based on the DRAM part selected and how it was connected to the 8M Mini. Okay, that makes sense.
But the mscale DDR tool also trains and calibrates the DDR memory. When you click "Gen Code", it even generates a file called "ddrphy_train.c", and another called "lpddr4_timing.c". So, in addition to telling u-boot the DRAM configuration (DDR type, density, bit swizzling, etc.), it looks like we also communicate the timing and calibration results to u-boot. But why? Doesn't u-boot regenerate these calibration values on every boot? Where/how do the mscale-generated timing and calibration values get used?