trueControl
/
sc7-testo-firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md

This commit is contained in:
true 2023-10-31 08:22:07 -07:00
parent f504e921d6
commit cfd9715023
1 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
README.md
View File

@ -7,9 +7,9 @@ This is a PlatformIO-compatible project.
   
**BE AWARE:** **BE AWARE:**
On REV1 boards, the right potentiometer only works for the first half of its rotation. Turning the right pot beyond half way will not cause damage, but will consume extra current (up to ~3-5mA) and will flash the eyes red an error indicator while in RGB fun mode. On REV1 boards, the right potentiometer only works for the first half of its rotation. Turning the right pot beyond half way _will not cause damage_, but the addon will consume extra current (up to ~3-5mA). If the knob is within the affected second half of rotation, the eye LEDs will flash red as an indicator while in RGB fun mode.
To work around this, use the right pot within the first half of its rotation. To work around this, use the right pot only within the first half of its rotation.
   
@ -42,6 +42,13 @@ The TEST-O Robot is:
- There is an empty RGB LED program slot available for hackers to add one - There is an empty RGB LED program slot available for hackers to add one
## Hacking
Use a DAPLink probe to debug. If you don't have one, there are many projects to convert existing devboards to DAPLink.
If you want to hack on this without a debug probe, an XMODEM bootloader is available. Use a TTL UART to connect to the UART pins on the addon header. To activate the bootloader, ensure the left knob is between halfway to full clockwise. Press and hold the button while powering on. The bootloader will now indicate it is working with flashing LEDs, and will communicate at 115200-8-N-1. Send your firmware.bin file using XMODEM using a terminal emulator.
## Specifications ## Specifications
- PUYA PY32F003W16S6 MCU - PUYA PY32F003W16S6 MCU
@ -56,23 +63,16 @@ The TEST-O Robot is:
## Misc Notes: ## Misc Notes:
- This device is using PUYA PY32F003 MCU. This is a CM0+ MCU - This device is using PUYA PY32F003 MCU, an MCU intended for
that is intended for the China domestic market. This MCU, the China domestic market. This MCU, as well as other
as well as other PY32F002A/003/030 cores with at least 32K PY32F002A/003/030 cores with at least 32K flash, internally
flash, internally uses the same core as PY32F030F6P6. uses the same core (and has the same features) as PY32F030F6P6.
- To activate the bootloader, press and hold the button while - The normal firwmare does not use UART and leaves the pins configured
powering on while the left knob is turned between halfway to as SWD for the user.
full clockwise. The bootloader will now communicate on the UART pins
of the addon header at 115200-8-N-1 and wait for XMODEM data.
- To use a debugger, connect using the UART pins on the addon header. - There is no official OpenOCD support for this MCU. This project uses
The normal firwmare does not use UART and leaves the pins configured pyOCD as adding PUYA MCU to pyOCD is trivial. Using OpenOCD, J-Link,
as SWD for the user. Use a DAPLink compatible debugger. If you don't
have one, there are many projects to convert existing devboards to DAPLink.
- There is no official OpenOCD support for this MCU. Adding the PUYA MCU
to pyOCD is trivial, so this project uses pyOCD. Using OpenOCD, J-Link,
or anything other than the DAPLink compatible debugger with pyOCD or anything other than the DAPLink compatible debugger with pyOCD
is untested and left as an exercise to the programmer. is untested and left as an exercise to the programmer.