Posts made by ajb2k3

@felmue thanks for taking the time to write up about it

@pwcrilly check the connections between the modules base and face as this is a symptom of one of them not connected securely. Also make sure to use the correct length screws to secure them.

@Bipman I don't have one at present but I wonder how we'll it will work with the CoreMP135.

@PharkieB I will have to check because I've been so busy that I have actually forgotten!

@sirtet Are you using the correct Stick C UIFlow firmware?
There are 3 different StickC revisions. the blank screen suggest that you have the wrong version loaded.

@PharkieB Yes, I use Thonny for programming and uploading Micropython.
Thonny makes it easier to upload images and libraries to M5Stack devices.
https://thonny.org

@burner Arduino

@avmg2502 How is it crashing?
What is the error message?

@thinpoint

Tried a different cable?
Installed the drivers?

@ti45001 Are you burning the specific correct fire/psram version?
Have you tried the specific fire/psram version of UIFlow2?

@stefanj9 Yes, just like the older editions of Raspbian OS you have to manually run the resize script on initial startup. The command is listed on the CoreMP135 product page but it's easy to miss.
My WIP guide to the CoreMP135 is going to be released next week but untill then you need to run the following command.

./resize_mmc.sh

and hit return.

@genanann Erase first and then burn again.
It's almost impossible to "Brick" a device.
Believe me I have tried!

@ioamas how do you know it’s not charging, have you checked the battery’s voltage?

@MadMackz We dont support or condone the use or discussion of devices and firmware for potential illegal use.

Now as you are new your first steps are to learn about UIFlow2 and programming in Micropython of which there are many resources available online.

@ZokiZok Pin 1 isn't available for use.

@MiguelM Looks like the wrong firmware has been burned.

@kuriko

Just been playing with SSH banner options.
!

@kuriko I will add that to my guide but you really dont want to allow root access to a device that runs on a network.

@hillsh_vi The problem is that UIFlow2 was designed for the newer processors consisting primary of the S3 and C3 groups because of a fundamental change to the way Micropython operates on them including the boot loader.
You may have noticed that the older gen devices could be programmed without actually touching the cores where as the new gen have to be put into boot loader mode for firmware writing.

Ok So Finially managed to get around to looking at the SSH issue with the CoreMP135.
The issue turns out to be with Debian itself.
The root account is heavily locked down and prevents access to ssh.
To SSH into the CoreMP135 you need to create a new user and use that user account to access the CoreMP135 with SSH.