So I just got past the hurdle I had when trying to do extended advertising in the following support thread, and now I have a new problem along the same lines:
Now that I believe I can get extended advertising working, I set CONFIG_BT_EXT_ADV=y in my proj.conf file to start adding in code to do that, but before proceeding with the extended advertising firmware I wanted to double check to see if legacy advertising was still working with this CONFIG enabled - and it does NOT work.
Now i'm getting the same -5 return code error when I call bt_le_adv_start() that I got when trying to do extended advertising before.
I've gone back and forth a couple times now to make sure I'm not doing something else wrong, and if that CONFIG line is present, legacy advertising does not work. If it's not present, it does work (bt_le_adv_start returns 0 and I can see the device start advertising from the nRF Connect app on my phone).
Maybe the version of hci_rpmsg that gets loaded into the network core of the nRF5340 can only handle either extended advertising or normal but not both? What all changes when CONFIG_BT_EXT_ADV=y is in the .conf file?
The product I'm designing is supposed to be a generic Bluetooth interface device so my customer may send commands to enable either type of advertising, so I need to be able to turn on either one when commanded to.
Thanks,
Glen