GOLIOTH SAMPLE HARDCODED CREDENTIALS not working?

Golioth Cloud Help
1

Description

I’m trying to build the Conexio Golioth project Hello. When I build it now I get these errors with the hardcoded credentials like the KCONFIGs aren’t accepted anymore?

Steps to Reproduce

C:/ncs/v2.9.1/conexio-firmware-sdk/samples/conexio_stratus/golioth_samples/hello/prj.conf:3: warning: attempt to assign the value ‘y’ to the undefined symbol GOLIOTH_SAMPLE_HARDCODED_CREDENTIALS

C:/ncs/v2.9.1/conexio-firmware-sdk/samples/conexio_stratus/golioth_samples/hello/prj.conf:52: warning: attempt to assign the value ‘“stratusPro_nrf9151@conexio-stratus”’ to the undefined symbol GOLIOTH_SAMPLE_PSK_ID

C:/ncs/v2.9.1/conexio-firmware-sdk/samples/conexio_stratus/golioth_samples/hello/prj.conf:53: warning: attempt to assign the value ‘“8ef15237651d0a82f28edb853592f6f9”’ to the undefined symbol GOLIOTH_SAMPLE_PSK

error: Aborting due to Kconfig warnings

Expected Behavior

It would build.

Actual Behavior

It does not build.

Environment

Zephyr 2.9.1 with Golioth 0.18.

Logs and Console Output

C:/ncs/v2.9.1/conexio-firmware-sdk/samples/conexio_stratus/golioth_samples/hello/prj.conf:3: warning: attempt to assign the value ‘y’ to the undefined symbol GOLIOTH_SAMPLE_HARDCODED_CREDENTIALS

C:/ncs/v2.9.1/conexio-firmware-sdk/samples/conexio_stratus/golioth_samples/hello/prj.conf:52: warning: attempt to assign the value ‘“stratusPro_nrf9151@conexio-stratus”’ to the undefined symbol GOLIOTH_SAMPLE_PSK_ID

C:/ncs/v2.9.1/conexio-firmware-sdk/samples/conexio_stratus/golioth_samples/hello/prj.conf:53: warning: attempt to assign the value ‘“8ef15237651d0a82f28edb853592f6f9”’ to the undefined symbol GOLIOTH_SAMPLE_PSK

error: Aborting due to Kconfig warnings

Attempts to Resolve

I can’t think of any to try.

2

@wischmi2 yes, hard coded credentials were removed in v0.18.0. Shell commands can be used instead.

3

Are there instructions on how to do this for the Conexio Stratus 9161?

4

I’m building the Conexio version of the Golioth Hello code but I believe he assumes we can use the hardcoded credentials. When I try to build the Golioth version of the Hello program it crashes and gives me MBEDTLS_PK_C defined, but not all prerequisites.

This issue is specifically called out in a Golioth issue of the v18 code.

This issue is closed but there is no information on what the solution was or how to fix it.

5

Hey @wischmi2,

Just a heads-up, the Conexio documentation is based on the Golioth Zephyr SDK, which was deprecated as of July 31, 2024, so it’s no longer up to date and shouldn’t be used as a reference.

Instead, use the Conexio Firmware SDK GitHub repo, particularly the golioth_samples/hello example. This sample is using the newer Golioth Firmware SDK, along with NCS v2.9.0.

They’re not yet on the latest Golioth Firmware SDK (v0.18.1), so for now, I recommend you try building the golioth_samples/hello example as-is from the Conexio Firmware SDK. Just make sure you’re using the correct versions: NCS v2.9.0 and Golioth Firmware SDK v0.17.0.

Hardcoded Golioth credentials are supported in Golioth Firmware SDK v0.17.0, so you’re good on that front.

Additionaly to be aware of, you’re currently trying to use Golioth Firmware SDK v0.18.0, which expects NCS v3.0.1, while you’re still on v2.9.1, so there’s a version mismatch.

7

@marko, thanks for the assist here with the Conexio SDK.

@wischmi2 , yes, currently the conexio SDK sample for Golioth is still using the Golioth Firmware SDK (v0.17.0 ) as it is on NCS v2.9.0 atm. I will upgrade the Conexio SDK later to NCSv3.0.1 and to the latest Golioth SDK as well. It’s hard to keep up with the NCS releases every month :frowning:

Reach out to Discord if the issue persists with the current Conexio SDK + Golioth.

8

Hi Rajeev, I was able to get the code building by going back to 0.17.0 Golioth sdk. Thanks for the info from everyone!

1 Like
9

@wischmi2 glad to hear that its up and running now.