Dev Academy Bluetooth Low Energy Fundamentals with nRF7002 DK?

Hello,

I have the nRF7002 DK, which includes the nRF5340 (App + BLE cores) on-board.

The hardware requirements do not list this DK as usable for the course, which seems like it should work since it has the nRF5340 on-board.

Can I run the course examples on the nRF7002 DK and if so, what do I set the board target to in the build configuration?

The course materials just says to create a build configuration.

I'm guessing this example has to load code to both the App and Network cores, but I don't know.

I've tried setting it to nrf7002dk/nrf5340/cpuapp/ns.

When I do, a clean build generates the following build warnings.

Both cores are listed under the build config. The course does not instruct as to how I specifically flash both cores. Do I just select the "build" folder level then Flash under Actions and that automatically flashes both cores? That is my presumption.

When I do this... it seems like the flash worked as LED2 is flashing as expected, but I cannot bond to the nRF Connect server (Android).

It seems to be failing on invalid public key.

Thank you in advance.

Chris

Parents
  • Hi Chris

    Okay, so I was able to reproduce this, but it does not seem to be an issue per se for the sample, just the nRF5340 reporting that it's not able to import a key (not needed by the sample). The peripheral_lbs sample seems to do exactly what it is meant to, but with these error messages because of the connected nRF7002. I will create an internal ticket on this, but since it does seem to work as expected (you're not supposed to pair/bond to this sample) I'm not sure it will be of high priority.

    Best regards,

    Simon

    EDIT: There is indeed an issue with some configs, and a workaround is to set CONFIG_TFM_PROFILE_TYPE_NOT_SET=y in your prj.conf file. Note that this will drastically increase the memory footprint of the application, but it will fix the public key import issue.

Reply
  • Hi Chris

    Okay, so I was able to reproduce this, but it does not seem to be an issue per se for the sample, just the nRF5340 reporting that it's not able to import a key (not needed by the sample). The peripheral_lbs sample seems to do exactly what it is meant to, but with these error messages because of the connected nRF7002. I will create an internal ticket on this, but since it does seem to work as expected (you're not supposed to pair/bond to this sample) I'm not sure it will be of high priority.

    Best regards,

    Simon

    EDIT: There is indeed an issue with some configs, and a workaround is to set CONFIG_TFM_PROFILE_TYPE_NOT_SET=y in your prj.conf file. Note that this will drastically increase the memory footprint of the application, but it will fix the public key import issue.

Children
No Data
Related