Jump to content

nsunier

Programmer
  • Posts

    53
  • Joined

  • Last visited

Everything posted by nsunier

  1. I'm currently testing the GLCD functions. It works quite well for the GLCD_FONT, GLCD_FONT_BIG, GLCD_FONT_KNOB_ICONS fonts. But I'm not able to use the GLCD_FONT_SMALL, GLCD_FONT_METER_ICONS_H and GLCD_FONT_METER_ICONS_V ones?! I got this error message when I do a make: rm -rf _output/* rm -rf _output rm -rf *.cod *.map *.lst rm -rf *.hex mkdir -p _output sh ./bin/mios-sdcc -c -mpic16 -p18f452 --fommit-frame-pointer --optimize-goto --optimize-cmp --disab le-warning 85 --obanksel=2 -pleave-reset-vector -I./src -I ./include/c -I ./modules/glcd_font -DDEB UG_MODE=0 modules/libdev/pic18f452.c -o _output/pic18f452.o Processor: 18f452 ./bin/mios-gpasm modifies _output/pic18f452.asm, result in _output/pic18f452__mios-gpasm-tmp.asm sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 -DSTACK_HEAD=0x37f -DSTACK_IRQ_HEAD=0x33f -I ./modules/mios_wrapper module s/mios_wrapper/mios_wrapper.asm -o _output/mios_wrapper.o sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 modules/app_lcd/ks0108/app_lcd.asm -o _output/app_lcd.o sh ./bin/mios-sdcc -c -mpic16 -p18f452 --fommit-frame-pointer --optimize-goto --optimize-cmp --disab le-warning 85 --obanksel=2 -pleave-reset-vector -I./src -I ./include/c -I ./modules/glcd_font -DDEB UG_MODE=0 main.c -o _output/main.o Processor: 18f452 ./bin/mios-gpasm modifies _output/main.asm, result in _output/main__mios-gpasm-tmp.asm sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 modules/glcd_font/glcd_font_big.asm -o _output/glcd_font_big.o sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 modules/glcd_font/glcd_font_knob_icons.asm -o _output/glcd_font_knob_icon s.o gplink -s ./etc/lkr/p18f452.lkr -m -o project.hex _output/pic18f452.o _output/mios_wrapper.o _output /app_lcd.o _output/main.o _output/glcd_font_big.o _output/glcd_font_knob_icons.o error: missing definition for symbol "_GLCD_FONT_METER_ICONS_V", required by "_output/main.o" make: *** [project.hex] Error 1 These fonts are defined in the ...\modules\glcd_font\glcd_font.h: // $Id: glcd_font.h 69 2008-02-01 00:20:18Z tk $ /* * Header File for GLCD Fonts * * ========================================================================== */ #ifndef _GLCD_FONT_H #define _GLCD_FONT_H ///////////////////////////////////////////////////////////////////////////// // Defines array pointers to all available fonts // // (hope that SDCC ignores predefined constants which are not // compiled into the project) // // Pointers are defined as 4-byte arrays. Actually, this is only the font // header, the bitmap data follows after the header, but is not counted // here (not required) ///////////////////////////////////////////////////////////////////////////// extern code char GLCD_FONT_BIG[4]; extern code char GLCD_FONT_SMALL[4]; extern code char GLCD_FONT_KNOB_ICONS[4]; extern code char GLCD_FONT_METER_ICONS_H[4]; extern code char GLCD_FONT_METER_ICONS_V[4]; #endif /* _GLCD_FONT_H */ What should I modify? Best regards, nsunier
  2. I've tried almost all configuration with only the three DOUT modules (with different cables). It's only when I use three modules that it produces boot faillures. One or two modules are ok. This design allows up to four DOUT modules?!
  3. I've tried to remove all DIN modules: CORE -> DOUT (3) -> DOUT (2) -> DOUT (1) It produces the same problem. Sometimes it works, sometimes it doesn't.
  4. I've connected this last DOUT module before the first DIN module: CORE -> DOUT (3) -> DIN (1) -> DIN (2) -> DIN (3) -> DOUT (1) -> DOUT (2) It produces the same problem. Sometimes it works, sometimes it doesn't. I can observe two behaviours: 1. it works, I switch on-off-on quickly, it works again 2. it works, I switch on-off-on slowly (10 sec off), it doesn't works
  5. The problem seems not to be fully solved. The boards are connected together by this way: CORE -> DIN -> DIN -> DIN -> DOUT -> DOUT -> DOUT Almost each DOUT is connected to a LED (>100 LED) Often when I power on the system (without any current limitation: max available current is 3A) all DOUT LED switch on and stay powered and the CORE refuse to boot. When I remove the last DOUT module in the chain all LED blink at startup and the CORE boots without any problem. What can I do? Best regards, nsunier
  6. I've tried first to compile only "ks0108_c_example". An error message told me that "MIOS_BIN_PATH" variable was not set. So I create it in User Variables. The error message disappeared and I got this output message: rm -rf _output/* rm -rf _output rm -rf *.cod *.map *.lst rm -rf *.hex mkdir -p _output sh ./bin/mios-sdcc -c -mpic16 -p18f452 --fommit-frame-pointer --optimize-goto --optimize-cmp --disab le-warning 85 --obanksel=2 -pleave-reset-vector -I./src -I ./include/c -I ./modules/glcd_font -DDEB UG_MODE=0 modules/libdev/pic18f452.c -o _output/pic18f452.o Processor: 18f452 ./bin/mios-gpasm modifies _output/pic18f452.asm, result in _output/pic18f452__mios-gpasm-tmp.asm sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 -DSTACK_HEAD=0x37f -DSTACK_IRQ_HEAD=0x33f -I ./modules/mios_wrapper module s/mios_wrapper/mios_wrapper.asm -o _output/mios_wrapper.o sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 modules/app_lcd/ks0108/app_lcd.asm -o _output/app_lcd.o sh ./bin/mios-sdcc -c -mpic16 -p18f452 --fommit-frame-pointer --optimize-goto --optimize-cmp --disab le-warning 85 --obanksel=2 -pleave-reset-vector -I./src -I ./include/c -I ./modules/glcd_font -DDEB UG_MODE=0 main.c -o _output/main.o Processor: 18f452 ./bin/mios-gpasm modifies _output/main.asm, result in _output/main__mios-gpasm-tmp.asm sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 modules/glcd_font/glcd_font_big.asm -o _output/glcd_font_big.o sh ./bin/mios-gpasm -c -p p18f452 -I./src -I ./include/asm -I ./modules/app_lcd/ks0108 -I ./modules/ glcd_font -DDEBUG_MODE=0 modules/glcd_font/glcd_font_knob_icons.asm -o _output/glcd_font_knob_icon s.o gplink -s ./etc/lkr/p18f452.lkr -m -o project.hex _output/pic18f452.o _output/mios_wrapper.o _output /app_lcd.o _output/main.o _output/glcd_font_big.o _output/glcd_font_knob_icons.o Do you think it's OK? Can I integrate my code? Best regards, nsunier
  7. Makefile generated. Makefile.bat generated. Assembling MIOS SDCC wrapper ========================================================================== Compiling pic18f452.c Processor: 18F452 ========================================================================== Compiling main.c Processor: 18F452 ========================================================================== Linking project error: missing definition for symbol "_GLCD_FONT_KNOB_ICONS", required by "_output\main.o" error: missing definition for symbol "_GLCD_FONT_BIG", required by "_output\main.o" ERROR!
  8. I've included all subfolders of "ks0108_c_example.zip" in my project and included the "glcd_font.h" header. When I do a make, I get this error message: error: missing definition for symbol "_GLCD_FONT_KNOB_ICONS", required by "_output\main.o" error: missing definition for symbol "_GLCD_FONT_BIG", required by "_output\main.o" ERROR! Any idea? Best regards, nsunier
  9. Thank you very much! :) I will try it as soon as possible. Best regards, nsunier
  10. Thank you very much for the link. But it seems to generate only asm code. How can I use it inside my C software? Excuse my question I'm a newbie. best, nsunier
  11. Hi, I'm using a KS0107/KS0108 compatible GLCD with success. I use the following functions: MIOS_LCD_Clear(); MIOS_GLCD_GCursorSet(...,...); MIOS_LCD_PrintCString("..."); But now, I want to define new characters (with custom sizes). I've fund the following functions: MIOS_GLCD_FontInit(); MIOS_LCD_PrintChar(); I've copied the "..\MIOS 1.9\source code\src\mios_glcd_font.xpm" into a subdirectory of my project. I haven't modified anything in this file and executed the "perl convpix.pl -c mios_glcd_font.xpm" script. Then I've modified the "mios_glcd_font.h" file in order to have the same structure as the original one: statis code char * charset = {...,..., ... ,...}; In "main.c", I've included the .h file and written MIOS_GLCD_FontInit(charset); Then: MIOS_LCD_PrintChar(0x00); -> it prints a complete 6-pixel column with random pixels. Why? I haven't fund many informations, examples nor tutorials about GLCD. :-\ Any help is welcome. Thanks! nsunier
  12. If I understand well, I should use the MIOS_AIN_Pin7bitGet function in order to get the AIN states? I don't know in detail how works the MIOS OS. Is it allowed to run this function in the Init()? I'm not sure that the pots are already read... nsunier
  13. Hi, I use the AIN_NotifyChange(unsigned char pin, unsigned int pin_value) function to send MIDI message and update display when a pot is moved. It works quite well. Now, I want, at startup, to do the same thing for each AIN channel in order to send to the PC software the initial AIN channels state. How can I achieve this? Should I call in the Init(void) function (within a loop) the function above or is there another cleaner way to do that? Many thanks in advance for your help. nsunier
  14. I've just found the answer by myself. I was applying a 1A current limitation which is sufficient to supply all boards and all LED turned on. But by this way the inrush current is limited and does not allow the system to boot correctly. I have increased the limitation to max (3A) and it seems to work. Hope it can help someone... Have a nice day! ;) nsunier
  15. Hi, I have: 1x core module 2x ain modules 3x din modules 3x dout modules I've loaded with success the ain64_din128_dout128_v2_0 example code. All seems to work quite well. I use a DC laboratory stabilised power supply (9V). I can switch on the PSU without applying the voltage and I have another switch on PSU in order to enable output voltage. So the voltage has a very small settling time. Often when I power on all DOUT go to 1 and nothing is displayed on LCD. It seems to be freezed. I have to retry 10-15 times until it succeeds. Has someone an idea? Thanks in advance for your help/ideas. nsunier
  16. I'll try it as soon as I have built the AIN/DIN/DOUT modules. Now, only the CORE one is built. I've uploaded the program and I receive MIDI messages. It seems to work well. A big thank you for your help. :) nsunier
  17. And now, I've changed GPutils to 0.13.3b version: Makefile generated. Makefile.bat generated. Assembling MIOS SDCC wrapper ========================================================================== Compiling pic18f452.c Processor: 18F452 ========================================================================== Compiling main.c Processor: 18F452 ========================================================================== Linking project ========================================================================== Converting to project.syx Block 003000-0033FF allocated - Checksum: 06 Block 003400-0037FF allocated - Checksum: 26 Block 003800-003BFF allocated - Checksum: 34 ========================================================================== SUCCESS! It seems to be working?! Just a last question: I don't have the same checksum like you. Is it a problem? nsunier
  18. I've just tried with SDCC 2.5.0. The '--fstack' error disappeared. But the output still shows warnings: Makefile generated. Makefile.bat generated. Assembling MIOS SDCC wrapper ========================================================================== Compiling pic18f452.c Processor: 18F452 _output\pic18f452.asm:168:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:171:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:174:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:177:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:180:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:186:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:189:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:192:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:195:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:198:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:204:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:207:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:210:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:213:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:216:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:222:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:225:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:228:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:231:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:234:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:237:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:243:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:252:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:255:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:264:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:272:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:277:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:285:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:288:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:293:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:296:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:299:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:304:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:309:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:314:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:317:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:320:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:323:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:329:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:334:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:360:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:363:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:366:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:378:Warning [231] No memory has been reserved by this instruction. ========================================================================== Compiling main.c Processor: 18F452 ========================================================================== Linking project ========================================================================== Converting to project.syx Block 003000-0033FF allocated - Checksum: 06 Block 003400-0037FF allocated - Checksum: 26 Block 003800-003BFF allocated - Checksum: 34 ========================================================================== SUCCESS! nsunier
  19. No. Just to be sure, I've deleted every project files and re-downloaded them. It generates exactly the same error. Do you think, I should use another version of GPutils and SDCC? (Where have you find SDCC 2.7.4? On this page, I can see that the latest version (even for Mac) is 2.7.0) nsunier
  20. Ok, I understand. I've also ordered PIC18F452. So it's not a problem. But I've used the PIC18F4620 because I was thinking: 'I'll have less limitations in the future.' So, I'll go back with the PIC18F452. And now, about the compilation problem? I haven't modified yet the source code. So it's a PIC18F452 source code. It should work?! Kind regards, nsunier
  21. Hello, I'm trying to compil the ain64_din128_dout128_v2_0 C example code. I use Windows XP SP2. I've installed GPUTILS 0.13.5; POSIX; SDCC 2.7.0. I go in source code directory and type make: Makefile generated. Makefile.bat generated. Assembling MIOS SDCC wrapper ========================================================================== Compiling pic18f452.c at 1: warning 117: unknown compiler option '--fstack' ignored _output\pic18f452.asm:168:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:171:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:174:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:177:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:180:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:186:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:189:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:192:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:195:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:198:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:204:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:207:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:210:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:213:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:216:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:222:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:225:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:228:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:231:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:234:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:237:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:243:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:252:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:255:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:264:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:272:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:277:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:285:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:288:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:293:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:296:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:299:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:304:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:309:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:314:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:317:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:320:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:323:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:329:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:334:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:360:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:363:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:366:Warning [231] No memory has been reserved by this instruction. _output\pic18f452.asm:378:Warning [231] No memory has been reserved by this instruction. ========================================================================== Compiling main.c at 1: warning 117: unknown compiler option '--fstack' ignored ========================================================================== Linking project ========================================================================== Converting to project.syx Block 003000-0033FF allocated - Checksum: 06 Block 003400-0037FF allocated - Checksum: 26 Block 003800-003BFF allocated - Checksum: 34 ========================================================================== SUCCESS! I'm wondering what's going wrong with this '--fstack' command. Can anyone help me? Another question: I use a PIC 18F4620 instead of 18F452. Should I modifiy only 'main.c' (#include "pic18f452.h" -> #include "pic18f4620.h")? Thanks! ;) nsunier
  22. The Problem seems to be solved! :) I've tried several MIDI configurations with my two MIDI I/O interfaces without any success. I've to admit that they are both crappy interfaces. My PC motherboard doesn't have any Game Port interface. But I was reminded that I have an old Creative Sound Blaster Live! 5.1 Digital sound card. The problem is that I've already another Creative X-Fi XtremeMusic plugged into my PC. I've tried many times to reinstall drivers from both Live! and X-Fi installations CDs. It has generated many problems. It made me crazy! Finally the Game Port appeared in Control Panel but no extra MIDI I/O ports in MIDI-OX... At the end I've tried to install with success alternate drivers: kX Project. Now I've one more MIDI IN port and one more MIDI OUT port in MIDI-OX. I plugged my Game Port - MIDI cable, I made a loopback connection and launch a SysEx transfer... Exactly the same content! Wow, what's a great new! So I connect the CORE module, launch MIOS Studio beta7 and retry: I click on "Wait for upload request before starting upload" and "Smart Mode - Use feedback from core". Then I switch OFF the PSU and click on "Start". After that I switch ON the PSU and... It's fully successful. Yes! Many thanks for your precious help! ;) Please tell me how can I modify the title of this topic in order to add: [sOLVED]? Just an extra question: I've already planned to buy a specific MIDI I/O card. My choice was until now a M-Audio MIDISPORT 2x2. Do you think it's a good choice? (It's the same manufacturer as for my keyboard...:-\) Advise me what model you buy? I want one or two IN/OUT; I want USB interface; I want a small box; I want a not too expensive price; I want a reliable interface (even for SysEx).
  23. When I do a loopback between M-Audio Keystation Pro 88 IN and OUT ports: Here is an attached plot of the M-Audio Keystation Pro 88 MIDI IN port. (alive message = Active Sensing) Now, I do a loopback between BCA2000 OUT and Keystation Pro 88 IN and send a SysEx message (see attached files...). The three screeshots show always the beginning of OUT monitor and the beginning, the first known events and the first SysEx data on IN monitor. Perhaps the BCA2000 MIDI interface is crappy?!
  24. Just to explain: My PC doesn't have any MIDI I/O connectors. Yes, on motherboard, there is the game port (= MIDI I/O) but I don't have the adapter to plug into. So I have an external sound card with one MIDI IN port and 2 MIDI OUT ports: the Behringer BCA2000. On other hand I have a MIDI controller/keyboard which have one MIDI IN port and one MIDI OUT port: the M-Audio Keystation Pro 88. Both of them are connected to the PC by the mean of USB. Both of them could be used as MIDI IN/OUT interface. They are listed in MIDI-OX (see attached file...)
  25. TEST PROG1: OK Done with the Forest Electronics USB Prog'r+ programmer software. If you are not sure that the bootstrap loader has been burned successfully, use the verify function of IC-Prog/P18 TEST CORE1: OK I've measured the 10MHz by the mean of a scope. ensure that you've stuffed a 10 MHz crystal (parallel cut) to your PIC18F core module TEST CORE2: N/A only relevant for MBHP_CORE_V1 and MBHP_CORE_V2 PCB: are all 5 jumpers connected to the programming port? TEST CORE3: OK Check it visually for bad solderings or missed junctions TEST CORE4: OK 5V measured on each test point -> VDD OK. Check Vdd of the power supply. TEST CORE5: OK 5V measured on each test point -> ground OK Check the ground of the power supply. TEST CORE6: OK (There is a mistake in the mbhp_core_extract_midi_plugs.gif file: 2x M- for MIDI Out !?) Check the polarity of your MIDI plugs. TEST CORE7: OK Check the polarity of the protection diode D1. TEST CORE8: OK Check the resistor values at the MIDI Out Port: R8 and R7=220 Ohm (resistor code: red-red-brown) TEST CORE9: OK? My cables are 1:1 (pin 1 = pin 1; pin 2 = pin 2; ...). On the mbhp_core_midi_crosslink.gif file: pin 4 = pin 5; pin 5 = pin 4 !? Just to ensure: this diagram shows a crosslink between the core module and your PC: TEST CORE10: OK If you notice a lot of request messages like shown in this snapshot, then there is a short circuit between the Rx and Tx pin of the PIC. Check the tracks which are routed from the MIDI-Link port J11 to the Rx/Tx pins for direct connections (see the layout and schematic), you could scratch with a screw driver between the tracks to ensure that they are not connected together. TEST CORE11: OK The code upload can also fail if no, or a too small bypass cap is connected to the power rails of the PIC. A possible effect is, that for example "F0 F0 F0 F0 7E F0 00 01" will be sent by the PIC instead of the proper SysEx string "F0 00 00 7E 40 ... F7". Another effect could be, that something is received by your MIDI interface, but not displayed by the MIDI monitor because of the invalid MIDI event structure. This all can happen even when the IO and Software loopback test which is discussed below is passing, If this happens, check that the 2200 uF cap (C5 of the core module) is soldered properly. If you are unsure about the state of the cap, since you've re-used it from an old device, try another one. If you are using the optimized PSU for MIDIbox SID, bypass the outer pins of the (not mounted) 7805, so that C5 has contact with the +5V/Ground rails (see also mbhp_4xsid_c64_psu_optimized.pdf)! TEST OUT1: OK A small pulse occurs every 2 seconds. Connect a LED to your MIDI Out port and check if it flickers: mbhp_core_extract_out_led.gif TEST OUT2: OK good quality PSU Somebody noticed in the forum, that the MIDI Out of his core module didn't work because of an "incompatibility issue" with the bench supply he used and the switching PSU of his PC. The solution was to disconnect the middle pin of J12 (ground line of MIDI Out port) TEST PC1: OK Checked with two different MIDI I/O interface. check the MIDI-Ox configuration - have you select the correct ports? TEST PC2: OK? Please look at the attached files... Is it correct or not? ensure that the MIDI interface of your computer is working: loopback the MIDI Out of your PC to the MIDI In of your PC and send any SysEx dump by using the "Send/Receive SysEx" function of MIDI-Ox. The number of sent bytes must match with the number of received bytes. If it doesn't match, search for a new driver for your MIDI interface/sound card. If not available, you can possibly fix this problem by lowering the Low Level Output Buffer size (normaly set to 2048) and by increasing the output delay (normaly set to 0 ms) in the MIDI-Ox SysEx configuration menu The next test/check results will be posted as soon as possible... I've tried with two MIDI I/O interfaces: Behringer BCA2000 M-Audio Keystation Pro 88 (I can't use it's MIDI OUT port since it sends a alive message every few seconds)
×
×
  • Create New...