This forum does not work for me. The simplest questions remain uncommented, not even to ask for answers. This is not a base for thinking about professional usage of DS and Jetson Nano.
So what other options do we have? Is there some paid support? I would be happy to ask my bosses to spend this money, since I don’t move forward and I’m tired of being forced to ask again and again to no avail.
In the hope, that at least this question will be answered or even discussed - Have a nice day.
Hi foreverneilyoung.
Please help to list down those issues, then we can review them again.
To do further support, please contact with our region sales for the details.
Thanks for the follow up. Here is the list of my open issues
This is IMHO a bug Phantom detections in cluster modes != 0 I provided you with all means to reproduce
A question for more information: Cluster modes - a deeper description avaialble?
Also this: Can I determine DS and JP version at python level?
And this: Question regarding confidence - #7 by foreverneilyoung. If you don’t see my point anymore, here again: “What is the meaning of ntp_timestamp”?
I need to make my SD file system read only to no avail. Is there any tutorial, I could follow? I tried something (shown here), but it didn’t work Make Jetson Nano SD /dev/root read-only
I now twice thad the situation, that the Nano’s “device mode” (the L4TBR0 thingy) stopped working. I was working for hours and hours with it and then - out of the sudden, the device disappeared on the Nano and there was NO WAY to recover from that. The Nano still reacted on plugs of the USB cable, but nothing happened anymore. I’m sure my cable is working and on the other side is a trustworthy device, which is completely out of focus for errors - my Macbook. I could only recover from this by re-flashing the SD card…
Thanks
agreed, I’d pay to be able to phone someone
We are in holiday in the past week, so there are some delay.
And, for topics - Can I determine DS and JP version at python level? and Stability of Jetson Nano together with DeepStream , we replied you even we were in holiday.
As discussed on topic - Stability of Jetson Nano together with DeepStream , this is because of the filesystem in your SDCard. You need to make sure you didn’t hot-plug SDCard when system is running, or sudden power shutdown, HW connection of the SDCard is good, etc.
So you are still on holiday or will there be more to come? I don’t see any qualified answer to my concrete questions. If this is all what this forum can offer, than thank you very much and consider to stay on vacation.
You need to make sure you didn’t hot-plug SDCard when system is running, or sudden power shutdown
Yeah, thanks treating me like an idiot. I have deserved that because I was hoping for qualified assistance of engineers here.
Of course, I don’t do anything of these stupid things you are assuming me to do. But what shall I do if the box crashes out of the sudden, just because one has touched the USB cable, w/o asking for permission beforehand? That’s why I wanted to make the file system RO, I have made very good experiences with operations like this on a Raspberry PI, which survived > 3 K power cycles w/o damaging the SD card then.
If these kind of “suggestions” is what you will be able to deliver than this is the wrong place for me to expect anything anymore. Please don’t “answer” me again, you just make my day (worse)
There is no paid support option for things like Nvidia Jetson Nano. Statement from Nvidia
Hi foreverneilyoung,
If you’re going to use Jetson Nano to launch product, may I know the roughly number of unit for 2021? Also your product development and launch plan?
Then we can discuss internally with team.
Please be more patient with the support in forum. Thanks
Well, I can ask the board, but basically this depends on me. If I say, the Nano is a capable device but the software has issues, the hardware tends to instabilities and the support is to forget about, then they will for sure not ask for it anymore. I’m still evaluating you for a bigger project.
So far I’m convinced I will drop you in favour of an RPI / Coral TPU pair. It sucks, if simple questions like “what is the meaning of ntp_timestamp” (which I asked at least 10 times now) are still unanswered after weeks.
But this is not what concerns me most. I’m pretty disappointed that I cannot find a solution, which applies a minimal SD protection, which would satisfy me and at least work. ATM this is the major blocking point and I’m baffled, if I’m really the only one, who has this issues.
To say it clear: I finished my evaluation last Friday and reported. I clearly said, this box is not production ready. I really would like to change that, but I can’t w/o a minimum of support of some people, who are knowing what they are talking about. I’m clear about, that I can’t ask for it for free. But there is not even paid support…
This is maybe the sign I did need: After dealing the entire weekend with the box, trying to make it boot RO, it is now not booting anymore at all. Not even with a fresh image or with an older image.
That’s it then.
Hi foreverneilyoung,
Really don’t understand how you make it boot RO, but suggest to open another topic to get issue root caused and resolved.
Regarding the SD protection, as the reply at Make Jetson Nano SD /dev/root read-only, that’s not supported, but for eMMC module only.
Please help to reply back to each topic you created, then our team can help to move it forward.
Thanks
Really don’t understand how you make it boot RO, but suggest to open another topic to get issue root caused and resolved.
I didn’t make it. And I will not open yet another topic on this, it will not work.
Regarding the SD protection, as the reply at Make Jetson Nano SD /dev/root read-only, that’s not supported, but for eMMC module only.
I’m sorry, I don’t believe that. As @linuxdev stated each Linux rootfs can be made RO. But obviously not your’s.
Please help to reply back to each topic you created, then our team can help to move it forward.
For what topic do you miss my response? For me it is quite the other way around.
And to let you know how I bricked the Nano: I just used your SDK manager and “managed” to kill it:
In the middle of the flash the Nano booted and that was it.
FYI, when flash stage completes, then the Jetson reboots. This is so first boot account setup can be performed. Then any optional packages which JetPack/SDKM specified can be installed over ssh. If you don’t have video output, then it might be that the Jetson is otherwise up and booted. However, your screenshot does show that flash itself failed. Don’t worry about that, a “bricked” unit implies it can’t be flashed, but this will in no way prevent you from flashing again to correct any problem.
What I’m going to suggest is to find the flash directory and do nothing but flash on command line. This has the least number of possibilities of failures. You will find this directory:
~/nvidia/nvidia_sdk/JetPack...version.../Linux_for_Tegra
With the Jetson in recovery mode you would run a command like this (you’ll have to edit…I don’t see in this thread which version of Jetson is used…I can clarify if you mention the actual model of Jetson…this pretends it is a full Xavier):
sudo ./flash.sh jetson-xavier mmcblk0p1 2>&1 | tee log_flash.txt
Note that the “`2>&1 …” is to create a log of the flash. Technically not needed but this would be very useful since you can upload it to the thread.
Beware that a lot of failed package dependencies are network errors, or else very simple to fix…but we’d need the exact message to know.
This morning I flashed a JP45 from Nvidia using Balena Etcher on another device. No chance, the box does not boot anymore. I have an HDMI monitor attached. Tried with two other new SDs and the same procedure. Same output. Informed my dealer. Sent the box back. I feel innocent, I just used followed the Nvidia tool. For the first time BTW, never did that before. I was just curious if this “manager” would give me the option to make the SD RO.
I think I’m done with the Nano. Let’s see what happens with the box. But I doubt I will restart again. With this missing support I don’t feel fit enough to go into the next stages with this device. The imagination to be forced to beg for answers every now and then is frustrating enough.
I am new to this thread so not sure if I can still help any system side issue (flashing/booting problem).
If you get stuck in sdkmanager, maybe you can directly use flash.sh and share both host and device side to us.
I write a page for more detail about why I prefer to debugging with flash.sh but not sdkmanager. You can check it here.
Thanks. Will consider if I get the board back or a new one.
No, SDKM is more or less a way to download and set up the flash software and some optional packages. There is no ability to select if the filesystem would be read-only. What happens is a basic install is performed by flash, and then the Jetson reboots. After rebooting first boot account setup is expected. Then SDKM will be able to use that account over ssh to install other optional packages, e.g., CUDA.
Once you have a working read-only setup it is easy to customize the such that every flash will contain your customizations, and in theory “just work” right after flash. Other than some boot content the files in the host PC’s “Linux_for_Tegra/rootfs/” will be an exact match to what gets flashed.
An example of a customization would be to add a user home directory and full user name creation to the “rootfs/”, and thus be able to avoid first boot setup…the user would just exist. This extends to other customizations.
