Hahahah…Dont get mad. I was just trying to know whether PCIE lane has any relevance to USB.
I think you believe I am bad linux engineer.
Anyways I will try to debug the pcie issue via mentioned link. Now. And get back to you
Sometimes there are hardware engineer directly working on the interface bring up and they may not work on Linux kernel before.
Those software settings may not be part of their job so (if possible) I think it would be better to directly get a real software engineer to join to discuss. That is the point I am trying to say.
Same NVME connected as USB is flashed successfully…Please tell me further steps
As for this, this does not matter because this is still a USB device to Jetson. Not a PCIe device on your C4.
USB was successfully flashed but when i rebooted the jetson it didnt detect it it gave this
sharing logs in a moment
Sometimes USB is detected and sometimes its not to be flashed. I did find that if I format the USB drive and then flash it does then
Are you still using nvme to USB or you are using a USB drive?
I am using NVME in USB (It is detected and flashed) , I have tried USB 16gb that does not have sufficient storage but it is detected every time I connect, I have used 64 GB usb it is neither detected nor flashed.
Right Now:
I tried JetPack 6 Version, In it no case follows, neither USB detected nor PCIE,
I believe there is some configuration I am missing for my custom board
It could be that even the usb configuration on your board is also wrong. You need to at least find an interface that can use to boot first. Otherwise you won’t be able to debug anything.
Flashing many times brought ubuntu image.Now i will try to diagnose pcie issues
some pcie related logs after booting to ubuntu
Logs.txt (2.9 KB)
Why did the error log become worse here? Did you change anything in PCIe C4 controller setting?
5.329322] tegra194-pcie 14160000.pcie: Adding to iommu group 3
[ 5.330345] tegra194-pcie 14160000.pcie: Failed to get PHY: -19
Changed nothing. Except that I am using now JP 6.1 version. Not JP 5.1.4 version
How did you flash your jetpack6… it is most likely something in boot stage goes wrong.
sdk manager. USB settings works. Can you point out which boot file i need to check
Ok… fine. Forget about what I just told. Share me the full dmesg of current situation.
I will share in a moment I have one little observation I believe you can share any info about it. I observed that if flashing to USB it doesnt flash everytime. flash says it didnt detect the usb while uart log says it is ready after the flashing is failed. is there a way i can increase the detection time. Because I believe same is for PCIE
Check l4t_initrd_flash_internal.sh and search for below variable to let the flash waiting timeout higher.
maxcount=${timeout:-120}
I don’t think your PCIe issue could be fixed by adjusting this.
Yes You were right this doesnot correct the issue. I am still trying to experiment with USB currently before going to PCIE. USB is giving odd behavior . I have to run several times before only-flash works and detects usb . Whenever JETSON boots power on the usb adpater can tell that this time flashing work Any idea why can be this behavior
I guess the issue here is none of your software setting matches your board design or the hardware itself has some issue.
Even USB software (Device tree) needs to match the board design.
sorry for the late response. here is dmesg logs
dmesglogs.txt (79.3 KB)