I do no want to "pollute" the forum with a non-question topic, and given my announcement is very related to this topic, I'll post it as a comment here.
Some weeks ago I began analyzing the format of nRF8001 setup messages, and I think I made enough progress to make my "work in progress" public. So far I have a Python script for showing byte-to-byte differences between setup data from two nRFgoStudio reports (i.e. those ublue_setup.gen.out.txt files created when generating services.{c,h} files) and another tool for extracting the setup data from the report file and dumping it in human readable format.
Note that my goal is not to write a full featured tool like nRFgoStudio, but simply to fully understand what happens "under the hood" during setup. That said, anyone is free to customize the tool for other purposes.
My short term plans:
finish analyzing the remaining fields (i.e. those related to pipes and 128-bit UUIDs).
write more tools that help analyze the message format
I do no want to "pollute" the forum with a non-question topic, and given my announcement is very related to this topic, I'll post it as a comment here.
Some weeks ago I began analyzing the format of nRF8001 setup messages, and I think I made enough progress to make my "work in progress" public. So far I have a Python script for showing byte-to-byte differences between setup data from two nRFgoStudio reports (i.e. those ublue_setup.gen.out.txt files created when generating services.{c,h} files) and another tool for extracting the setup data from the report file and dumping it in human readable format.
Note that my goal is not to write a full featured tool like nRFgoStudio, but simply to fully understand what happens "under the hood" during setup. That said, anyone is free to customize the tool for other purposes.
My short term plans:
finish analyzing the remaining fields (i.e. those related to pipes and 128-bit UUIDs).
write more tools that help analyze the message format
