MCUFRIEND_kbv - anybody successful?

Working libraries, libraries being ported and related hardware
Post Reply
bianchifan
Posts: 82
Joined: Sun Oct 18, 2015 1:27 pm
Location: W'tal, Germany

MCUFRIEND_kbv - anybody successful?

Post by bianchifan » Mon Jan 02, 2017 11:42 am

In summer last year I found a lib - MCUFRIEND_kbv - which would had spared me some time and nerves if I had know earlier.
The last version helped me initializing an unknown controller.
Still unknown (ID: 1581, didn't found such ILI) but usable now ;)

Yesterday I played with this lib paired with a blue pill.
1st. problem, serial output.
I must add 5 seconds delay for connecting a terminal program after establishing the virtual com port.

2nd prob, parallel shields.
When the control ports are connected, the virtual com port sucks and the connection is lost.
If the physical connect resides on a hub all hub all other devices on this hub are lost.
Sometimes the MCU gets bricked and must be unbricked via boot jumper and LInk utility.

stevestrong
Posts: 1735
Joined: Mon Oct 19, 2015 12:06 am
Location: Munich, Germany

Re: MCUFRIEND_kbv - anybody successful?

Post by stevestrong » Mon Jan 02, 2017 2:26 pm

1. The PC needs up to 5 seconds to re-enumerate the USB port as serial. To avoid timing, you could use

Code: Select all

while ( !Serial.isConnected() ) ;
2. looks like a short caused from IO pin to Vcc/GND. Double-check connections. Very important, don't forget to activate the LCD_RST wire!

bianchifan
Posts: 82
Joined: Sun Oct 18, 2015 1:27 pm
Location: W'tal, Germany

Re: MCUFRIEND_kbv - anybody successful?

Post by bianchifan » Tue Jan 03, 2017 9:06 am

stevestrong wrote:1. T..To avoid timing, you could use

Code: Select all

while ( !Serial.isConnected() ) ;
MCUFRIEND_kbv uses simply
while (!Serial) ;

The problem is different and my knowledge about serial tranfers is darked out, nearly a black hole meanwhile.. :lol:
In AVR world (I tried win7 only):
I can attach any of MCU(tiny13, tiny65, 328p) via any Serial-USB Transmitter, the game is always th e same.
If the port is visible in the device manager HTERM/SerialMonitor can listen on the virtual port.
If the terminla is started with an already existing connection the port/MCU gets resetted.

In STM32 world the terminals cannot connect, port is busy...
example HTerm:
- disconnect all
- start Hterm
- attach pill
- wait for port
- refresh port list
- connect to port
- watch the output

example Serial Monitor.
- start IDE/close Serial Monitor
- attach pill
- wait for port visible
- check IDE tools menu for port
- start Serial Monitor
- watch the output
stevestrong wrote:2. looks like a short caused from IO pin to Vcc/GND. Double-check connections. Very important, don't forget to activate the LCD_RST wire!
mea culpa, I wrote nonsense, the control ports are ok.
The fault steps in with the connection of D0-D7, I mismatched the lines :oops:

Post Reply