-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQUEST] Backport improvements from "CC1352 Flasher" fork by the BeagleConnect project #154
Comments
FYI, there are also these additional downstream forks of that "cc1352-flasher" code which have added further improvements, ex: https://github.com/mercenaruss/cc1352-flasher by @mercenaruss as well as in turn forks of it, like: https://github.com/tube0013/tubeszb_addons/tree/main/tzb-cc2652-flasher by @tube0013 |
I'm happy to put together properly formatted pull requests for specific features. I'd rebased several times in hopes of getting things cleaned up to submit here, but I got the impression there wasn't interest in continuing to maintain it. I am only interested in cc1352 (p1/p7) flashing on Beagle platforms and making it easier to use for Beagle users, specifically with Zephyr. |
I will also be happy to help with the effort and improve the flasher. I have created a argparse PR for a start. |
FYI, tip if using Home Assistant is to check out these addons that are also reply on / are based on cc2538-bsl (or cc1352-flasher): |
@Hedda @jadonk @Ayush1325 I'm more than happy to backport all these changes back into this script! feel free to submit a PR. Could take a little time for me to check them, but will get merged eventually! |
Nice. What order should we stage updates? We recently updated to put it on pypi. |
I've been thinking I want to set some defaults based on the name or symlink of the executable script. |
@jadonk @Ayush1325 @git-developer Did you see Texas Instruments forked cc2538-bsl and are including it in SimpleLink SDK? Originally posted by @Hedda in #160 (comment)
|
Didn't see that. Thanks for the news. This is also a ping for me to work on the PRs. |
So, just for reference there are now 2 more independent flashing implementations now (mostly for cc1352p7 but can be easily extended):
|
FYI, @tl-sl has worked on a cc2538-bsl based web flasher with support for CC2674P P10 (CC2674P10) for @smlight-tech now: That webflasher depends on their "smlight_cc_flasher" project which in turn is another fork of JelmerT's cc2538-bsl project: @darkxst wrote smlight-cc-flasher is based on a heavily modified + improved fork of JelmerT's cc2538-bsl project, tTested with the new experimental SMLIGHT SLZB-07p10 Zigbee Coordinator USB adapter based in CC2674P P10 (CC2674P10) they released: PS: Please also see related issue tracker requesting support for CC2674 (CC2674P/CC2674R) and CC1354 (CC1354P) compatibility: |
BeagleConnect project has a fork of cc2538-bsl called "cc1352-flasher" written by @jadonk and they added a few improvements:
https://openbeagle.org/beagleconnect/cc1352-flasher
https://git.beagleboard.org/beagleconnect/cc1352-flasher
https://pypi.org/project/cc1352-flasher/
@JelmerT suggest you consider backporting their improvements if they do not themself submit pull requests to upstream repo.
Note! While the cc1352-flasher code is also available on GitHub it looks to be lagging behind the code in openbeagle.org repo:
https://github.com/beagleboard/cc1352-flasher
The text was updated successfully, but these errors were encountered: