kunerd / clerk Goto Github PK

CGRAM has different size than DDRAM.

CGRAM = 64 byte
DDRAM = 128 byte (2 line version)

The CGRAM is logically divided into characters of 8 or respectively 10 lines each, depending on the font size of the display. So it would be nice to have utility functions to seek the RAM by character and character line offsets.

On fast hardware without OS, e.g. f3 discovery, stm32, the initialization flow doesn't work reliable.

1. 4-bit mode initialization timing needs to be re-factored
2. write operation probably needs some better timing, too

To make this lib easier to (re-)use, it should make usage of the traits provided by the embedded-hal crate. The current impls in the hal module are already very similar to them, so porting should not be a big problem.

The only thing that needs clarification is whether to use the single pin or the port wise traits?

This should be Configurable via the type system.

see #14

When doing a left shift of cursor, the internal address counter will overflow. Needs clarification what actually happens with the internal address counter of real hardware.

remove closures in .set_* methods, by using either:

• the builders directly via reference: .set_entry_mode(EntryModeBuilder::default().set_move_direction(...))
• a public struct: https://play.rust-lang.org/?gist=5555953cc7b2421c281b65adb1fb9d45&version=stable
• an enum for all settings:

  display.set(Function::EntryMode{...})
  display.set(Function::DisplayControl{...})

Currently the hardware interface is highly influenced by the GPIO interface that I use on my Raspberry Pi, but most embedded devices use only some kind of memory for this purpose.

1. allow different type for each pin
2. do not require to convert from integer, use real types instead