Connectivity, WiFi and other issues

[lu7did]

Question over e-mail by Charudatt

some differences observed in v90 firmware with debug on-board

• the Debug listing are not the same between the use of Si4732/CA2003
• It does not show logging onto the WiFi and getting the time from NTP server as it used to show in the previous Listing
• EEPROM does show the WiFi Credentials though
• Setting the time zone to 0 does not show the UTC time on the display , as I feel it simply does not log onto the netwrok
• Request - Please display the I2C status of the Si5351 also like shown for the Rx chip if used.

How do I change the default frequency from 70740 to 140740 ?

[lu7did]

some differences observed in v90 firmware with debug on-board

• the Debug listing are not the same between the use of Si4732/CA2003The code is different, therefore the traces might differ. Remember the DEBUG clause must be activated for the trace to occur, it's de-activated in the repository code. 

* It does not show logging onto the WiFi and getting the time from NTP server as it used to show in the previous Listing

The standard source code at the repository is for the Raspberry Pico and not the Raspberry Pico W, therefore all WiFi related functions are disabled by default,you might activate the support for the Raspberry Pico W uncommenting the sentence //#define RP2040W             1  //Comment if running on a standard Raspberry Pico (non Wireless)   * EEPROM does show the WiFi Credentials though_ Yes, because of the above, they are stored but not used. 

* Setting the time zone to 0 does not show the UTC time on the display , as I feel it simply does not log onto the netwrok

Nope, because of the above NTP doesn't connect to the network, with the Raspberry Pico standard the only time available is the manual synchronization. 

* Request - Please display the I2C status of the Si5351 also like shown for the Rx chip if used. Please log in as an enhancement for future implementation.

How do I change the default frequency from 70740 to 140740 ?

You should change it while the firmware is running and it will be stored in the EEPROM for the next power up, it will be reversed when you flash code again though.For a permanent change you should change the definition to the frequency of your wish. unsigned long freq = 7074000UL;  I'll post this note as a question in GitHub in case any other had a similar problem.