-
-
Notifications
You must be signed in to change notification settings - Fork 897
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
Add ATTiny85 support (#1382) #1508
base: development
Are you sure you want to change the base?
Conversation
Add support to hwCPUFrequency Add support to hwCPUTemperature
Different temperature offset
Butler never emailed the patch file to fix the coding style errors like he said he would. Probably due to the following: Slack Send Pipeline step running, values are - baseUrl: , teamDomain: mysensorscore, channel: #jenkins, color: danger, botUser: false, tokenCredentialId: slack_token, notifyCommitters: false, iconEmoji: , username: , timestamp: |
CI seems to be broke? |
@dfleck I tested this patch against the latest 2.3.2 and there is a problem ... if you could take a look at it.
|
I just realized you are using the dev branch. I'll try that out. |
I tested this on the dev branch. The diff applies just fine. But I am getting errors in a generic sketch with Sketch:
Errors:
I'm using https://github.com/SpenceKonde/ATTinyCore if that makes a difference. |
Fix sense on a couple of if defs
Sorry. I messed up. It is fixed now and tested with a few different processors now. |
I'm able to apply the patch now. Here is the sketch I'm testing with:
Here is the output on the gateway if anyone would like to review it:
Another smaller issue though, I'm getting the following error unless I'm using
|
The ATTiny85 doesn't have a "real" serial port, just a shift register. So the chip libraries don't have a serialEventRun() function. I've seen some sketches include a line to weak link serialEventRun() but I chose to force a MY_DISABLED_SERIAL so the developer has a reminder they need to use software serial or some such workaround. Besides, after you add a radio there isn't much in the way of leftover pins for serial plus whatever your monitoring :-). The presentation message failing the first time it is sent is a bit beyond my understanding of MySensors. I would apply Butler's script but I never receive them. |
I'm thinking the FAILs there are because I'm using a gateway on v2.3.2 and my testing device was on dev (with these patches). Not 100% though. Just a thought. I'm not really sure how compatible the two versions are supposed to be. |
I don't have a good way to diagnose this (I end up taking down my home automation MySensor interface to look at the gateway). I run different versions from the gateway because I don't want to reflash all of my devices every upgrade and it seems to work, but I wouldn't know if there was a temporary failure. I have no clue how compatible different versions are supposed to be. On top of that my ATTiny85 development board has stopped working. Ugh! |
I think you might be right. I don't think I applied #1381 along with your patch that time. I'll have to retry it. |
All this request really does is "fix" serialEventRun(), implement HW frequency (which fixes a bunch of compile errors from different timer names), and implement HW temperature. I would be amazed if it had any impact on the wireless protocol. |
Add ATTiny85 support (#1382)
Fix MY_DISABLED_SERIAL on AVR (#1505)
Add support to hwCPUFrequency
Add support to hwCPUTemperature