* Fix filesystem mutex handling
This fixes the re-initialization of the filesystem mutex when the dyn storage
module is reinitialized. Using xSemaphoreCreateMutex would cause a memory leak
when the begin function is called multiple times and a semaphore leakage could
be caused by the re-initialization of the global fsMutex variable while the
semaphore is taken.
The fsMutex should not be taken while the logLine function is called as this
would cause a nested take of the fsMutex, which causes a deadlock.
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
* Fix hard coded littlefs in json upload
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
* Add new AP hardware support OpenEPaperLink_ESP32-PoE-ISO_AP
This is based on Olimex ESP32-PoE-ISO
https://www.olimex.com/Products/IoT/ESP32/ESP32-POE-ISO/open-source-hardware
It has a SD Card slot that is used to store all filesystem data on SD.
Use the prepare_sdcard.sh script to copy all needed data to an empty
SD card that is formatted with FAT filesystem. The AP firmware will format
the SD if an unformatted or from formatted card is used. This can be used
to intially prepare an empty SD card for usage.
For tag communication a ESP32-C6-WROOM-1(U) is used with the following
connection scheme:
ESP32-PoE-ISO | ESP32-C6-WROOM-1
---------------+------------------
GPIO5 | EN
GPIO13 | GPIO9
GPIO36 | GPIO3
GPIO4 | GPIO2
GPIO33 | GPIO24
GPIO32 | GPIO25
| GPIO8 pullup 5.1k
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
* Avoid error message log print when parsers.json is missing
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
* Workaround for IEEE802.15.4 modem stuck issue
The ESP32-C6 esp-idf based modem firmware can run into a case where it
does not receive data anymore from the tags. This can be detected when
it starts to print
"receive buffer full, drop the current frame"
and does not recover from that. In such a case a modem reset is triggered.
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
* Add OpenEPaperLink_ESP32-PoE-ISO_AP to release build
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
* Add OpenEPaperLink_ESP32-PoE-ISO_AP to condidional build
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
* Add Ethernet support
The ethernet support allows to make the network/internet connection
via LAN cable instead of WiFi. LAN is preferred, if a LAN cable is
connected and a valid IP configuration via DHCP can be obtained, WiFi
is switched off. If the LAN cable is disconnected, a fall back to
WiFi is done.
Use those defines in platform.ini for PHY settings:
ETHERNET_PHY_POWER: IO pin where the PHY can be switched of/on, can be
-1 if not used.
ETHERNET_CLK_MODE: PHY clock mode, see eth_clock_mode_t in ETH.h
ETHERNET_PHY_MDC: PHY MDC pin
ETHERNET_PHY_MDIO: PHY MDIO pin
ETHERNET_PHY_TYPE: PHY type, see eth_phy_type_t in ETH.h
Limitations:
- only DHCP is supported, no static IP configuration for LAN so far.
- If GPIO0 is used for one of the ETHERNET_CLK_MODE modes, then GPIO0
cannot be used to clear the WiFi configuration.
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
---------
Signed-off-by: Frank Kunz <mailinglists@kunz-im-inter.net>
Co-authored-by: Frank Kunz <mailinglists@kunz-im-inter.net>
So far the serial output is a mix of \r\n for println() and \n for
sprintf() and such.
This commit consolidates this to a consistent \r\n.
There should be no noticeable difference for users of terminals that
auto-substitute a sole \n to \r\n.
This will however make the serial output friendly to default behavior of
various terminal emulators like 'screen' and 'minicom'.
This commit doesn't touch anything that is not serial output and also
leaves 'ets_printf' alone just in case.
Co-authored-by: Thomas B. Rücker <thomas.ruecker@relexsolutions.com>
Pretty complex change here: pending images/commands are now queued.
A command (like LED flasher) will not overwrite a pending image anymore. Also, sending multiple preloaded images is possible.
Also works (at least, as far as I could test) in combination with Multi AP and mirroring tags ('display a copy' content type).
It you want to test this: don't forget to upload the changed files in /www (the pending icon is now displaying the amount of queued messages). Timing improvements will follow later (only one message can be transmitted every checkin. If multiple messages are queued, at this moment, you have to wait until the next checkin which takes 40-60 sec).
This comes also with the advantage of better stability if you upload multiple images to the same tag in succession. Before queuing, if was possible to replace the image between sending the pending message and the image transfer to the tag, causing md5 mismatches and instability.
Solves #47
* New hardware profile: PoE AP
- added harware profiles for C6 firmware in menuconfig
- added free PSRAM stat in webinterface
* fix(fsfree): fixed var type of freesize of FS
When an SD Card is available it is the more interesing
metric in terms of space usage. We are therefore using
it here.
Signed-off-by: Mimoja <git@mimoja.de>
To be able to store more images and never worry about running
out of storage again we are adding support of SDCards.
We are faced with two options:
1) Remove the LittleFS code
2) Allow for both FSs but increase the app partition as we run
out of space.
We have opted for 2 for two reasons:
1) Unformated SDCards can be initialized from the littleFS
2) If the SDCard and the flasher share the same SPI pins
the SDCard needs to be completely disconnected so there needs
to be a FS in that rare case.
Performance wise the SDCard is not slowing the system down.
Writing the AP db with 70 APs takes 2.5 seconds, on the SD
only 800ms. This however is SD and setup depending.
By default the SDCard is expected on pins 18,19,23 however this
is configurable via preprocessor defines.
Globally we replace LittleFS with a new pointer to the currently
used FS allowing for hotswapping where the FS pointer is not saved.
One case which is therefore not working is the SPIFSEditor which
copies the FS interally.
Signed-off-by: Mimoja <git@mimoja.de>
