Bluetooth: Controller: Receiving Periodic Advertising Reports with larger AD Data post v3.0.0-rc2

[GatCode]

Hi everyone,
I've discovered that the periodic advertisement implementation is broken on v3.0.0-rc2 and rc3 - in more detail it breaks as soon as you set the periodic advertisement data to more than 30 bytes on the sender side. As you can see in this video, I basically executed the samples (periodic_adv and periodic_sync) on two nrf52840dk's and only changed the advertisement data size and commented out some print statements on the receiver side. If you now look at the received data (right side on the video), you can see that in rc1, everything looks good and comes in at a certain pace but as soon as I flash the rc2, the periodic advertisements sometimes come in and sometimes not. Also in rc2, the periodic advertisements stop completely after some time.

[carlescufi]

@GatCode thanks for the report. Could you try bisecting to find the exact commit that introduced the regression please?

[GatCode]

@carlescufi, sure - the last working commit was 93d6d1e - therefore faa89c7 introduced the bug

[cvinayak]

@GatCode Please set the correct value for CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX in your application if you want longer than the Bluetooth minimum AD data size of 31 bytes to be received.