Jump to content

EvilEvilEvil

Members
 View Profile  See their activity

  • Posts

    49

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by EvilEvilEvil

  1. Displays not initializing after working for a while

    in MIDIbox SEQ

    Posted

    8 hours ago, Hawkeye said:

    Nope, should work.

    Can you go to the bootloader and set the LCD type again? It is explained here:

    http://www.ucapps.de/mios32_bootstrap_newbies.html

    Here is the relevant section for the SEQ:

    Example2: two HD44780 based 2x40 character LCDs are connected to your MIDIbox
    Enter: 

    
     lcd_type CLCD
     lcd_num_x 2
     lcd_num_y 1
     lcd_width 40
     lcd_height 2
     store

    Many greets and good luck!
    Peter

     

    Screen Shot 2017-11-20 at 10.53.22 AM.png

  6. Displays not initializing after working for a while

    in MIDIbox SEQ

    Posted

    4 hours ago, Hawkeye said:

    +1, it might "just" be a soldering fault somewhere in that area - can you photograph the core front and back (deinstalled STM32F4 module) in high res and post it here?

    I already did :hmm:

    4 hours ago, Hawkeye said:

    If you have access to an oscilloscope, you can check all data pins at the display, it should show activity on most lines arriving at the display during startup, interesting are the lines R/S, E and R/W... and if these work properly, check the data lines.

    I don't have an oscilloscope. I've tested the pins some.

    4 hours ago, Hawkeye said:

    I assume that you replaced the display "one last time"? Smaller HD44780 test screens are really cheap on ebay, the current one could still be burned from the previous core/wrong polarity?

    OK, I'll try another one. Then that's it for now. Maybe in some months I'll get encouraged to go back at it.

    4 hours ago, Hawkeye said:

    Many greets and good luck!
    Peter

    Thanks again

  8. Displays not initializing after working for a while

    in MIDIbox SEQ

    Posted

    Just now, Hawkeye said:

    Hm, a few questions:

    * what happens, if you turn the contrast pot? Do the solid blocks visible in the picture just disappear and fade to "nothing"?

    Yes. the brightness and contrast work as expected

    * which firmware do you have installed? can you install the newest MBSEQ from ucapps (and make sure you use the stm32f4 branch)?

    I have midibox_seq_v4_094/MBHP_CORE_STM32F4 installed

    * do you "see" the core in MIOS studio and can you send commands to the just installed MBSEQ via the terminal?

    Yes, of course. This is all documented in previous posts in this thread (I know.. it's a lot of content ;)

    * did you build this second core as a completely new unit, aka have you also installed a new stm32f4 module or have you just plugged the old stm32f4 module to a newly built MIDIbox core?

    Ye, completely new as if I had never done it before. New stm32 with a new core.

    * if it is a new core, have you checked the orientation and proper installation of the 74hc595 and '541?

    Yes, resoldered both of them. Checked the pin orientation many times. Ordered more 595Ns, 541ANs and have a full bag of them now!

    Many greets and good luck!
    Peter

     

  12. Core won't boot anymore, dead STM32F4?

    in MIDIbox SEQ

    Posted · Edited by EvilEvilEvil

    Same exact thing I'm experiencing. It worked and I put it aside for some weeks while I built the other mods. Now it doesn't and just produces the black bars on the LCD. I've rebuilt my core, ordered another LCD and tried another discovery board - same result. It makes no sense because it worked fine several weeks ago. TK, please help! :grin:

    What does MIOS Studio say? Does Seq4 actually start?

  13. Displays not initializing after working for a while

    in MIDIbox SEQ

    Posted

    1 hour ago, latigid on said:

    Verify each of the intended connection points on J15 are made correctly with the display.
    Check for shorts between the cable pins (can happen with misaligned header)
    You are fiddling with the contrast and brightness controls each time, right?

    What firmware is loaded on the Core?

    Yes, changing the contrast and brightness often. My assumption is that if you can see the bars then you can see the regular OS display, correct?

  21. Displays not initializing after working for a while

    in MIDIbox SEQ

    Posted

    On 10/31/2017 at 4:33 AM, latigid on said:

    A common problem with Eurorack power headers is they only work if the notches are polarised the same way on both the bussboard and the module. If the module has "pin 1" on the opposite side as the power output header and both headers are keyed, there is no way to correctly plug in the cable.

    The Core schematic is correctly drawn as a "mirrored" header.

    Still not quite sure I understand. I have the red stripe going from the inner pin closest to the brightness/contrast pots to pin 15 on the LCD. The LCD has numbered pins.  

  25. Displays not initializing after working for a while

    in MIDIbox SEQ

    Posted · Edited by EvilEvilEvil

    Thanks. This is what I get on the bootloader screen 'help'. Perhaps I did connect the lcd wrongly at some point. Would this really have the potential to damage it?

     

    EDIT : Just noticed that IC1 is getting pretty hot when it's plugged in for 5 minutes or so. I think I'm just going to cough up the $70 and build a new board... 

    EDIT 2  :fear: Amateur hour. So when I reset IC1 late last night in all my frustration, I put it in backwards.... :blush: hence the heat. HOWEVER - when it was reversed, the bootloader recognized LCD 1 and the testlcd pin D1 worked (screenshot 1). Now that IC1 is back facing the correct direction, bootloader says "failed: no response from LCD 1" and testlcdpin 1 doesn't work again. Does this shed any light on the situation? That it recognized the LCD when IP1 is (accidentally) reversed? See screenshot 2.

     

     

    Screen Shot 2017-10-23 at 7.28.21 PM.png

    Screen Shot 2017-10-23 at 8.52.14 PM.png

×
×
  • Create New...