Can't use private signing key starting in v1.3.0

[krog1]

After moving to v1.3.0, my build fails, because the imgtool can't find the module cbor. I see some updates for zephyr that indicate cbor.py is now required, and it's included in the v1.3.0 toolchain directory (v1.3.0/toolchain/opt/bin/Lib/site-packages/cbor/cbor.py) but the build isn't seeing it. Copying the cbor.py file to the bootloader/mcuboot/scripts directory fixes the issue.

Is there an environment variable that I need to set somewhere? It seems like I need to update the Python path somehow, but I don't see any reference to that in the ncs documentation.

Thanks,

Chris.

[Didrik Rokhaug]

Hi.

Did you open the terminal from the Toolchain Manager, or did you open it "directly" from Windows?

Best regards,

Didrik

[krog1]

I'm building from Segger Studio, version 4.52. I'm opening it from the Windows Start menu.

Thanks,

Chris.

[Didrik Rokhaug]

The Toolchain Manager sets up a virtual environment, which lets it provide fixed versions of tools you might also have installed on your computer.

However, for this to work, you have to open SES or the terminal from the Toolchain Manager.

If you do that, the necessary paths should be set, so that SES finds the cbor package.

[krog1]

OK, thanks. The "Open IDE" button doesn't actually show up for me on the Toolchain Manager, but I may need to reinstall everything. I'll try that when I get a chance this week.

Thanks,

Chris.

[Didrik Rokhaug]

krog1 said:

The "Open IDE" button doesn't actually show up for me on the Toolchain Manager

 Could you take a screenshot of what you see?

This is how it looks like for me:

Note that the number of versions might be different, depending on which versions you have installed.

You can also try "Ctrl+r" to re-load the application. That might help.

[krog1]

Hi, thanks for the response Didrik.

I tried the ctrl-R, but no change. I updated the toolchain and the SDK, but no change. Here's the screenshot:

[Didrik Rokhaug]

That's interesting. I'll report this to our developers.

Could you also check if the "down arrow button" works as it should?

From there, you should also be able to open a command prompt (cmd or git bash), which should let you build from the command line.

Also, what version of the Toolchain Manager are you using?

Another thing you can check is if you have SES installed in the toolchain folder:

Open the folder used by the Toolchain Manager, navigate into v1.3.0/toolchain, and you should see a folder called segger_embedded_studio, which should look similar to the folder where you installed SES manually.

[krog1]

Didrik,

The drop-down menu is the same as your screenshot. I tried running west build from the command line prompt, but CMake is failing a test build with "unrecognized option '--major-image-version'". I suspect I have an environment variable set wrong.

I'm using v0.7.1 for the toolchain manager. nRF Connect doesn't have an "Update" button showing, so I'm assuming that's the latest one.

I have the segger_embedded_studio folder in the toolchain directory, and if I run the SEGGER Embedded Studio in the toolchain directory, everything builds properly even if I remove the cbor.py file I copied over.

I just created a start menu shortcut to the segger executable in the toolchain directory, and it seems to work fine. I'll need to change this every time I upgrade the toolchain, but that's not a big deal.

If the devs need any help debugging the "Open IDE" issue on the toolchain manager I'm happy to help, but I'm good with this solution for now.

Thanks,

Chris.