Possible Bug version 2.2.0
-
Here I am at home .... I proceeded to redo the procedure and this sot is the log ....
I had to put an image because the last signs that mida I can not copy them as text ....
@sindrome73 sorry, the capabilities string indicate software signing. But I don't see the backend initialization message. Could you please enable verbose signing debug?
-
tell me how to abbilitate the detailed signature debug .....
-
tell me how to abbilitate the detailed signature debug .....
-
Here is the log with the Debug signed abbreviation.
I specify that I had to disable // # define MY_DEBUG because the scketch is too big
-
Here is the log with the Debug signed abbreviation.
I specify that I had to disable // # define MY_DEBUG because the scketch is too big@sindrome73 signing messages look sane. But the logs look very corrupt. It also looks like the sketch crashed and restarted so I suspect you are running out of stack space. The arduino IDE reports and warns about memory usage and I suspect you get a warning on that.
-
Here is the log with the Debug signed abbreviation.
I specify that I had to disable // # define MY_DEBUG because the scketch is too big@sindrome73 you could try to completely disable debug on your node and observe the behavior of your gw or controller.
-
Yes indeed I have already said this !! So true that to have the DEBUG of the signature I had to disable the DEBUG.
But with this same script, and going to Mysensors 2.1 it works !!
@sindrome73 well, 2.2.0 could be requiring more memory than 2.1. You can compare since the IDE reports exactly how much memory is used.
-
But it is the same with both 2.2 and 2.1.
With Arduino Pro Mini, enabling the signature debugging must be disabled because it exceeds counque the maximum available memory ....... -
Ok .... Tomorrow I'll do it ..... But it will be difficult to have the Gateway Log because with the signature enabled, the sketch is very large, and does not allow me to activate the Debug ....
@sindrome73 you could see in your controller if communication gets though. I could see in the node log that signing handshaking takes place. So I am sure your problem is memory use. You need to reduce the size of your sketch. Or get more powerful hardware to support the features you want to use.
-
Ok tomorrow calmly I will make these changes and update you .... A Tomorrow, and thanks for now .....
-
Ok tomorrow calmly I will make these changes and update you .... A Tomorrow, and thanks for now .....
@sindrome73 I'm off to bed as well. Good night and we will figure something out later on.
-
Ok tomorrow calmly I will make these changes and update you .... A Tomorrow, and thanks for now .....
@sindrome73 You can try to load a default sketch from examples with signing to make sure everything is working fine.
If you are out of memory, strange things may happen. -
Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)
-
@anticimex I must admit that in the world of ESP32 or SAMD I find atmega328p memory restriction more and more an issue. Its ok for 1 sensor and signing, but on some nodes I have 3-4 sensors and debugging and signing have to be disabled due to memory constrains.
BTW, some nodes do behave strangely even when you approach memory limit.
Having said that, I think we need to establish if @sindrome73 node is working fine - a default sketch plus signing would reveal it.
-
@anticimex I must admit that in the world of ESP32 or SAMD I find atmega328p memory restriction more and more an issue. Its ok for 1 sensor and signing, but on some nodes I have 3-4 sensors and debugging and signing have to be disabled due to memory constrains.
BTW, some nodes do behave strangely even when you approach memory limit.
Having said that, I think we need to establish if @sindrome73 node is working fine - a default sketch plus signing would reveal it.
@alexsh1 sensors behave strange because stack space is consumed.
Regarding signing and 2.2.0, I know for a fact it works, and I have tested it on atmega328p. But sure, trying with the secure actuator sketch should help reveal if the problem lies with the GW. -
Hello!! Sorry if I'm late.....
So I tried to do the checks as suggested .....If I load the schetck with Mysensors Ver 2.1 the Arduino IDE gives me 28620 Bytes used 93% of the space
If I load the schetck with Mysensors Ver 2.2 the IDE of Arduino gives me 29310 Bytes used 95% of the space
So it could be a problem of space and therefore makes my Arduino Pro unstable .....
Tomorrow I'll try to load the same Scketch on An Arduino Uno that should have a little more space ..... I keep you updated on the developments -
Hello!! Sorry if I'm late.....
So I tried to do the checks as suggested .....If I load the schetck with Mysensors Ver 2.1 the Arduino IDE gives me 28620 Bytes used 93% of the space
If I load the schetck with Mysensors Ver 2.2 the IDE of Arduino gives me 29310 Bytes used 95% of the space
So it could be a problem of space and therefore makes my Arduino Pro unstable .....
Tomorrow I'll try to load the same Scketch on An Arduino Uno that should have a little more space ..... I keep you updated on the developments@sindrome73 anything above 90% puts you well into the danger zone. Stack space is what is left after linker has placed the symbols. And the atmega328p has little ram so less than 10% of that ram is not much for the stack. I don't have the numbers of the library worst case stack usage but it depend heavily on what features you use and in the order they are used, and so on.
-
Hello!! Sorry if I'm late.....
So I tried to do the checks as suggested .....If I load the schetck with Mysensors Ver 2.1 the Arduino IDE gives me 28620 Bytes used 93% of the space
If I load the schetck with Mysensors Ver 2.2 the IDE of Arduino gives me 29310 Bytes used 95% of the space
So it could be a problem of space and therefore makes my Arduino Pro unstable .....
Tomorrow I'll try to load the same Scketch on An Arduino Uno that should have a little more space ..... I keep you updated on the developments@sindrome73 Try to load any sketch from MySensors examples just to see if everything is working fine with v2.2.0. If you are running out of memory its a good practice to try the sketch on Mega or SAMD (more cpu+memory)
