Possible Bug version 2.2.0

[alexsh1]

@anticimex Just out of curiosity - what happens if re-personalisation is not done after moving to 2.2.0? Signing fails?

[Anticimex]

@alexsh1 checksum verification for the signing backend will fail and signing will not operate

[alexsh1]

@anticimex OK, but if the GW is still on 2.1.1 and nodes are 2.2.0 it should be fine, right?

[Anticimex]

@alexsh1 if the 2.2 node has correct checksum yes. And this is shown in the debug log.

[sindrome73]

@anticimex

532/5000
I made the customization from the beginning, with MySensors 2.2.0

I followed these steps:

• The EEPROM has been deleted
• Open SecurityPersonalize.ino inserted the new Key
• loaded the scketch and it does not go

I redid the same procedure above, then EEprom deleted, SecurityPersonalize file, and loaded the scketch, but this time using Mysensors 2.1.1
And here it worked ..... The same thing I did on Several Pro Mini at 5V 16Mhz and the result is the same ..... That's why I assume there may be something wrong with 2.2.0

[Anticimex]

@sindrome73 2.2 works. At least signing. Log please.

[sindrome73]

I apologize, but I did not understand what you tell me ....

I would like to add that the script without the signature with the 2.2 version works, while the signature works only with MySensors 2.1

[Anticimex]

@sindrome73 log please.

[sindrome73]

In the evening ..... Now I'm at work and I can not

[Anticimex]

@sindrome73 no problem

[sindrome73]

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 ....

[Anticimex]

@sindrome73 log looks pretty corrupt, but I can't find any signing related messages so it would seem signing is not enabled on the node. Do you have a log from the GW? Is it also running 2.2.0?

[Anticimex]

@sindrome73 sorry, the capabilities string indicate software signing. But I don't see the backend initialization message. Could you please enable verbose signing debug?

[sindrome73]

tell me how to abbilitate the detailed signature debug .....

[Anticimex]

@sindrome73 https://www.mysensors.org/apidocs-beta/group__MySigningTroubleshootinggrp.html

[sindrome73]

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

[Anticimex]

@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.

[sindrome73]

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 !!

[Anticimex]

@sindrome73 you could try to completely disable debug on your node and observe the behavior of your gw or controller.

[sindrome73]

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 ....