Hello,
regarding PinTool v6 (WIN64 version: Pins_Tool_for_i.MX_Processors_v6_x64.exe)
I would like to create a new configuration for i.MX6ULL processor, but available default processors are only i.MX 6Quad and i.MX RT.
How to load or import i.MX6ULL processor and package data?
best regards
Timo
Hello Timo,
The information for all the supported packages is fetched from the repositories on demand, so please make sure that the tool has internet access and setup firewalls so that the tool can fetch the processor’s information.
You should be able to see the i.MX6ULL this way. Please let us know if the problem continues.
Regards,
The problem still occurs...
- the PC has internet access, every other internet connection works fine
- the pin tool runs with local admin rights
- after "check for update" only "No updates for the current installations have been found".
- If I perform "update/download" over the data manager nothing happens exept a short popup "operation in progress".
- under "preferences" I tried the options "proxy connection = direkt" and also "native"
- under "preferences" I tried the options "processor data update = "auto" and also "manuel"
So obviously it is not possible to download the repositories on demand over the implemented tool functionality.
Is there an option to download the repository over a different way? If yo send me an URL I can try by browser
best regards
Timo
ahh, I found an error log under "help":
"
!MESSAGE Connection to http://mcuxpresso.nxp.com/staticdata/updates/imx_6.0/p2.index failed on sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Retry attempt 0 started
!STACK 0
javax.net.ssl.SSLHandshakeException: ......
.
.
.
"
Hello Timo Pirrung,
I checked with our experts and they suspect that the problem with v6 may be related to the Java environment and they suggested to try the solutions on the following links:
http://magicmonster.com/kb/prg/java/ssl/pkix_path_building_failed.html
If you try these fixes please let us know of your findings.
Regards,