We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Presently, two Python modules in python_modules/common are referencing the mch22 Python module:
python_modules/common
mch22
badgePython/python_modules/common/dashboard/launcher.py
Lines 1 to 2 in 2fe3374
badgePython/python_modules/common/dashboard/home.py
Unfortunately that module is not frozen into the firmware (which I believe is the correct behavior) unless using the mch2022_defconfig:
mch2022_defconfig
badgePython/configs/mch2022_defconfig
Lines 139 to 140 in 2fe3374
which then calls
badgePython/manifests/mch2022.py
Line 1 in 2fe3374
Here was the boot traceback leading to the discovery:
ets Jul 29 2019 12:21:46 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0030,len:6608 load:0x40078000,len:14788 ho 0 tail 12 room 4 load:0x40080400,len:3792 entry 0x40080694 I (29) boot: ESP-IDF v4.4.1 2nd stage bootloader I (29) boot: compile time 13:00:45 I (29) boot: chip revision: 3 I (32) boot_comm: chip revision: 3, min. bootloader chip revision: 0 I (39) boot.esp32: SPI Speed : 40MHz I (44) boot.esp32: SPI Mode : DIO I (48) boot.esp32: SPI Flash Size : 8MB I (53) boot: Enabling RNG early entropy source... I (58) boot: Partition Table: I (62) boot: ## Label Usage Type ST Offset Length I (69) boot: 0 nvs WiFi data 01 02 00009000 00024000 I (76) boot: 1 otadata OTA data 01 00 0002d000 00002000 I (84) boot: 2 phy_init RF data 01 01 0002f000 00001000 I (91) boot: 3 ota_0 OTA app 00 10 00030000 00200000 I (99) boot: 4 ota_1 OTA app 00 11 00230000 00200000 I (106) boot: 5 nvs_key NVS keys 01 04 00430000 00004000 I (114) boot: 6 appconfig WiFi data 01 02 00434000 00080000 I (121) boot: 7 vfs Unknown data 01 81 004b4000 00339000 I (129) boot: End of partition table I (133) boot_comm: chip revision: 3, min. application chip revision: 0 I (140) esp_image: segment 0: paddr=00030020 vaddr=3f400020 size=4660ch (288268) map I (253) esp_image: segment 1: paddr=00076634 vaddr=3ffbdb60 size=052b4h ( 21172) load I (262) esp_image: segment 2: paddr=0007b8f0 vaddr=40080000 size=04728h ( 18216) load I (270) esp_image: segment 3: paddr=00080020 vaddr=400d0020 size=e04a8h (918696) map I (602) esp_image: segment 4: paddr=001604d0 vaddr=40084728 size=11054h ( 69716) load I (631) esp_image: segment 5: paddr=0017152c vaddr=400c0000 size=00064h ( 100) load I (631) esp_image: segment 6: paddr=00171598 vaddr=50000000 size=00818h ( 2072) load I (649) boot: Loaded app from partition at offset 0x30000 I (650) boot: Disabling RNG early entropy source... BADGE.TEAM E (1015) gpio: gpio_install_isr_service(449): GPIO isr service already installed Internal FatFS: File system partition definition not found! Starting app 'dashboard.home'... Traceback (most recent call last): File "boot.py", line 78, in <module> File "dashboard/home.py", line 1, in <module> ImportError: no module named 'mch22' Fatal exception in the running app!
The text was updated successfully, but these errors were encountered:
renzenicolai
No branches or pull requests
Presently, two Python modules in
python_modules/common
are referencing themch22
Python module:badgePython/python_modules/common/dashboard/launcher.py
Lines 1 to 2 in 2fe3374
badgePython/python_modules/common/dashboard/home.py
Lines 1 to 2 in 2fe3374
Unfortunately that module is not frozen into the firmware (which I believe is the correct behavior) unless using the
mch2022_defconfig
:badgePython/configs/mch2022_defconfig
Lines 139 to 140 in 2fe3374
which then calls
badgePython/manifests/mch2022.py
Line 1 in 2fe3374
Here was the boot traceback leading to the discovery:
The text was updated successfully, but these errors were encountered: