delwinbest / mks-tft28 Goto Github PK

So I sat down and ported the bigtreetech LCD Marlin control system from
https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware
to
https://github.com/darkspr1te/MKSTFT_Marlin_Touch

Uarts are problem still,
to switch serial port (Wifi TXD,RXD,RX,TX or AUX1 TX,RX)
UART1 WIFI: TXD,RXD
UART2 AUX1: TX,RX
UART3 WIFI: TX,RX
in variants.h
#define SERIAL_PORT _USART1 (line #125)

connecting TXD/RXD from wifi connector to the TX/RX of the Ramps cable , open a terminal on the ramps board and you should see commands echoed back,

After flashing , copy MKS folder to SDCARD , create blank file reset.txt (this triggers touch calib)
reset MKSTFT , fonts should update right away.
Enjoy, feel free to Fork ,

N.B
USB Host hangs, CPU / XTal speed is incorrect but close enough for 115200 baud to work , will loose uart sync sometimes,
using UART2 as main uart(via AUX1 TX/RX) not working, AUX1 TX/RX is 5v, low is 2.56 - need to test on another board
speaker works but disabled for normal use
switch board type from #define STM32F10X_CL (#79 variants.h file )
to
#define STM32F10X_HD

will still function abliet slower, must port those _CL changes to other lib(arduino one)
as is now show's it's correct speed loading data from spi (test difference you will see)
only issue is under _CL the math is off for uart, errors occur.

i2c eeprom untested,
built usin CMSIS libs/STDPeriph
SDDeinit(); causes hang
see boot.c for SPI EEprom & sdcard updating code

The LCD only works when using MKS bootloader, this implies there is missing init code in main software. Need to refactor and create feature parity between the two.

Relates to #1

So i've overhauled /variant enough so out of the box UTFT/URTOUCH(calibrated)/SD Card, EEPROM-SPI/I2CPROM/All uarts 1/2/3 (HW) , External SD/SPI , RTC/PWM workings using most default demos, and i've dome some examples on top, i cannot get platformio to output a file with vectors for 0x8000000 only 0x8007000 despite my io additions, DM me at igeekcrg at gmail.com if you want to pull req the new changes as i wont be pushing them for while.
darkspr1te

As a developer I'd like to select a build environment which will build either a bootloader compatible hex file (VECT offset 0x7000) , or flash the FW directly on the target board (no VECT offset).