-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[jetson-tx2] Flashing fails, is it due to new FAB new boards have? #478
Comments
Could you please share the steps you are using here to build and images signing ?
|
Also - can you flash and boot the target device with stock L4T R32.3.1? If you can't use regular L4T due to having a custom carrier, can you try putting a D02 module in a Jetson TX2 development kit and try stock L4T there? In addition to what @ichergui mentioned, it would also help to see the full log of your doflash.sh session plus the output captured on the serial console of the TX2 during the flashing process. |
Hi @manuel-wagesreither
|
Thank you all for being of help here! @ichergui We are signing our Mender update artifacts, but not the images itself. @madisongh @dwalkes |
@ichergui In the generated rootfs this file is missing for some reason.
At a flashed board, the content of this file is:
I assume this board is of |
No problem, the file is not missing, it will be auto generated via systemd service called I don't have here a Jetson TX2 with the same Did you succeed to flash you device by using a stock L4T as @madisongh suggest ? if not, please try it and let us know if you got any issues. I suggest to try with the DevKit. |
Got it, thanks for the explanation. Due to COVID-19 I'm working from home and won't have access to an development kit until next week. Same for a Jetson TX2 with FAB
I joined this team when Yocto was already up and running, so I'm lacking some basics of using the Jetson TX2 in a standalone way. That is, when it is not integrated in our product. If I understand the NVIDIA website right, I using the SDK and following this guide would be a feasible way to do this, right?
Will do that. |
Yes, that should do it. |
Are you interested in the D02 logs for further development of meta-tegra? If yes, I will do the steps as requested. If not, I would skip it, as we're reasonably convinced that @dwalkes is right and our outdated Jetpack version is the root cause. Here's a link to PCN 206440 which contains detailed information on this. When trying to
The PCN says this hardware version changed the DRAM, so as far as I'm concerned, this is proof enough. I would close this ticket if there is nothing from your side. Thank you everyone and @dwalkes in particular! |
Sounds that way, based on what's in the PCN. You'll need at least L4T R32.4.2 for the firmware and config files necessary to support the new DRAM. And it looks like I need to update the TEGRA_BUPGEN_SPECS setting in the jetson-tx2 machine config file to add an entry for the D02 FAB. |
Do you intend to add support for L4T R32.4.2 to zeus? |
We have R32.4.3 support on the |
Alright, so an update to dunfell it is. Appreciate your work on meta-tegra! Thank you! |
Hello everyone,
we've received a new batch of Jetson TX2 SOMs which we are unable to flash with our Yocto-created distribution based on
zeus
. We are on596c4adc1e
of meta-tegra, but as far as this is concerned it should be functionally equal to currentzeus-l4t-r32.3.1
.These are the last few lines of
./doflash.sh
output:The script doesn't return and just gets stuck then.
The failing SOMs have
FAB=D02
(whatever that means); while our existing SOMs haveFAB=D00
.In an attempt to add compatibility for this new boards, we made the following changes, which didn't help.
Can someone shed some light on this?
One of our engineers assumed the bootloader which
doflash.sh
pushed onto the board might not run there due to incompatibility or wrong signature. Is he correct? Which other steps would one need to do to add compatibility with these new boards?Are we even on the right track here?
Thank you a lot,
Manuel
The text was updated successfully, but these errors were encountered: