Skip to content

Arduino nRF52 board from vendor velleman unkown board ? #12

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

Closed
cybernout opened this issue Aug 26, 2018 · 3 comments
Closed

Arduino nRF52 board from vendor velleman unkown board ? #12

cybernout opened this issue Aug 26, 2018 · 3 comments
Labels
topic: documentation Related to documentation for the project

Comments

@cybernout
Copy link

cybernout commented Aug 26, 2018

does not know the arduino uno board from vendor velleman,

output From Arduino Ide :

Board Info:

BN: Arduino/Genuino Uno
VID: 2341
PID: 0043
SN: 856343138393515001E0

ouput from arduino-cli ( 64 bit linux , ubuntu 18.04 LTS ):

$ ./arduino-cli board list
FQBN    Port        	ID       	Board Name
    	/dev/ttyACM0	2341:0043	unknown   

so compile fails as well output :

$ ./arduino-cli compile --fqbn arduino:nrf52 /home/yellabs/Arduino/MySketch
Fully Qualified Board Name has incorrect format.

core files are present :

$ ./arduino-cli core list
ID                	Installed	Latest	Name                
arduino:nrf52     	1.0.2    	1.0.2 	Arduino nRF52 Boards
sandeepmistry:nRF5	0.5.1    	0.5.1 	                 

please take a look and see if you can give advise or fix

@cybernout
Copy link
Author

cybernout commented Aug 26, 2018

i leave it here if some one else has this issue, but you could remove it, its solved by updating the arduino IDE , output now ,

$ ./arduino-cli core list
ID                	Installed	Latest	Name                
arduino:avr       	1.6.21   	1.6.21	Arduino AVR Boards  
arduino:nrf52     	1.0.2    	1.0.2 	Arduino nRF52 Boards
sandeepmistry:nRF5	0.5.1    	0.5.1 	

i can then compile without any problems to ,

./arduino-cli compile --fqbn arduino:avr:uno /home/yellabs/Arduino/MySketch
Downloading missing tool: builtin:[email protected]
builtin:[email protected] downloaded                                                                                                                 
Installing builtin:[email protected]
Sketch uses 928 bytes (2%) of program storage space. Maximum is 32256 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 2039 bytes for local variables. Maximum is 2048 bytes.

@cmaglie
Copy link
Member

cmaglie commented Aug 30, 2018

I guess that the original problem was the wrong FQBN:

$ ./arduino-cli compile --fqbn arduino:nrf52 /home/yellabs/Arduino/MySketch

you used arduino:nrf52 that is not a full FQBN because it has the platform provider (arduino) the architecture (nrf52) but NOT the board.

In your second post instead you used arduino:avr:uno that correctly refers also the board used uno.

@cmaglie cmaglie added the topic: documentation Related to documentation for the project label Aug 30, 2018
@JoannaBro
Copy link

I had the same problem. The arduino:nrf52 platform supports only one board - Arduino Primo and to use it, you should call the following command:
$ ./arduino-cli compile --fqbn arduino:nrf52:primo /home/yellabs/Arduino/MySketch.

per1234 pushed a commit that referenced this issue Nov 16, 2020
[CM-177] Change library name and bearSSL includes
per1234 added a commit that referenced this issue Aug 9, 2021
per1234 added a commit that referenced this issue Dec 7, 2022
…C encrypted PKS #12

The "Check Certificates" GitHub Actions workflow uses OpenSSL to check for problems with the project's signing
certificates.

Certificates exported to PKS #12 archive files using older tools may have been encrypted using the RC2-40-CBC algorithm.

Due to the availability of more secure modern alternatives, default support for RC2-40-CBC encryption was dropped in
OpenSSL 3.x

The macOS signing certificate uses this RC2-40-CBC encryption.

The "Check Certificates" GitHub Actions workflow runs on the `ubuntu-latest` runner. Previously, this runner used Ubuntu
20.04. This has now changed to Ubuntu 22.04. With the operating system update came an OpenSSL update from 1.1.1f to
3.0.2. This caused the workflow runs to fail on the macOS certificate job:

Error outputting keys and certificates
80FBB0C5087F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()

Even though no longer done by default OpenSSL still supports RC2-40-CBC encryption in its "legacy" provider. So
compatibility with the certificate is restored by adding the `-legacy` flag to the openssl commands.
per1234 added a commit that referenced this issue Dec 7, 2022
…C encrypted PKS #12

The "Check Certificates" GitHub Actions workflow uses OpenSSL to check for problems with the project's signing
certificates.

Certificates exported to PKS #12 archive files using older tools may have been encrypted using the "RC2-40-CBC"
algorithm.

Due to the availability of more secure modern alternatives, default support for RC2-40-CBC encryption was dropped in
OpenSSL 3.x.

The macOS signing certificate uses this RC2-40-CBC encryption.

The "Check Certificates" GitHub Actions workflow runs on the `ubuntu-latest` runner. Previously, this runner used Ubuntu
20.04. This has now changed to Ubuntu 22.04. With the operating system update came an OpenSSL update from 1.1.1f to
3.0.2. This caused the workflow runs to fail on the macOS certificate job:

Error outputting keys and certificates
80FBB0C5087F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()

Even though no longer done by default, OpenSSL still supports RC2-40-CBC encryption via its "legacy" provider. So
compatibility with the certificate is restored by adding the `-legacy` flag to the `openssl pkcs12` commands.
per1234 added a commit that referenced this issue Dec 7, 2022
…C encrypted PKS #12 (#2002)

The "Check Certificates" GitHub Actions workflow uses OpenSSL to check for problems with the project's signing
certificates.

Certificates exported to PKS #12 archive files using older tools may have been encrypted using the "RC2-40-CBC"
algorithm.

Due to the availability of more secure modern alternatives, default support for RC2-40-CBC encryption was dropped in
OpenSSL 3.x.

The macOS signing certificate uses this RC2-40-CBC encryption.

The "Check Certificates" GitHub Actions workflow runs on the `ubuntu-latest` runner. Previously, this runner used Ubuntu
20.04. This has now changed to Ubuntu 22.04. With the operating system update came an OpenSSL update from 1.1.1f to
3.0.2. This caused the workflow runs to fail on the macOS certificate job:

Error outputting keys and certificates
80FBB0C5087F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()

Even though no longer done by default, OpenSSL still supports RC2-40-CBC encryption via its "legacy" provider. So
compatibility with the certificate is restored by adding the `-legacy` flag to the `openssl pkcs12` commands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: documentation Related to documentation for the project
Projects
None yet
Development

No branches or pull requests

3 participants