@ajb2k3 said in Issue with Port C (UART) of M5Stack Fire (Finger unit OK but GPS No Good):
@liemph Try connecting the m5stack to a pc and opening a terminal connecting to the M5Stack.
the terminal may show more information.
I took the log file by using teraterm serial monitor program. I did not see any valuable information for debugging. This is the results:
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
mode:DIO, clock div:1
ho 0 tail 12 room 4
ho 0 tail 12 room 4
I (32) boot: ESP-IDF v3.3-beta1-696-gc4c54ce07 2nd stage bootloader
I (32) boot: compile time 19:36:27
I (32) boot: Enabling RNG early entropy source...
I (38) boot: SPI Speed : 80MHz
I (42) boot: SPI Mode : DIO
I (46) boot: SPI Flash Size : 16MB
I (50) boot: Partition Table:
I (54) boot: ## Label Usage Type ST Offset Length
I (61) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (69) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (76) boot: 2 factory factory app 00 00 00010000 001f0000
I (83) boot: 3 internalfs Unknown data 01 81 00200000 001ff000
I (91) boot: End of partition table
I (95) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0xe970c (956172) map
I (379) esp_image: segment 1: paddr=0x000f9734 vaddr=0x3ffbdb60 size=0x034dc ( 13532) load
I (383) esp_image: segment 2: paddr=0x000fcc18 vaddr=0x40080000 size=0x00400 ( 1024) load
I (386) esp_image: segment 3: paddr=0x000fd020 vaddr=0x40080400 size=0x02ff0 ( 12272) load
I (398) esp_image: segment 4: paddr=0x00100018 vaddr=0x400d0018 size=0xdbea8 (900776) map
I (662) esp_image: segment 5: paddr=0x001dbec8 vaddr=0x400833f0 size=0x12bf8 ( 76792) load
I (688) esp_image: segment 6: paddr=0x001eeac8 vaddr=0x400c0000 size=0x00064 ( 100) load
I (688) esp_image: segment 7: paddr=0x001eeb34 vaddr=0x50000000 size=0x00808 ( 2056) load
I (708) boot: Loaded app from partition at offset 0x10000
I (709) boot: Disabling RNG early entropy source...
I (709) cpu_start: Pro cpu up.
I (713) cpu_start: Application information:
I (717) cpu_start: Compile time: Mar 13 2020 19:36:49
I (724) cpu_start: ELF file SHA256: 0000000000000000...
I (730) cpu_start: ESP-IDF: v3.3-beta1-696-gc4c54ce07
I (736) cpu_start: Starting app cpu, entry point is 0x400836e4
I (0) cpu_start: App cpu up.
I (746) heap_init: Initializing. RAM available for dynamic allocation:
I (753) heap_init: At 3FFAE6E0 len 0000F480 (61 KiB): DRAM
I (759) heap_init: At 3FFCB2C8 len 00014D38 (83 KiB): DRAM
I (766) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (772) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (778) heap_init: At 40095FE8 len 0000A018 (40 KiB): IRAM
I (785) cpu_start: Pro cpu start user code
I (131) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
Internal FS (FatFS): Mounted on partition 'internalfs' [size: 2093056; Flash address: 0x200000]
Filesystem size: 2031616 B
Used: 1605632 B
Free: 425984 B
I (359) [TFTSPI]: attached display device, speed=8000000
I (359) [TFTSPI]: bus uses native pins: false
W (534) sdspi_host: spi bus changed (1 -> 2)
E (577) sdmmc_sd: sdmmc_init_spi_crc: sdmmc_send_cmd_crc_on_off returned 0x106
[ M5 ] init sd card Fail
[ M5 ] node id:<deleted>, api key:<deleted>
I (2018) uart: ALREADY NULL
Please note that I deleted the node id and api key.
I didn't had any errors during burning.
The backlight is lit up.
Since I bought a M5Gray also, I recognisize the sound on the Fire as the sound of the Rock-Paper-Siccors game which is the default app.
I just thought, you were using the ui flow firmware previously right. I think there is an issue if you have flashed one of the micropython firmwares and try to use arduino afterwards without completely wiping the memory. Please try to use the erase tool in the M5 burner tool and then try and flash an arduino sketch again
Well, I have a couple of spots in my project that a button press would make things very easy. For example, I'm using M5ez for my interface, and use Blynk to display events on the M5 screen. I have backlight timeout set to 30 seconds. A new event doesn't turn the backlight back on, but a keypress does. So, in my if (newEvent) loop, I could have a M5.BtnA.press(), that would wake up the screen. Can I go into the M5ez library, figure out what happens after a real button press to wake the screen and replicate that? Yes, of course, and I have certainly tried that, but some of the items that need to be set are private, so calling them from a main loop is problematic. Rewriting that stuff so it's all public might work, but that solves one problem. I'd also like menus to time out - if there's no activity after going into a menu, I'd like it to time out and go back to the main menu. Again, code can certainly make that happen, but a M5.BtnA.press() would be a lot easier to implement... Does this make sense?
This means the M5Stack is officially certified for use with Microsoft Azure cloud services.
Below is a link to a video demo showing how to connect M5Stack to Azure using Mongoose OS. This video is targeted at Mac users but Mongoose OS can also be used on Windows or Linux.
Details on Mongoose OS: https://mongoose-os.com/
Details on Microsoft - Azure IoT Fundamentals: https://docs.microsoft.com/en-us/azure/iot-fundamentals/