I’m building my seq V4 and am facing a major problem: my LCD displays only show a row of black squares…
I’m building a wilba frontpanel. The MBHP bootloader is in my STM32F4 board: MIOS Studio tells:
Operating System : MIOS32
Board : MBHP_CORE_STM32F4
Core Family : STM32F4xx
Chip ID: 0x10076413
Serial: #320041000D51353235363632
Flash Memory Size: 1048576 bytes
RAM Size: 196608 bytes
MIDIbox SEQ V4.092
MIOS Studio proposes 4 Midi Ins and outs for the Midibox (named MIDIbox SEQ V4, MIDIIN2 (MIDIBox Seq V4), MIDIIN3 (MIDIBox Seq V4) and MIDIIN4 (MIDIBox Seq V4). MIOS Studio is also able to see what’s on my SD card, but it seems like the core board can’t read neither the wilba MBSEQ_HW.V4 nor the standard MBSEQ_HW.V4 files which are located at the root of my SD card (when I try to edit the MBSEQ_HW.V4 with the MIOS File browser, I get an “Invalid response from MIOS32 core during read operation” after about 14% of the file has been downloaded)
I must add that my frontpanel isn’t completely finished yet, so nothing else than the LCD displays are plugged on the MBHP_core_PCB (bought on smashTV shop).
This is the LCD I bought and its datasheet. It seems like the LCD for the seq V4 must use a HD44780 controller. The ones I got uses a ST7066U
controller but are said to be compatible with HD44780…
I tweeked the contrast and luminance pots but none of my tries gave any effect on displaying good things… I verified the connections and everything is at its own place (Seq ground to LCD ground, seq Vd to LCD Vd, etc. )
If you don’t find another problem, and although it is not highly likely, it might indeed be the controller, that is not 100% compatible, especially in 4-bit mode.I just did a quick google check and have found a few issues with compatibility of the ST7066U here and there. You should be able to source a cheap real HD44780 (it does not even need to be 40x2) from ebay for a few dollars to test…
Regarding the interrupted SD card transfers, i bet you are using windows, this is a common problem with the MIDI USB drivers under windows - for the moment, pull out the card, change the configuration file on your computer and plug it back in.
You might try some of the other LCD configs, though I couldn’t say what one would be better.
For the SD card, one way is to edit the file with a text editor on your computer and upload it using the file browser. Normally uploads go okay, but downloads hardly ever work for me.
It really kind to have taken the time to answer me, but I’m kind of lost with your answers now !!
12 hours ago, Hawkeye said:
If you don’t find another problem, and although it is not highly likely , it might indeed be the controller, that is not 100% compatible, especially in 4-bit mode.I just did a quick google check and have found a few issues with compatibility of the ST7066U here and there.
Do you mean that the problem is most likely anywhere else than the LCD controller ?
12 hours ago, latigid on said:
You might try some of the other LCD configs, though I couldn’t say what one would be better.
latigid, what do you mean by trying other LCD configs ? Byuing a new one that fits HD44780 standards ? Changing something in the config file ?
" Additional hints: So long as the operating system (MIOS) hasn’t been uploaded via MIDI, the LCD won’t be initialized and shows black bars at the upper line. If you don’t see these bars, adjust the contrast pot. The highest contrast can be achieved with V0=0V (you can adjust this voltage with the trimpot P2). "
This is exactly what I see (black bars at upper line)…But I don’t get the “[…] So long as the operating system (MIOS) hasn’t been uploaded via MIDI[…]”. I have the MIOS bootloader installed on my STM32F4, I have an accessible and readable SD card (from MIOS Studio) on which I’ve put the MQSEQ_HW.V4 at the root of the file system… Did I miss something during installation ?
The firmware is up and running, if you can see the MIDIbox in MIOS studio, so MIOS is running… While i am not certain, that the display controller is incompatible, I say, there is a fair chance. It might be something else though, e.g. some bad solder spots on the core.
To “debug” this, I’d therefore highly recommend to obtain a real HD44780 for testing purposes (e.g. a cheap 16x2 for ~ 3$/EUR from ebay) - it will also serve you well for other MIDIboxes, that you build later on :-). If that testing display works, you will have to replace the (more expensive) 40x2 panels.
The 2x16 with the right controller would be a great tool idea for testing. I would triple check your wiring as well. It is odd that you are getting only one row of dark characters. Normally they should both be lit with the same amount of contrast. The darkness of the both rows should be adjustable by the contrast pot equally at the same time. If it is too dark you will not be able to see the characters. The same if it is too light. the contrast should work in this way regardless if the controller is compatible or not. If the controller is not compatible or there is a soldering or component issue you will have the additional issue you mention of lack of characters or possible gibberish on the screen. If you are using header connectors it would be possible to get one backwards or reversed. If this were the case you might possibly have a data line connecting to the contrast connector. That may be cycling the contrast at a rate where only one line is being lit full contrast. If the wiring is good and contrast is working properly on the single line it is most likely you have a bad LCD.
a “stab in the dark” test could be to load the bootloader hex (through MIOS Studio, not using the boothold mode) and change for one of the following LCD types:
LCD Type: applications which are compiled with the “universal” LCD driver can handle various character/graphical LCD types and display dimensions.
It’s recommended to store these parameters of your MIDIbox in the bootloader info range.
Following commands are available:
lcd_types lists all available LCD types and their appr. number
set lcd_type the LCD type number (enter “lcd_types” to get a list of available types)
set lcd_num_x number of LCDs in X direction
set lcd_num_y number of LCDs in Y direction
set lcd_width width of a single LCD ()
set lcd_height height of a single LCD ()
store
(*) CLCDs: number of characters, GLCD: number of pixels
Example: a single HD44780 based 2x20 character LCD is connected to your MIDIbox (default)
Enter:
Please note: some applications (like MIDIbox SEQ V4) could overrule the predefined parameters if they can’t handle smaller (or larger) LCD sizes.
Please note also: some applications could have been released with a different LCD driver (MIOS32_LCD != “universal”) which don’t consider these parameters. It’s up to the developer to document this limitation.
It is odd that you are getting only one row of dark characters. Normally they should both be lit with the same amount of contrast. The darkness of the both rows should be adjustable by the contrast pot equally at the same time. If it is too dark you will not be able to see the characters. The same if it is too light. the contrast should work in this way regardless if the controller is compatible or not.
I’ve not been clear enough in my first post I think. Both LCD display a first row of black squares. Contrast and rightness are adjusted equally when I turn the pots !
I rechecked all the solders, they look fine. And the wiring is fine too !
I just received a 2x16 HD44780 LCD, wired it (checked twice) to the MBHP_Core J15A jumper and what I get is…a bright blue background…
What surprises me is that when I turn the contrast P2 pot, I can see 2 rows of 16 black squares (The 8 rigthmost squares on row 1 and 2) appear and almost immediately disappear…I need to constantly tweak the Contrast pot to see these squares…So I rechecked the solders of the trim pots and they seem fine. This “flickering when tweeking” thing isn’t visible when I use my original LCD : only the upper row is constantly filled with black squares.
All connections from the STM32F4 to the IC2 (74HC595) are good…
If everything was working, what should I see on this 2x16 LCD display ? Squares ? characters ? Could this come from a faulty BC337 .
I’v replaced the 74HC595, checked that the transistor had a “traditional” pinout and that the solders were good (to ground, R12 and R13).
I rewired my test screen (2x16 HD44780 LCD) and now all I get is a filled with black squares upper row. No matter of the amount of contrast and luminosity, no character appear…(yesterday’s flickering problem might have come from a bad wiring…thanks tireness)
I read that a row of black squares could mean that the LCD failed initialization and stays in “setup” mode. This is sometimes due to bad timing (delays) during the initialization procedure. Is there a way to modify this ?
My MBHP_Midi_IO module is not plugged in when I do my testing…could that have an influence ?
Could I have done something wrong during the bootloader procedure ? Is there a way to check the MIOS is correctly installed (apart from seeing that MIOS studio recognizes the midibox and that it accesses to the SD card ?)
I was going to suggest the 4x1K resistor array. I bought the wrong part once, and it was a “series” array and not a parallel that is the correct.
Damned !! Wrong resistor network…I made a mistake when I bought the parts…This is a 4x10K resistor array…and of course, no 4x1K resistor network in stock at home…Would it be a problem if I put a 4x 220 Ohms resistor network instead ( this one for example ) or if there is no resistor network ?