I asked M5Stack support, their answer is:

The ‘stuck’ design is the original function of the joystick, which we called 'self-clock'. For the purpose of keeping the joystick in one direction continuously, without manual operation.

Best Regards,
support@m5stack.com

I think it's the matter of the board selection. When I first tried homeuser33's code I used the M5Stack OEM board: M5Stack Arduino>M5Stack-Core2(The PSRAM is enabled). It kept rebooting itself. I then switched to ESP32 Arduino>M5Stack-Core2(The PSRAM is enabled as well), it then worked.
Today, I tried different combinations. It ended up with that the only scenario that it's not working if you use M5Stack Arduino>M5Stack-Core2 with PSRAM enabled. M5Stack Arduino>M5Stack-Core2 with PSRAM disabled works perfectly like world101 said. But if you use ESP32 Arduino>M5Stack-Core2, both enabled and disabled work. So I guess this is the matter of selecting different boards.

Thanks!

@felmue

@felmue said in Looking for Factory Test Source code for Core2:

Hello @jdonth

what I meant by Arduino framework version 1.0.6 is the arduino-esp32 framework version 1.0.6 (instead of 2.0.1) and not the Arduino IDE. Sorry if I wasn't clear.

BTW: when I run the app compiled with 2.0.1 I see this error in the log:

E (2888) I2S: i2s_check_set_mclk(253): ESP32 only support to set GPIO0/GPIO1/GPIO3 as mclk signal, error GPIO number:6
E (2895) I2S: i2s_set_pin(314): mclk config failed

I was able to fix this error by adding this line in function InitI2SSpakerOrMic():

tx_pin_config.mck_io_num = GPIO_NUM_0;

Thanks
Felix

Thank you Felix! I'm glad I found your solution for this error. It finally works. I'm using version 2.0.2. I can now run the EchoSTT on my Core2.

@jdonth I'm not sure if you fixed your error. I have the same deprecated error. But it still can get compiled. My suggestion is to update the M5Stack libraries. This is what I did.

I asked M5Stack support, their answer is:

The ‘stuck’ design is the original function of the joystick, which we called 'self-clock'. For the purpose of keeping the joystick in one direction continuously, without manual operation.

Best Regards,
support@m5stack.com

@ajb2k3 Thanks a lot for your confirmation and notes.
I was expecting that the joystick will bounce back to the center, even after it reaches at the end of each direction. But it seems that this is what M5Stack intended to do so.

I bought a Joystick Unit several months ago and didn't use it until recently. I found that it will stick and lock at the end the each direction without coming back to the center. Is it normal? My other joysticks (not from M5Stack) don't act like this. So I guess this is faulty, or others have the same problem?

Thank you!

@felmue That makes total sense! Thank you so much!
I replaced the PaHub with the Hub expansion unit. Everything works now.

I'm trying to connect multiple I2C units(red, for example joystick, Env II and Color) and I/O units(black, such as Angle, Light, and Dual Button) to the FIRE. But both PaHub and PbHub are using the PortA. Is there any way that I can make them work? My plan is to connect PaHub to PortA and connect PbHub to one of the channels on PaHub. My question is how to get the values from each unit. I'm using the Arduino IDE.
Thank you very much!

Never mind. I found out that my M5core2 library is too old. After updating to the latest version, it uploaded successfully.

Thank you anyway!

Hi, I really like your idea. I tried to upload to my core2, but it ended up with compile error:
code.ino: In function 'void UIHandle()':
code:1657:3: error: 'Event' was not declared in this scope
Event& e = M5.Buttons.event;
^
code:1657:10: error: 'e' was not declared in this scope
Event& e = M5.Buttons.event;
^
code:1657:17: error: 'class M5Core2' has no member named 'Buttons'

Can you please advise me what I should do to fix this?

Thank you!