We have problem to flash the QSPI flash on Parker chip of our boards. Tracing the flashing script, we found that it hangs at
/tmp/nvdd --inputbin=/tmp/bctCopiesBlob.tmp --device=/dev/mtd/mtd0 --startoffset=0 --partsize=524288
The flashing script was provided by Nvidia. Here nvdd is Nvidia’s dd to write to mtd0 (see below). Please advise. Does that mean QSPI flash is somehow corrupted?
A related question is how to erase mtd0 ? (some people suggest that maybe we should erase it first).
# ./nvdd -d|--device is necessary Error Code 0x4 Usage: -i|--inputbin <PARTITION_BINARY>. Input binary that will written or used for verification -f|--outputbin <filename>. Output binary name that will be created by reading data from device -d|--device <DEVICE_NAME>. Device on which nvdd will operate -o|--startoffset <START_OFFSET>. Offset on device from where nvdd operate -s|--partsize <PARTITION_SIZE>. Size of partition where input binary will be written -e|--parterase. Erase rest of the partition after writing binary-r|--readback. Read data from storage and compare with original binary -u|--partunlock. Unlock partition if it was locked -n|--nowrite. Used for verification only and avoid writing on device -m|--md5sum <MD5 STRING>. String used to validate written binary on device -p|--printmd5sum Print md5sum of the calculated for partition on device -E|--deverase <eoffset=OFFSET,esize=SIZE> Erase ezise on device from eoffset Example: ./nvdd --inputbin KERNEL_PRIMARY_16.img --device /dev/mtd0 --startoffset 6815744 --partsize 18874368 --readback