Seems to be weird version numbers on new batch, causing issue with the flash script. The issues can maybe be worked around but I can’t find any record of this SKU variant or what if anything has changed, so it’s unclear what else would need checking.
new batch shows: Board ID(3448) version(002) SKU(0004) revision(B.0)
older variant shows: Board ID(3448) version(402) SKU(0002) revision(B.0) from environment
‘tegrarcm --oem platformdetails eeprom’ output seems to confirm this too:
date code 5020: 699-13448-0002-400
date code 1424: 699-13448-0002-401
date code 4825: 699-13448-0004-002
Is there something going wrong reading the eeprom, or is this new actually a new variant?
(The memory PCN has been applied already, but this isn’t getting that far anyways)
There seems to be some problem on new batch (699-13448-0004-002), suggest to reach out to you local distributor to report this issue and prepare for new shipment. Sorry for that.
Hi, Thanks for the response. These were ordered from Arrow, I was not the direct contact with them but they didn’t seem to know anything about the issue (yet?).
Can we get some more details:
Is this a known issue? Are the effected date ranges known?
Do these modules just need to be RMAd, what is the process for that if so?
They shipped another batch more recently with slightly older date codes (3725) on PCB and they seem fine, but there are more on the way in the future and it would be good to know if/how we can avoid this issue in future, as well as how to resolve the issue with the modules we already have.
Arrow EU reported this issue first, and there are some modules shipped to customer already.
Currently this issue was fixed and created the lesson learn in our factory side(ODM partner).
Please do the swap with distributor.