1 of 1 people found this helpful
The main issue you are seeing here is due to a documentation error in the "Example 1" listing in Section 3.4.3 of the Rev. *C EZ-Serial User Guide (latest available online as of this moment). The bit value 0x01 for the "flags" value on the SAP command actually configures automatic advertisement on boot/disconnect, while the bit value 0x02 is required to enable custom advertisement content. If you use the command "SAP,F=2" instead of the one shown in the document, EZ-Serial will correctly use custom content. The bitfield values shown in Section 22.214.171.124 are correct.
It also appears that you have combined this example snippet with the "Example 2" listing in Section 3.4.1, where the actual advertisement parameters (not the content) are changed. This is not necessary in order to use custom advertisement data; you can simply use "/A" command with no other arguments. However, your output highlights a different issue that was recently discovered: the stack API command called internally by the "gap_start_adv" API command has at least one outcome which returns no error but which apparently does not trigger the start of advertising. This issue is currently being investigated, but it can be avoided by using argument combinations that always fall within correct bounds and including the correct "Flags" field in advertising payload data where applicable.
The User Guide will be updated to clearly describe all valid bounds and to show examples which only fall within these limits. The firmware itself will also be updated to validate all command arguments even if the underlying stack API call does not. This will be part of the upcoming v1.1 release.
In summary, try the following:
Jeff. I will try. I'm novice so far and wasn't sure what settings might be culprit.
I also think there is typo in Table 3-8 : 2nd line : Field Descrip ... should read "Length: 5 bytes".
Good catch on the Length value in Table 3-8. You are correct that this should be 5 bytes instead of 3.