-
Can you share the sdkmanager log? It should be inside ~/.nvsdkm on your ubuntu host. Are you stuck in the “download” process of sdkmanager or you already flashed the board but you cannot tell the board is fine or not?
-
We usually use the serial console from UART port to check the boot log when IO peripherals are not working. For example, no HDMI monitor or no usb device mode.
This is most likely the last run where I was only trying to get the Nano to connect.
log text follows:
wsprdaemon@wsprd7:~/.nvsdkm$ cat sdkm.log
17:56:22.155 - info: SDK Manager started running at: 2021-05-28 17:56:22.154
17:56:22.156 - info: SDK Manager log file name: sdkm-2021-05-28-17-56-22.log
17:56:22.156 - info: SDK Manager client version: 1.5.0
17:56:22.156 - info: SDK Manager is running in GUI mode
17:56:24.642 - info: Current DB Version: 14
17:56:25.513 - warn: Registering a callback with no name for event: System settings table changed after getting machineInfo
17:56:25.749 - info: User agent for http requests: SDKM/1.5.0.7774 (ubuntu1604)
17:56:25.827 - warn: Registering a callback with no name for event: Session started
17:56:25.967 - warn: Registering a callback with no name for event: Session started
17:56:25.967 - warn: Registering a callback with no name for event: Report component install/uninstall error messages
17:56:25.967 - warn: Registering a callback with no name for event: Report component install/uninstall error code/type
17:56:25.968 - info: downloadMetrics.reset
17:56:25.968 - warn: Registering a callback with no name for event: Session started
17:56:25.968 - warn: Registering a callback with no name for event: Session resumed
17:56:25.969 - warn: Registering a callback with no name for event: Session started
17:56:25.969 - warn: Registering a callback with no name for event: Session ended
17:56:25.969 - warn: Registering a callback with no name for event: File init download status
17:56:25.969 - warn: Registering a callback with no name for event: File pending download
17:56:25.969 - warn: Registering a callback with no name for event: File started downloading
17:56:25.969 - warn: Registering a callback with no name for event: File finished downloading
17:56:25.969 - warn: Registering a callback with no name for event: File checksum verifying
17:56:25.969 - warn: Registering a callback with no name for event: Component init status
17:56:25.969 - warn: Registering a callback with no name for event: Component started action
17:56:25.969 - warn: Registering a callback with no name for event: Component finished pausing download
17:56:25.969 - warn: Registering a callback with no name for event: Component finished resuming download
17:56:25.969 - warn: Registering a callback with no name for event: Component finished action
17:56:25.970 - warn: Registering a callback with no name for event: Session started
17:56:25.970 - warn: Registering a callback with no name for event: Component finished action
17:56:25.972 - warn: Registering a callback with no name for event: Active bundle loaded
17:56:25.972 - warn: Registering a callback with no name for event: Component finished action
17:56:25.973 - info: Forking worker process
17:56:25.978 - info: Initializing the download service
17:56:25.983 - info: Download service pid is: 3432
17:56:25.985 - warn: Registering a callback with no name for event: File download in progress
17:56:25.985 - warn: Registering a callback with no name for event: File finished downloading
17:56:25.986 - warn: Registering a callback with no name for event: Session started
17:56:25.986 - warn: Registering a callback with no name for event: File download in progress
17:56:25.986 - warn: Registering a callback with no name for event: File finished downloading
17:56:25.986 - warn: Registering a callback with no name for event: File reset downloaded size
17:56:25.986 - warn: Registering a callback with no name for event: File download size updated
17:56:25.986 - warn: Registering a callback with no name for event: Component init status
17:56:25.986 - warn: Registering a callback with no name for event: Component started action
17:56:25.986 - warn: Registering a callback with no name for event: Component progress for action
17:56:25.986 - warn: Registering a callback with no name for event: Component finished action
17:56:25.987 - info: Download manager can use up to 6 download threads per file
17:56:25.987 - warn: Registering a callback with no name for event: Session started
17:56:26.019 - info: create .sdkm.bashrc under /home/wsprdaemon/.nvsdkm/.sdkm.bashrc
17:56:26.024 - info: installMetrics.reset
17:56:26.024 - warn: Registering a callback with no name for event: Session started
17:56:26.024 - info: uninstallMetrics.reset
17:56:26.024 - warn: Registering a callback with no name for event: Active bundle loaded
17:56:26.025 - warn: Registering a callback with no name for event: Active bundle loaded
17:56:26.025 - warn: Registering a callback with no name for event: Component finished action
17:56:26.025 - warn: Registering a callback with no name for event: File finished downloading
17:56:26.025 - warn: Registering a callback with no name for event: Component finished downloading
17:56:26.025 - warn: Registering a callback with no name for event: Session started
17:56:26.025 - warn: Registering a callback with no name for event: Session resumed
17:56:26.025 - warn: Registering a callback with no name for event: Session paused
17:56:26.025 - warn: Registering a callback with no name for event: Session complete when pausing
17:56:27.086 - warn: Registering a callback with no name for event: File started downloading
17:56:27.086 - warn: Registering a callback with no name for event: File download in progress
17:56:27.086 - warn: Registering a callback with no name for event: File checksum verifying
17:56:27.086 - warn: Registering a callback with no name for event: File finished downloading
17:56:27.256 - warn: Registering a callback with no name for event: Active bundle loaded
17:56:27.271 - warn: Registering a callback with no name for event: Terminal output
17:56:27.271 - warn: Registering a callback with no name for event: Login progress
17:56:27.272 - warn: Registering a callback with no name for event: undefined
17:56:27.272 - warn: Registering a callback with no name for event: Component download in progress
17:56:27.272 - warn: Registering a callback with no name for event: Component progress for action
17:56:27.272 - warn: Registering a callback with no name for event: Component started action
17:56:27.272 - warn: Registering a callback with no name for event: File started downloading
17:56:27.272 - warn: Registering a callback with no name for event: Component init status
17:56:27.272 - warn: Registering a callback with no name for event: Component finished pausing download
17:56:27.272 - warn: Registering a callback with no name for event: Component finished resuming download
17:56:27.272 - warn: Registering a callback with no name for event: Component finished downloading
17:56:27.272 - warn: Registering a callback with no name for event: Group finished downloading
17:56:27.272 - warn: Registering a callback with no name for event: Component finished action
17:56:27.272 - warn: Registering a callback with no name for event: Session paused
17:56:27.272 - warn: Registering a callback with no name for event: Session resumed
17:56:27.275 - info: Logger level is set to: info
17:56:27.457 - warn: Registering a callback with no name for event: Login progress
17:56:27.457 - warn: Registering a callback with no name for event: CLI Abort
17:56:27.491 - info: Front-end main function (startMain) was called
17:56:27.564 - info: Creating auto update task
17:56:27.578 - info: Host OS: ubuntu1604
17:56:27.579 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.json
17:56:27.600 - info: [Download Service]:Download service is initializing
Download service was initialized
Got heartbeat request
17:56:27.600 - info: [Download Service] Download service is alive
17:56:27.720 - info: Application configuration is:
{
mainRepoURL: ‘https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json’,
PIDServer: ‘P’,
DevZoneServer: ‘P’,
StarfleetServer: ‘P’
}
17:56:27.779 - info: manifest: {“name”:“sdkmanager”,“releaseVersion”:“1.5.0”,“releaseRevision”:“0”,“releaseBuild”:“7774”,“release”:false,“chrome”:“78.0.3904.113”}
17:56:27.779 - info: Telemetry parameters are: title: SDK Manager 1.5.0.7774 version: 1.5.0 dev: 0 internal: false
17:56:27.779 - info: autoLogin failed: Aborting auto login since there is no logged in user
17:56:27.780 - info: Telemetry: allow = . isGDPRAllowed=false
17:56:27.780 - info: Total memory: 3.75 GB
17:56:27.781 - info: Screen res: 1536 x 864, scaleFactor 2.5
17:56:27.781 - info: Total memory: 3.75 GB
17:56:27.781 - warn: The system does not meet the minimum requirements.
- Please use headless (CLI) mode for better experience. Get started with sdkmanager --help.
- Please reduce concurrent file download in SDK Manager Settings, for a better experience.
Do you wish to continue?
17:56:27.782 - info: Warning dialog pop up position: 520 360
17:56:27.806 - info: Warning prompt url:file:///opt/nvidia/sdkmanager/resources/app/output/dist/electron/pages/prompt/prompt.html#1622246187785-0.7548971182705497
17:56:27.812 - info: mainRepoUrl: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
17:56:27.814 - info: logging in with l1 url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
17:56:27.850 - warn: crontab read failure with Error: Command failed: crontab -l
no crontab for wsprdaemon
17:56:27.860 - warn: crontab read failure with Error: Command failed: crontab -l
no crontab for wsprdaemon
17:56:28.000 - info: Create timing task for auto update successfully.
17:56:53.406 - info: logging in to starfleet server
17:56:53.406 - info: Logging in with starfleet login method…
17:56:53.410 - info: Event: Login Progress: undefined
17:56:53.808 - info: Listening to Starfleet Redirect URL on port: 8080
17:56:53.809 - info: Listening to Starfleet Development signin URL on port: 40245
17:56:53.809 - info: Openning login URL in browser: https://login.nvidia.com/authorize?response_mode=query&response_type=id_token+token&device_id=51ad6bc6b5fe09a7cb601004f4091a175f0060baefd2a7aa9f4ae7c288d2aebf&scope=openid+consent+email&client_id=_gWkp8NvPxc7svfRKyXJ4IseQyYupLhWJiMxyPy0gm4&prompt=login&ui_locales=en_US&nonce=67676767&state=http://localhost:40245&redirect_uri=http://localhost:8080
17:56:53.812 - info: Event: Login Progress: Waiting for user to complete login in the external browser…
17:57:33.129 - info: Got Starfleet server signin response. Request URL: /?ui_locales=en_US&nonce=67676767&token_type=Bearer&expires_in=3600&access_token=RyP_vqiveDpQltuVAx2C2ASXKkLMnjh2O8VtiC1s3UPvae6Vr07jO_-t8vPJYTjo3lmIm-CX1KRzXQutBt-cEQ&id_token=eyJraWQiOiJwcm9kLWluaXRpYWwtdG9rZW4ta2lkIiwiYWxnIjoiRVMyNTYifQ.eyJzdWIiOiItRDNGMDZMQXNWdlJ1bTQ1OElXWWxTbE5nMUJmTnlTSkJDOXhEN3otc1pzIiwiaWRwX25hbWUiOiJOVklESUEtSiIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJpZHBfaWQiOiJQRGlBaHYya0pURmVRN1dPUHFpUTJ0Ulo3bEdoUjJYMTFkWHZNNFRaU3hnIiwiaXNzIjoiaHR0cHM6XC9cL2xvZ2luLm52aWRpYS5jb20iLCJleHRlcm5hbF9pZCI6IjIxNjg4NDc5NzYxNjY4NTI3NCIsInByZWZlcnJlZF91c2VybmFtZSI6ImpvaG53Y2xhcmsiLCJjb25zZW50Ijp7InRyYWNrQmVoYXZpb3JhbERhdGEiOnRydWUsIm9wdF9pbiI6dHJ1ZX0sIm5vbmNlIjoiNjc2NzY3NjciLCJhdWQiOlsiX2dXa3A4TnZQeGM3c3ZmUkt5WEo0SXNlUXlZdXBMaFdKaU14eVB5MGdtNCIsInM6aVRVRUZ0QlNBcDZCbW9fNFpvTktPNnY2N2d3WE9ROWNTQlhWOVMzTVdYVSJdLCJ1cGRhdGVkX2F0IjoxNjIyMjQ2MjQ3LCJhenAiOiJfZ1drcDhOdlB4YzdzdmZSS3lYSjRJc2VReVl1cExoV0ppTXh5UHkwZ200IiwiZXhwIjoxNjIyMjYwNjQ3LCJpYXQiOjE2MjIyNDYyNDcsImVtYWlsIjoiam9obndjbGFya0BmcmlpLmNvbSJ9.XhQTWuqe8fJTiD4qPUTWnTPY0T8zIXljHuQ4uOnXM7R7N85EymKeJcEY_2k9li0MJ6OKxJ8gzuAqDN-GCQbsEA
17:57:33.131 - info: Event: Login Progress: Authenticating with NVIDIA server…
17:57:33.134 - info: Event: Login Progress: Login credentials retrieved successfully.
17:57:33.675 - info: Event: Login Progress: Retrieving user information…
17:57:33.681 - info: User programs URL is: https://developer.nvidia.com/api/assets/v1/current_user_sdk/programs
17:57:34.208 - info: the DevZone programs that user can access:
17:57:34.209 - info: { id: 873374, name: Accelerated Computing Developer Program }
17:57:34.210 - info: { id: 874688, name: NVIDIA Developer Program }
17:57:34.210 - info: { id: 878431, name: Technology Access Group }
17:57:34.219 - info: Event: Login Progress: Loading and processing available products…
17:57:34.232 - info: Event: Login Complete: Succeeded
17:57:34.233 - info: Retrieving Data…
17:57:34.233 - info: Processing Data…
17:57:34.258 - info: Checking for GDPR allow. gdprAllow: . client version: 1.5.0.7774. Last seen client:
17:57:34.262 - info: LastSeenSDKMClientVersion is set to 1.5.0.7774
17:57:34.263 - info: Prompting privacy dialog: isThisNewSDKMClient=true. this.gdprAllow=
17:57:43.724 - info: Event: System settings DB changed
17:57:43.731 - info: Usage and platform data collection via Google Analytics sets to Allow
17:57:43.731 - info: Telemetry: allow = Allow. isGDPRAllowed=true
17:57:43.736 - info: Initialized Telemetry for GDPR. TrackID: UA-59254929-55. UserID: 5f93c7bc-0afd-5ac6-a027-554e83498af5.
17:57:43.737 - info: Telemetry: setting custom dimensions: UserType, SDKMode, SDKMVersion External UI 1.5.0.7774
17:57:43.737 - info: Setting custom dimension: UserType - cd5, External
17:57:43.737 - info: Setting custom dimension: SDKMode - cd6, UI
17:57:43.738 - info: Setting custom dimension: SDKMVersion - cd8, 1.5.0.7774
17:57:43.747 - info: Initializing Telemetry visitor. Application: SDK Manager 1.5.0.7774. Version: 1.5.0.7774. clientMode: UI. isDevelopmentEnvironment: 0. NV User: false
17:57:43.748 - info: Initialized Telemetry for SDK Manager. TrackID: UA-59254929-54. UserID: 5f93c7bc-0afd-5ac6-a027-554e83498af5.
17:57:43.748 - info: Telemetry: setting custom dimensions: UserType, SDKMode, SDKMVersion External UI 1.5.0.7774
17:57:43.748 - info: Setting custom dimension: UserType - cd5, External
17:57:43.749 - info: Setting custom dimension: SDKMode - cd6, UI
17:57:43.749 - info: Setting custom dimension: SDKMVersion - cd8, 1.5.0.7774
17:57:43.755 - info: mainRepoUrl: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
17:57:43.761 - info: Loading data from server: l1url. Url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
17:57:44.043 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:44.046 - info: Initial product lines number before validation: 6
17:57:44.324 - info: sdkml2_drive_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/Linux/sdkml2_drive_linux.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:44.327 - info: sdkml2_sdkmanager_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/SDKMANAGER/Linux/sdkml2_sdkmanager_linux.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:44.329 - info: sdkml2_doca_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DOCA/Linux/sdkml2_doca_linux.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:44.350 - info: sdkml2_clara_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/Clara/Linux/sdkml2_clara_linux.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:44.353 - info: sdkml2_jetson_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/Jetson/Linux/sdkml2_jetson_linux.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:44.358 - info: validating product line for target OS:
17:57:44.361 - info:
17:57:44.362 - info: validating release: SDK Manager
17:57:44.362 - info: Empty devzone program id, need to validate l3 url
17:57:44.364 - info: Validate l3 url successfully
17:57:44.365 - info: Event: Login Progress: Loading and processing available products…
17:57:44.377 - info: validating product line for target OS: Linux
17:57:44.378 - info:
17:57:44.378 - info: validating release: DRIVE Software 10.0
17:57:44.379 - warn: No access to devzone program id 879192
17:57:44.380 - warn: No access to release DRIVE Software 10.0.
17:57:44.380 - info:
17:57:44.380 - info: validating release: DRIVE Software 9.0
17:57:44.381 - warn: No access to devzone program id 879192
17:57:44.381 - warn: No access to release DRIVE Software 9.0.
17:57:44.381 - info:
17:57:44.381 - info: validating release: DRIVE Software 8.0
17:57:44.381 - warn: No access to devzone program id 879192
17:57:44.382 - warn: No access to release DRIVE Software 8.0.
17:57:44.382 - info:
17:57:44.382 - info: validating release: DRIVE Software 8.0
17:57:44.382 - warn: No access to devzone program id -1
17:57:44.382 - warn: No access to release DRIVE Software 8.0.
17:57:44.382 - info:
17:57:44.383 - info: validating release: DRIVE OS 5.2.6 SDK
17:57:44.383 - warn: No access to devzone program id -1
17:57:44.383 - warn: No access to release DRIVE OS 5.2.6 SDK.
17:57:44.383 - info:
17:57:44.383 - info: validating release: DRIVE OS 5.2.3 SDK
17:57:44.383 - warn: No access to devzone program id -1
17:57:44.383 - warn: No access to release DRIVE OS 5.2.3 SDK.
17:57:44.384 - info:
17:57:44.384 - info: validating release: DRIVE OS 5.2.0 SDK
17:57:44.384 - warn: No access to devzone program id 879192
17:57:44.384 - warn: No access to release DRIVE OS 5.2.0 SDK.
17:57:44.384 - info:
17:57:44.384 - info: validating release: DRIVE OS 5.2.0 SDK
17:57:44.384 - warn: No access to devzone program id -1
17:57:44.384 - warn: No access to release DRIVE OS 5.2.0 SDK.
17:57:44.384 - info:
17:57:44.384 - info: validating release: DRIVE OS 5.1.15 with DriveWorks
17:57:44.385 - warn: No access to devzone program id -1
17:57:44.385 - warn: No access to release DRIVE OS 5.1.15 with DriveWorks.
17:57:44.385 - info:
17:57:44.385 - info: validating release: DRIVE OS 5.1.15.0 SDK
17:57:44.385 - warn: No access to devzone program id -1
17:57:44.385 - warn: No access to release DRIVE OS 5.1.15.0 SDK.
17:57:44.385 - info:
17:57:44.385 - info: validating release: DRIVE OS 5.0.10.3 SDK with DriveWorks
17:57:44.385 - warn: No access to devzone program id 876061
17:57:44.385 - warn: No access to release DRIVE OS 5.0.10.3 SDK with DriveWorks.
17:57:44.385 - info:
17:57:44.385 - info: validating release: DRIVE OS 5.0.10.3 PDK
17:57:44.386 - warn: No access to devzone program id -1
17:57:44.386 - warn: No access to release DRIVE OS 5.0.10.3 PDK.
17:57:44.392 - info: validating product line for target OS: Linux
17:57:44.393 - info:
17:57:44.393 - info: validating release: DOCA 1.0
17:57:44.393 - warn: No access to devzone program id 895349
17:57:44.394 - warn: No access to release DOCA 1.0.
17:57:44.401 - info: validating product line for target OS: Linux
17:57:44.403 - info:
17:57:44.403 - info: validating release: Clara AGX 2.2
17:57:44.403 - warn: No access to devzone program id 887788
17:57:44.403 - warn: No access to release Clara AGX 2.2.
17:57:44.403 - info:
17:57:44.403 - info: validating release: Clara AGX 2.1
17:57:44.403 - warn: No access to devzone program id 887788
17:57:44.403 - warn: No access to release Clara AGX 2.1.
17:57:44.404 - info:
17:57:44.404 - info: validating release: Clara AGX 2.0
17:57:44.404 - warn: No access to devzone program id 887788
17:57:44.404 - warn: No access to release Clara AGX 2.0.
17:57:44.404 - info:
17:57:44.404 - info: validating release: Clara AGX 1.5
17:57:44.404 - warn: No access to devzone program id 887788
17:57:44.404 - warn: No access to release Clara AGX 1.5.
17:57:44.405 - info: validating product line for target OS: Linux
17:57:44.410 - info:
17:57:44.410 - info: validating release: JetPack 4.6 EA
17:57:44.410 - warn: No access to devzone program id 879404
17:57:44.410 - warn: No access to release JetPack 4.6 EA.
17:57:44.411 - info:
17:57:44.411 - info: validating release: JetPack 4.5.1
17:57:44.411 - info: Can access to devzone program id 874688
17:57:44.411 - info:
17:57:44.411 - info: validating release: JetPack 4.5
17:57:44.411 - info: Can access to devzone program id 874688
17:57:44.411 - info:
17:57:44.411 - info: validating release: JetPack 4.4.1
17:57:44.412 - info: Can access to devzone program id 874688
17:57:44.412 - info:
17:57:44.412 - info: validating release: JetPack 4.4
17:57:44.412 - info: Can access to devzone program id 874688
17:57:44.412 - info:
17:57:44.412 - info: validating release: JetPack 3.3.3
17:57:44.412 - info: Can access to devzone program id 874688
17:57:44.412 - info: Event: Login Progress: Loading and processing available products…
17:57:44.417 - info:
17:57:44.417 - info: validating release: DeepStream
17:57:44.417 - warn: No access to devzone program id -1
17:57:44.417 - warn: No access to release DeepStream.
17:57:44.417 - info:
17:57:44.417 - info: validating release: DeepStream
17:57:44.417 - info: Can access to devzone program id 874688
17:57:44.417 - info:
17:57:44.418 - info: validating release: DeepStream
17:57:44.418 - info: Can access to devzone program id 874688
17:57:44.418 - info:
17:57:44.418 - info: validating release: DeepStream
17:57:44.418 - info: Can access to devzone program id 874688
17:57:44.418 - info:
17:57:44.418 - info: validating release: DeepStream
17:57:44.418 - info: Can access to devzone program id 874688
17:57:44.418 - info:
17:57:44.418 - info: validating release: DeepStream
17:57:44.418 - info: Can access to devzone program id 874688
17:57:44.418 - info:
17:57:44.418 - info: validating release: DeepStream
17:57:44.418 - info: Can access to devzone program id 874688
17:57:44.655 - info: sdkml2_drive_qnx.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/QNX/sdkml2_drive_qnx.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:44.659 - info: validating product line for target OS: QNX
17:57:44.660 - info:
17:57:44.661 - info: validating release: DRIVE OS 5.2.6 SDK
17:57:44.661 - warn: No access to devzone program id -1
17:57:44.661 - warn: No access to release DRIVE OS 5.2.6 SDK.
17:57:44.661 - info:
17:57:44.661 - info: validating release: DRIVE OS 5.2.3 SDK
17:57:44.662 - warn: No access to devzone program id -1
17:57:44.662 - warn: No access to release DRIVE OS 5.2.3 SDK.
17:57:44.662 - info:
17:57:44.662 - info: validating release: DRIVE OS 5.2.0 SDK
17:57:44.662 - warn: No access to devzone program id -1
17:57:44.662 - warn: No access to release DRIVE OS 5.2.0 SDK.
17:57:44.662 - info:
17:57:44.662 - info: validating release: DRIVE OS 5.1.15.0 SDK
17:57:44.662 - warn: No access to devzone program id -1
17:57:44.662 - warn: No access to release DRIVE OS 5.1.15.0 SDK.
17:57:44.974 - info: Selecting Jetson product
17:57:44.977 - info: step1 load in ms: 1216.1399999999994
17:57:44.978 - info: Web server configuration build version 1003D584J23C132DOCA is set
17:57:44.984 - info: Checking for update with mainRepoURL: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
17:57:45.187 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:45.394 - info: sdkml2_sdkmanager_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/SDKMANAGER/Linux/sdkml2_sdkmanager_linux.json has been downloaded to /home/wsprdaemon/.nvsdkm/dist successfully.
17:57:45.397 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.json
18:21:18.616 - info: cleaning up engine
I do have good HDMI. I always and only see the White screen with the Green Nvidia logo.
-
The log you shared does not help. Please directly compress the whole folder and attach it here.
-
If this Green Nvidia Logo is shown after you flashed the board, then please still get the equipment to dump the log from uart.
Wayne, if you read this thread from the start it may be more informative. As to flashing, I had a good running system in a USB SSD, so is this a pre-flashed system? Or because it failed and since only displays the green logo should I answer Auto or manual flash. With a good working system on SSD we know that I did had a good flash for a time. Now that I have the Ethernet port working well I will move from the dining room table down to the garage. I will learn how to compress the log directory and contents. Thank you for all the help. I do have my slightly older Nano working well. an I just make a copy of the OS now running from SSD, or will the system ignore a forgin build?
John
Hi John,
Please let me explain what is difference between sdkmanager and sdcard image first. And then also explain the “boot from usb ssd” case. This may be complicated if you are not that familiar with nano boot process, so please ask question if you don’t understand.
-
If you are using sdcard based jetson nano module, then there are two devices on nano module to form a fine boot. A QSPI-NOR and your sdcard. QSPI-NOR contains the bootloader while the sdcard only contains the ubuntu filesystem.
When you are trying to use Etcher to do a “flash” for your sdcard, it is just doing update for the sdcard part. Thus, the QSPI-NOR on your module never gets changed.
No matter how many times you flash a sdcard to whatever jetpack version, the QSPI-NOR still stays on the version as the pre-built version from the factory.
Then, the question is how do we update QSPI-NOR here? The answer is the sdkmanager. SDKM will install a driver package “Linux_for_Tegra” on your host machine (ubuntu16.04/18.04) and then use the tools from it to flash both the QSPI-NOR and the inserted sdcard on your nano. The old file on sdcard will be formatted and re-install new jetpack. -
For the boot from usb-ssd case, it is just replacing the role of the sdcard in above case. However, sdkmanager by default does not make your board boot from usb. Sdkmanager will only follow the sdcard flow to boot the device from sdcard. It also has no capability to install or erase anything on your usb-ssd.
To make boot from usb-ssd, you have to follow the steps in our developer guide.
Back to your original problem, the real problem here is I don’t know what is your exact setup to make current situation.
-
How did you prepare your USB-SSD? I know there are lots of users here sharing their method to make nano boot up from usb drive. Honestly, I cannot guarantee the correctness of their method. Thus, need you to share what steps you’ve followed.
-
You didn’t share any log from the device yet. So far, I only see the “symptoms”.
Without the log, every debug is just a guess. The equipment to dump boot log from uart is a must-have when debugging such boot failure problem. Honestly, stuck in boot logo is a very common error that has many reasons.
I am also not sure if you really succeed in flashing sdkmanager. Again, because of lackng the sdkm log.
/home/wsprdaemon/wsprdaemon/nvsdkm.zip
Don’t know if this will work or not.
To move OS to USB SSD I used JetsonHacksNanoBootfrom USB on github.com. This is where I stopped on the old Nano.
I then installed HPC-SDK for OpenACC,compilers,CUDA,Nsight,
not knowing that many of these were already in the 451 SDK.
Running some of the m64 compiler tests the error was given that I need CUDA 10. I went to the Web for CUDA 10 but was given the instructions for CUDA 11. This was where I was stuck. I have learned since that time that Nsight and CUDA 11 are already installed and with the proper compiler command CUDA 11 will pass. I still don’t know if this will work with OpenACC and Nsight on the Nano. There is a RF protocol decoder program in C++ that I want to profile with Nsight in the hops that I might find some improvements as I currently run 22 copies of this program for 22 channels of wave files concurrently of my older nano that is 20% faster than a PI4. They do all get done decoding the signals before the next 2 minuet cycle passes.
The new Nano failed when I tried to remove the CUDA 11 package via apt-get remove. Screen went blank. After 30 minuets I power cycled and since then I only see green Nvidia logo. all attempts to flash micro SD and USB thumb drive have not provided a good start.
nvsdkm.zip (11.9 KB)
I found the Upload Icon this time.
The recovery button (on models with a button) just shorts the recovery pin to ground. While the button is pressed (or pin is grounded) any bring up of power or reset of power puts the system in recovery mode. There is no need to keep the button pressed after power is reset or started. There is no risk or problem with doing this while connected to the host PC.
FYI, the recovery mode does not change anything, it just puts the Nano in a mode the flash software can work with.
If you’ve just set recovery mode, and the micro-B USB is connected, then on the host PC you can run this command to see all NVIDIA products on USB:
lsusb -d '0955:'
Or this to see a Nano (though it might differ for eMMC, not sure, I have the SD version):
lsusb -d '0955:7020'
The “0955:” is for all things NVIDIA, the “7020” is the Nano.
Hi John,
Do you have “logs” folder in your ~/.nvsdkm? If you successfully run the sdkmanager and install jetpack, it should have similar contents as below.
ls logs
DRIVE
JetPack_4.2.1_EA_Linux
JetPack_4.2.2_Linux_GA
JetPack_4.2_Linux
JetPack_4.4.1_Linux
JetPack_4.4_Linux
JetPack_4.5_Linux
JetPack_3.3.3_Linux_GA
JetPack_4.2.1_Linux_GA
JetPack_4.2.3_Linux_GA
JetPack_4.3_Linux
JetPack_4.4_DP_Linux_DP
JetPack_4.5.1_Linux Linux_SW
If there is no such directory on your host, then you probably didn’t install anything yet… Share us the screenshot of your sdkmanager GUI so that we can check your instructions.
Correct. I have never succeeded with SDM manager. The manager does not see my Nano. We were attempting to Use SMDManager because all other Boot (micro SD and USB failed to rebuild the Nano. I went out Tuesday and purchased a quality micro USB cable – the same result, no communications with Nano.
After you put the device into recovery mode, do you see the jetson nano (nvidia corp) in the “lsusb” command result on your host as @linuxdev’s comment?
If you’ve just set recovery mode, and the micro-B USB is connected, then on the host PC you can run this command to see all NVIDIA products on USB:
lsusb -d ‘0955:’
Or this to see a Nano (though it might differ for eMMC, not sure, I have the SD version):
lsusb -d ‘0955:7020’
Also, when board is in recovery mode, all the peripherals will be disabled and OS will not be available. Thus, if you still see anything on the screen, it means the board is not in recovery mode.
I don’t think your board has hardware defect. Sounds like just didn’t put the board into recovery mode correctly.
linuxdev was correct. After setting FC-REC to GND SDKManager sees my Nano and a download is in progress. I assume I will be asked about the Flash, Automatic or manual? I am guessing that in the past this unit has been running SDK 451 I should select Automatic? Is this correct?
John
Yes. I had the reply: Buss 003 Device 004: ID p955:7f21 NVidia Corp
Then I started the download in SDKManager
OK SDKManager finished with the Download, I assume to the micro SD card. The SDKManager exited. I powered off the Nano, removed the micro USB cable installed the keyboard dongle and powered on. I only have the green Nvidia logo. I am going to assume that the QSPY-NOR is still expecting to find the OS on the USB SSD. I will bring up SDK Manager and try again with only the SSD attached.
Well the Download to the SSD was very fast but the same results. No boot only the Nvidia logo. For both the MSD and the SSD I did a SYS RST, same result. I will send the Logs.
sdkmlogs05-30.zip (72.4 KB)
Log files from 5-30
ls from…logs…
mon@wsprd7:~/.nvsdkm/logs/JetPack_4.5.1_Linux$ ls -l
total 20
-rw-rw-r-- 1 wsprdaemon wsprdaemon 188 may 30 14:29 NV_CUDA_CROSS_HOST_COMP.log
-rw-rw-r-- 1 wsprdaemon wsprdaemon 176 may 30 14:29 NV_CUDA_HOST_COMP.log
-rw-rw-r-- 1 wsprdaemon wsprdaemon 226 may 30 14:29 NV_L4T_NVIDIA_NSIGHT_GRAPHICS_HOST_COMP.log
-rw-rw-r-- 1 wsprdaemon wsprdaemon 188 may 30 14:29 NV_L4T_NVIDIA_NSIGHT_SYSTEMS_HOST_COMP.log
-rw-rw-r-- 1 wsprdaemon wsprdaemon 186 may 30 14:29 NV_VPI_CROSS_HOST_COMP.log
wsprdaemon@wsprd7:~/.nvsdkm/logs/JetPack_4.5.1_Linux$