CC1101 RF module failed about ithowifi HOT 17 CLOSED

You just gave the logging of the init process ;-)
What happens is that if the module is not working or one of the Power and/or SPI pins are not connected the module won't initialise. The firmware detects this and logs the message you copied. There is one other pin that cannot be checked this way but that will result in a good init but remote signals won't be processed.

from ithowifi.

I believe I found it. There was a compiler directive not clean-up completely which resulted in an SPI pin not being set as output. This only manifests itself after a cold start.... so upgrade would go fine and the CC1101 module would work just fine but after a powercycle the CC1101 module is not detectable anymore. pfff, this was a nasty one.
Could you try this firmware file?
nrgitho-hw2-v2.2-rc2.bin.zip

from ithowifi.

Great catch!
I saw the changes but didn't link them to this issue.

from ithowifi.

This is the case since the upgrade to beta 10? Or are you not sure?
Otherwise maybe a good idea to revert back to the previous version just as a test. If that doesn't work the only thing that I can come up with is that somehow the CC1101 module failed or the connection to the module failed. In that case I will send you a replacement module.

from ithowifi.

I'm not sure if it's since version beta 10.
Let me revert back to an older version to rule out if it's just beta 10.
Is there a way to retrieve logging of the init process of the CC1101 module?

from ithowifi.

I mean a more detailed logging 😛
Ok, so if dust of my scope I could try to see if the it's a connection issue. I'll look for the data sheets of the CC1101 module to guide me.
Does the Attiny only handle the init of the Itho or also the init of the CC1101 module?

from ithowifi.

I can reproduce it, beta9 is working just fine.... somehow, don't know where but I implemented a bug.....

from ithowifi.

Let's look tomorrow 😊

from ithowifi.

A recompile of the same source seems to 'fix' the issue. I'm afraid I made a mistake somewhere and selected the wrong build environment for the final build of beta10, doh!
2.2-rc1 is the version you can try to see if this fixes your issue.

edit: btw 'tomorrow' has become today :P

from ithowifi.

edit: btw 'tomorrow' has become today :P

That happens every day ;)

from ithowifi.

Sorry to tell you..........
Setup: init of CC1101 RF module failed
logfile0.current.log

from ithowifi.

grmbl.... i'll investigate further. Could you please downgrade to beta9 and see if the init works again with that version. That at least rules out a hardware issue then.

from ithowifi.

Let's look at the code changes......beta 9 is OK
logfile0.current.log

from ithowifi.

This afternoon I looked at the delta between beta 9 and 10 and could find a lead.
How did you find it?

The new bin is OK

2163 N: System boot, last reset reason: POWERON_RESET
2182 N: HW rev: 2, FW ver.: 2.2-rc2
4240 N: WiFi: connection successful
4307 N: WiFi info:
4326 N: Mode:STA
4345 N: Status:3
4364 N: IP:192.168.41.149
4433 N: Setup: Virtual remote ID: 18,142,112
4471 N: Setup: Alternative SHT30 sensor found
4507 N: Setup: init of CC1101 RF module successful
5991 N: MQTT: connected, System config: 1
6069 N: Webserver: started
6089 N: mDNS: started
6109 N: Hostname: nrg-itho-8e70
6131 N: Setup: done

from ithowifi.

This afternoon I looked at the delta between beta 9 and 10 and could find a lead.
How did you find it?

I removed '#include "hardware.h"' with commit 92fdcb0 which is actually not really used anyway but forgot to remove

Apparently only a cold boot resets the pin regs of the ESP32, so an upgrade from beta9 to beat10 would first just work fine.
That set me on the wrong foot a few times but after a lot of trying I could narrow it down to the mentioned commit.

The new bin is OK

great!

from ithowifi.

I saw the changes but didn't link them to this issue.

My neither but luckily time and effort solves all these kind of things :)

from ithowifi.

solved with 2a65bd6

from ithowifi.