Hi Jason,
yes I already did but it does not help.
in CubeCell repo we do not track the exact git commit number of the code that was forked from the original repo and unfortunately the official repo did not update the readme.md file in 2018 for many, many commits.
so if you try to find a match (to get to the original github commit number) it is very difficult.
I tried to do a search, pulling multiple revisions and doing a diff … but I can’t get a proper match.
===
if you have the original checkout of the Semtech code you should be able to do a “git log” and publish the version of the code that was ported into the CubeCell repo.
===
NOTE: I’m trying to do this because our LoRaMac code is extremely old and there are many, many fixes in the official repo, not to mention the support for security element ATECC608a in the develop branch which is MANDATORY for a REAL product.
Right now the CubeCell is good for a demo … but NOT good for a product since security is an issue !!!
LoRa/LoRaWAN requires a secure element to protect DevEUI and AppEUI … and the recommended best practice (TheThingsNetwork) is to use a dedicated secure element.