Closed Mausy5043 closed 7 years ago
FooDeas
commented
7 years ago Interesting! Only the timestamps of these files, which are created while building are affected. Maybe building on a VM?
The empty "TIMEOUT" file belongs to the MSD boot feature. It tells the bootloader to increase the enumeration timeout limit from two to five seconds without the need to permanently change the OTP bit.
(I can't read your js script here in a trice.)
Mausy5043
commented
7 years ago Built on a Raspberry Pi B+
I've updated the link. It's a shell script, I pasted in the wrong link. Here is the correct one
I've added an extra ls -al --full-time and built it again. The files are being/ seem to have been/ will be created about 6 seconds in the future 😲 . Great Scott!
I gathered from the source that the TIMEOUT file was only created during install. Not during the build.
FooDeas
commented
7 years ago You are using a remote FS. Eigher the time on that system is in future compared to the local ~or it uses another time zone~.
Check it by creating any new file in your mount folder, using the stat command and compare it to the output of date. If you do this in one command chain, you can reproduce and verify your issue.
(The timeout file is created while building in line 681.)
Mausy5043
commented
7 years ago @FooDeas You're right. The remote system's time wasn't getting update by ntp
Thanks!
After the building of the
develbranch this evening; looking at thetreelisting (see below) two odd things caught my eye. First is the fact that some files were created in "The Future" and the second is presence of the fileTIMEOUTthat's in the root.Note: This is after the build phase (clean, update, build) and the
usbbootparameter is not set (as far as I know).WTF?
NB: This is how I build: