Revision 2 Mockup
I've started working on some mockups for the next revision of the Serial Monitor. The main issues that I feel are needed to be addressed are:
- Slow to update data on display
- Use RAM to store data instead of FLASH
- Have a more general channel where the user can choose to have two inputs, two outputs or one of each
- Modular design with three major building blocks, Connector Block, Input processing Block, UI Block
This is the solution I've come up with for the second revision of the Serial Monitor. The other solutions below are left for reference purpose.
Final version
FPGA Mockup 1
Positive
- Any resolution on the display can be controlled, only have to change FPGA config
- The FPGA and lcd can be a separate board -> LCD controller board
- Can use cheaper MCU
- Can add as many features to the the “LCD controller” as I want to, i.e multiple layers, transparency etc
- More fun to develop because of FPGA!
- Should be faster than Revision 1 as we now have full control over the data interface between the LCD and MCU
- Can basically use any display I want, LVDS, HDMI?
Neutral
- FPGA not as “developer friendly” as MCU only solution
Negative
- A lot of work to get the FPGA working with LCD? -> Bought FPGA development board to find out!
- More components -> Cheaper MCU won’t matter
- Interface between FPGA and MCU hard?
- Difficult to handle multiple layers?
- Use two board?? One GUI board and one data processing board
FPGA Mockup 2
Positive
- Easier to implement the GUI on a MCU
- More fun to develop because of FPGA!
- True parallell handling of the serial channels, FPGA is better at that than MCU
- The interface between the MCU and FPGA only need to transfer the currently displayed data
- Special data processing, like auto baud rate
- Basically "infinite" number of channels as the FPGA is very flexible
- Can divide the system in to two parts, Data capture (FPGA) and GUI (MCU) -> Two separate boards
Neutral
- FPGA not as “developer friendly” as MCU only solution
Negative
- Interface between FPGA and MCU hard?
- Stuck with STM32F429 max resolution 1024x768 and it's functionality
MCU Only Mockup
Positive
- Fewer components -> Cheaper?
- Easy solution, code available for the STM32F429 discovery board
Neutral
- Only two layer support in STM32F429
Negative
- Stuck with STM32F429 max resolution 1024x768 and it's functionality
- Hard to share RAM for data and LCD? -> Use two RAMs?
Homepage
Pictures
GUI Mockup
Contact
Version 2:
ui-processor-rtos
fpga-config-mcu
fpga-config-over-uart
Version 1:
freertos-serial-monitor
freertos-serial-monitor lcd test
Simple GUI:
General
GUIObject
GUIButton
GUILabel
GUIStaticTextBox
GUIAlertBox
GUIButtonGridBox
GUIButtonList
GUIInfoBox
Tasks:
LCD Task Message
LCD:
LCD ER-TFT070-4
LCD ER-TFTM070-5
LCD HY070CTP-HD
LCD HY101CTP-HD
LCD YL070MY01
Touch Controller
Measurements:
STM32 GPIO Speed
FT5206 Waveform Capture
Version 2:
Revision 2 Mockup
Module IDs
Boards:
Connection Board
UI Processor Board
Data Processor Board
Isolated Power Module
LCD Board
Modules:
1. GPIO Module
3. CAN Module
5. RS-232 Module
15. nRF24L01 Module
Future Module Ideas
FPGA:
FPGA Main Blocks
FPGA Communication
FPGA UART
FPGA GPIO
FPGA Timestamp
FPGA SDRAM
FPGA PLL
[FPGA ID Reader](https://github.com/hampussandberg/HexConnect/wiki/FPGA-ID Reader)
FPGA LVDS
FPGA Monitor
FPGA Tips and Tricks
Learning Quartus II
Version 1:
Requirement Specification
Hardware Design
Hardware Rev 1 Fixes