Jump to content

KUI

Members
 View Profile  See their activity

  • Posts

    66

  • Joined

  • Last visited

 Content Type 

Posts posted by KUI

  5. Display options

    in MIDIbox NG

    Posted · Edited by KUI

    Hi TK,

    Finished my last show for 2013:)

    I have tested the changes and can report that there are some improvements and still some undesirable issues.
    The boot issue has disappeared.
    I was testing the display 16 corruption and thought to tell the MBNG that it had 24 displays attached.
    What should be display 16 appears to be display 24. If I type " lcd@(24.1.1) test " the text appears on display 16.

    Also now having trouble with dispalys 4 and 6 staying dark. If I disconnect the second display board completely, reboot, displays 1-8 are fine.
    If you would like pics please just say so.

    Also very impressive video with the synth:)

     

    Today:

     

    Continued testing. it looks like there is something amiss in the SR routing. With mbng configures with 24 displays.

     

    On the SmashTV dout module J3 O7 should be display 16. J3 O7 is definitely display 24.

     

    On J4 O7 does nothing. O0 is display 23, O1 is display 22, O2 display 21, O3 is display 20, O4 is display 19, O5 is display 18, O6 is display 17, O7 is nothing.

     

    When configured for 32 displays the pattern repeats, but with displays 32-25 with display 32 missing, it should appear on J5 O7.

     

    When configured for 40 displays the pattern repeats, but with displays 33-40 with display 40 missing, it should appear on J6 O7.

     

    Also, during all these tests J3 O7 continued to be Display 24.

     

    Hope this helps

     

     


    Keep it up, we'll find it:)


    KUI

  6. Display options

    in MIDIbox NG

    Posted · Edited by KUI

    in $MIOS32_PATH/modules/app_lcd/universal/app_lcd.c you will find the APP_LCD_SERGLCD_CS_Set() function which sets the CS lines.

    MIOS32_BOARD_J28_SerDataShift() is used to update the 74HC595 SR connected to J28

    E.g. an interesting SW change would be following modification at !all branch in APP_LCD_SERGLCD_CS_Set() 

    int selected_lcd = mios32_lcd_device - 8; // BEGIN mod: swap CS lines of 15th and 16th LCDif( selected_lcd == 7 ) selected_lcd = 6; else if( selected_lcd == 6 ) selected_lcd = 7;// END mod        int selected_lcd_sr = selected_lcd / 8;        u8 selected_lcd_mask = value ? ~(1 << (selected_lcd % 8)) : 0xff;

    This would swap the CS lines of the 15th and 16th display in the software

    If now display 16 still outputs incorrect data, you know that the problem is located at the hardware side.

    Best Regards, Thorsten.

    Hi TK,

    Successfully changed the code to swap cs lines in the software. The problems stays with socket 16. So the problem is in my hardware?

    I will inspect my boards. The really strange thing is that I have 2 lp17 core boards they both do the same thing.

    I will report back soon.

    Thanks

    KUI

     

  7. Display options

    in MIDIbox NG

    Posted

    So I have confirmed that cs line 16 is connected to pin 15 of the 74HC595.

     

    Tried three different 74HC595s no change, even changed the one on the core.:^/

     

    With the clock coming from J15B. I am unable to get the bootloader store function to access displays 9-16.

     

    In the past display 16 mimics, erroneously though, some of display 1's text.  See my pic half way down this page 

     

    KUI

  8. Display options

    in MIDIbox NG

    Posted

    Hi TK, For clarity, I have display 9-16's clock coming from J15B. The cs lines are coming from a smashTV 4xdout module. All oleds have a 100uf between 3.3v and gnd. Displays1-8 have a 240ohm resistor in series with the cs lines. KUI

  9. Display options

    in MIDIbox NG

    Posted

    Hi TK,

     

    I swapped display 15 and 16 physically.  No changed display 16 still showing same as video.

     

    I then routed cs line for display 16 to display 15 and 16, same text and corruption on both.

    I then routed cs line for display 15 to display 15 and 16, clean text no corruption on either display.

     

    I noticed with the output from my SAC machine that the corruption is only there when the displays are being updated, in the case of your oled test app, they are being constantly updated, hence the continuous scrolling.

     

    some kind of artifact?

     

     

    Regards

     

    KUI

  10. Display options

    in MIDIbox NG

    Posted

    :-/   Are you able to swap displays? It would be interesting, if for example display 16 behaves the same way if another OLED is plucked into the socket. And another interesting test: how does it behave, if the CS line of display 16 is connected to the same 74HC595 pin, which is routed to display 15 (I would expect, that both displays show the same text)   Best Regards, Thorsten.
    Will test shortly. KUI

  13. Help Can't Build

    in MIDIbox NG

    Posted

    Just updated from the SVN. And downloaded the new mios32_toolchain.

     

    Here is what I get:

     

    **** Build of configuration Default for project midibox_ng_v1 ****

     

    make all

    rm -f project.hex

    arm-none-eabi-gcc.exe: nano.specs: No such file or directory

    make: *** [project_build/project.elf] Error 1

     

    **** Build Finished ****

     

    I am using Eclipse

     

    Eclipse IDE for C/C++ Developers

     

    Version: Indigo Service Release 1

    Build id: 20110916-0149

     

     

    Am I missing something?

     

    Thanks

     

    KUI

  14. Display options

    in MIDIbox NG

    Posted

    Update,

     

    I can confirm that J15B SCLK works. I now have displays 1-8 off of J15A, and displays 9-16 running off of J15B and J28 through a dout module for the cs lines.

    Thanks TK, that makes connecting the next 8 displays at least easier:)

     

    Still have the scrolling on display 16.

     

    Occasionally if I have to reboot I must do it twice with 6 seconds in between boots.

     

    Cheers

    KUI

  15. Display options

    in MIDIbox NG

    Posted

    So. . .  Same result on display 16.

    Removed the 100 ohm resistors on the D0 D1 And DC lines.

    Result, garbled displays on 1-8.

    Added the resistors back one at a time. When D0 and D1 are isolated through the 100 ohm resistors, displays 1-8 are stable. DC seems to make no difference.

     

    Hope this helps

     

    Cheers

     

    KUI

  16. Display options

    in MIDIbox NG

    Posted · Edited by KUI

    Hi TK,

     

    So that seems to fix the boot issue for all 16 displays :smile:

    I have attached a video of the behavior of display 16.

     

    NOTE: I still have 100ohm resistors in series with the D0 D1 and DC lines between the two 8 OLED display boards.

    Should I attempt with them removed?

     

     

    Thanks

     

    KUI

    VIDEO0020-0.zip

  17. Display options

    in MIDIbox NG

    Posted

    Hi TK,

     

    I am in Nashville TN, USA.

    I am using the original LPC17 core board. All 16 of my displays are booting and working with the old gcc. I only have one issue on display 16, slight scrolling of the second line, its scrolling left to right.

    Still get two displays missing when using the new gcc you posted.

    I have not tried just twelve displays. Like Novski I jumped from 8 to 16.

     

     

    Cheers

     

    KUI

  18. Display options

    in MIDIbox NG

    Posted

    2) question to KUI and Novski: are you using a 74HC595, or 74HCT595 as shift register?

    I'm using a 74HC595 (without T) as recommended in the MBHP_CORE_LPC17 schematic. I don't remember the exact reason anymore, but I remember that some people had problems with driving LCDs when they used 74HCT595.

    I only want to ensure, that you are using exactly the same HW components...

     

    Best Regards, Thorsten.

    I am using 74HC595N shift registers.

     

    I have not tried to distribute D0 and D1 through shift registers yet.

     

     

    KUI

     

    KUI

  19. Display options

    in MIDIbox NG

    Posted

    Hi TK. we had a misunderstanding im sorry for that.

    I have a HC version and tested it. But all the displays stay dark.

    I can't locate my falure but im shure that there is a miss connection somewhere. Give me a day or two. I will look another time over that as soon as possible.

    Because my PCB i so complicated its hard to solve it.

     

    does KUI's display work now?

     

    best regards

    novski

    Hi Novski,

     

    I am out of town until nov. 25th.

     

    Look back over the posts to find out where I was with the dispalys before I left to go to work.

     

    thanks

    KUI

  20. Display options

    in MIDIbox NG

    Posted · Edited by KUI

    Fine! :smile:

    Could you please also check the firmware image that I created with the new gcc version?

    -> http://www.ucapps.de...v1_027_pre5.zip

    Display #16: the CS lines of the J28 shift register are not initialized during boot, this could be the reason.

    All displays should be correctly cleared after boot once the MBNG application takes over the control - can you confirm this?

    Best Regards, Thorsten.

    Hi Thorsten,

    I can confirm that after the mbng app takes over all display are correct.

    I loaded 027 pre 5 and I get displays 9-16 initializing okay. Display 4 and 6 are not working.

    I then reloaded 027 5 oldgcc and all displays work correctly.

    Went back and fourth 4 times to prove to myself that there was a difference.

    Thanks

    KUI

  21. Display options

    in MIDIbox NG

    Posted

    Apparently it was a bad idea to change two things once: pre5 has been compiled with a newer gcc version which creates faster code. I've to review the timing dependent routines...

     

    In order to confirm, if this assumption is true, could you please try following build?

    -> http://www.ucapps.de/mios32/midibox_ng_v1_027_pre5_oldgcc.zip

     

    Best Regards, Thorsten.

    Hi All,

     

    This seems to fix the initialization issues for me on displays 9-16.

    I can power and re power over and over and get all 16 displays to work.

     

    Novski,

    I had recurring corruption on all displays until I put the 100 ohms resistors in series with D0, D1 and DC between the two 8 channel display boards.

     

    TK,

     

    P.S. I am only home for 18hrs between shows. Be back in the game on Nov.23rd, money calls:)

     

     

    I still have a little weirdness on display 16. On boot in partially displays the same text that you show on display 1.

     

     

    Thanks

    KUI

  22. Display options

    in MIDIbox NG

    Posted

    <blockquote class='ipsBlockquote'data-author="Duggle" data-cid="160643" data-time="1384050925"><p>

    That's a big supply.<br />

    So the regulated 5V for the OLEDs is coming from the core?</p></blockquote>

    Yes Duggle 3.3v for OLED comes from the core.

  24. Display options

    in MIDIbox NG

    Posted

    Novski I only have corruption with the 16oled app on display 16 see pic in post above, no spreading text or flipping

     

    I fixed the corruption issue by moving the 100ohm resistors you have on the D0 and D1 lines to after the first 8 displays. I also added a 100 ohm resistor to the DC line as well. This seems to suppress the noise that comes after I added display 9-16.

     

    Still looking for a solution to the power cycle issue.

     

    Thanks

     

    KUI

  25. Display options

    in MIDIbox NG

    Posted · Edited by KUI

    I have added 100nF caps between 3.3v and gnd to every oled, no change:(

     

    When I power the core cold I only get the first 8 displays, unplug count to 5 and replug I get all 16, unplug count to 5 replug all 16 displays again, unplug count to 10 and replug only the first 8, I can repeat this cycle over and over.

     

     

     

    Also I am having weirdness on display 16.

    the second lines seems to be scrolling?

    with some kind of wraping issue.

     

    I have attached an image of both display 15 and 16 after sending store from the bootloader aswell.

     

    Hope this info helps to sort out the problem.

     

     

    Thanks

    KUI

    post-8647-0-85176300-1383851051_thumb.jp

    post-8647-0-74751400-1383851453_thumb.jp

×
×
  • Create New...