Topics created by jpk

@jpk said in Base M5GO BOTTOM: Issues with UART (Port C): @ajb2k3 Have you got any photos and a write up about this resistor issue? Sorry, no photos. My cutter was faster than my camera. But the issue is described in the first post. Removing the resistors resolved the issues described above - for me. I do not recommend this procedure. Maybe someone from M5Stack can answer this. All photos I find online do not have these resistors installed - at least not in the way it was done on my module. Maybe this "feature" has been integrated into the PCB directly with later revisions. Again, at least for my module there is a mismatch between hardware and documentation. I cannot tell which one is "correct". Can you consider creating a Hackster.io project documenting this modification please? Hmmm no. Please correct me if I am wrong, but both Hackster.io and the M5Stack-Facebook-Site need registration before even reading the existing posts? I see this somehow critical: Essential information about M5Stack is distributed on several platforms ==> You always have to check all sites... I don't like being forced to register before reading content provided by other users for free. Yes, some more features would be nice, but this forum is more than sufficient for discussing technical issues. BR, jpk Facebook yes, hackster no. Also there is github which is useful for storing code and files which you don't need to register to read files.

@butch said in Identify M5Stack Fire Revision & Issues: @jpk Was there ever any response / resolution to this question regarding Fire Hi Butch, not really. But they put some more informations on the webpage. Which does not contribute to clarify things. @m5stack @lukasmaximus In the mean time there are a lot of modules and there is more and more documentation. But the documentation is really a bit annoying and not always clear...Questions in this forum are not really answered. Initially I really was impressed by the m5stack, but this lack of quality/documentation is a bit disappointing. Want an example? Maybe you can sort it out (b.t.w it is still the same question of the first post in this thread): 1.) Revisions (new information on the page) See this page, scroll down to "Version-Change" https://docs.m5stack.com/#/en/core/fire?id=version-change But surprise, my PCB revision ("2018. 2A") is not even listed.. :-? According the numbering scheme I own a PCB before "Initial public release" (or it is hex_2A=dec_42?)...? 2.) I2C Adresses used by the equipment https://m5stack.oss-cn-shenzhen.aliyuncs.com/image/m5-docs_table/I2C_Address.pdf The "Fire is not explicetly listed here, but it should be part of "M5Core" section. Again: Revisions (see 1.)) are not taken into account here. ==> Based on this information (0x68, see first post) I should have a MPU6886 (=latest 2019 PCB revision acc 1.)) installed...? But this does not match the fact, that I have an old and undocumented PCB revision... 3.) As the "MPU9250 Basic Example Code" is working for me, I assume I have a MPU9250 installed, which again acc. 1.) would mean I have a PCB revision "2019.7". 4.) In the "official" (?) store https://www.aliexpress.com/store/product/M5Stack-NEW-PSRAM-2-0-FIRE-IoT-Kit-Dual-Core-ESP32-16M-FLash-4M-PSRAM-Development/3226069_32847906756.html?spm=2114.12010612.8148356.5.1adc593auFAMct There is still written "9DOF: SH200Q+BMM150", even though the latest version should be "MPU6886" acc. 1.) Confused? :) jpk