There are sometimes some early lines (at the start) which are binary, but that’s too far into the boot to think it isn’t an error. The actual progression of boot is very short and it stops before it even gets to a bootloader, so if this is truly the full log, then something in the QSPI is missing very early on (dev kits booting to an SD card have that content in QSPI memory; this memory is accessible only via flash). This was not an SD card error, the boot didn’t even get close to the point of searching for SD card.
You might find this post of interest:
https://forums.developer.nvidia.com/t/does-jetpack-sdk-5-1-work-with-jetson-tx2/253581/8
(related to you because your boot never got past the part which is equivalent to BIOS, and thus never even started the part which is really bootloader, and it is bootloader which would have searched for the SD card)
The way I see it you cannot succeed without flashing the module. One thing I will suggest is that perhaps character set got in the way during your flash steps (and if you didn’t flash the module itself, that counts for something getting in the way of flash steps…the SD card itself doesn’t really get flashed). When using sdkmanager to flash I suggest you prefix your startup with “LANG=en_US.UTF-8”. Be sure to use the same release which is used for creating the SD card. An example, assuming you have a 5.x JetPack, but don’t necessarily have the exact most recent release and want to see other releases and are logged in as your regular user:
LANG=en_US.UTF-8 sdkmanager --archivedversions
(if your sdkmanager is the same release as that which created the SD card, then no need for “--archivedversions”; additionally, you might need a 4.x JetPack release if you are using an earlier SD card release)