Shum

Hi Thorsten It was carless of me that I missed changing the first line of the code. It is fine now, thanks a lot. Best regards Shum

Hi Thorsten, Since the Yamaha driver is only Win 3.1 compatible, could not get it to work on winxp. I used another serial driver meant for win98/Xp and it works. The midi merger-RS232 combination makes a good serial to midi interface. The unit that I built can be used as a midi merger as well as a serial midi interface. Thanks again Best regards Shum

Hi Thorsten, I looked at the main.asm file in the midibox64 application and replaced the code as recommended (for 2x24 LCD). Using MPLAB, I recompiled the main.asm file to build the main.hex file. This was done successfully. I then uploaded this file through MIOSStudio into the pic. Mios rebooted, but the LCD display remains at 2x16 configuration. I searched through the readme file but could not find information on LCD setting. Could I be doing something incorrect here?. Thanks Best regards Shum

Hi, My MIOS midibox64 is up and running, however as I am using a 2x24 LCD, the image presented is not at the center. How to make modification on the firmware to center the display. Thanks Best regards Shum

Hi Thorsten, Thanks for the infromation. Best regards Shum

Hi, I was looking for a serial to midi interface, and I built one based on the midimerger using pic16f877-20 and a MAX232 chip. The unit itself is working, I also downloaded the Yamaha driver. But how to get the interface working via the serial port (using com port 2). Thanks Best regards Shum

Hi Thorsten, Loaded the bootloader with burner to the pic. Uploaded MIOS with MIOS Studio_v7 successfully. Thereafter uploaded the midibox64 application without fail. The uploading was very smooth and fast. I got the feeling that the pic18f452 is more susceptible to noise than the older 16f877. For those who are using switching power supply unit to power the core, there is a need to have additional smoothing and noise trap circuit to ensure the quality of the supply. I took the liberty to include here an additional circuit for those who are going to use switching power supply. This is in response to Digispunk's posting Best regards Shum

Hi Thorsten, Michael and Stryd_one, Something simple and overlook!. It was the power supply unit. I measured the output voltage it registered 12V DC. It was because the same psu was used on the old pic16f877, it led me to believe that it was fine. Having read all the suggestions that were given, I finally measured the output with a scope. To my horrior, the ripple on the DC output was very high. I later found that the smoothing cap. was OC. I replaced it with a new 1000uf 25V and ripple was gone. Powered up the core and uploaded the MIOS. This time around it was easy and there was no error and the LCD showed "ready". I uploaded the main.syx for midibox64 and T.Thorsten came on the LCD. I appreciate all the help given to me and thanks guys! :) Best Regards Shum

Hi Thorsten, I am sorry that I did not reply to the email. I did use the script from the Mios V1-9_SCR. I use the main.asm file to generate the hex file using the MPLAB. The I uploaded it to the core, however it failed to work as well. Since I have tried all the tools to upload MIOS, including the one from the SCR package and fail, it was too embarrasing to mentioned it. I looked through troubshooting guide and those from the forum postings I got the feeling the my SB AWE64 sound card/driver may be the problem (though it work on the old pic16f877 - midibox64 and also on syx transfer of soundbanks on my WX5 and VL70M). I have the following snap shorts from midiox - the result of the MIOS upload. I may have to buy another sound card, do you have any suggestions what I should buy or should I build the USB-Midi module? Thanks Regards Shum

Hi Michael, I tried to upload the MIOS you sent me to the core via the syxexBox, and I got the result as shown in the attach pics.

Hi Michael, I have not uploaded the MIOS to the core yet. I want to be sure the MIOS.syx file is converted correctly first. :) I typed in the following syntax "perl hex2syx.pl mios_v1_9_pic18f452.hex -os_upload" to start the conversion. As I mentioned before, at the end of the conversion, I got an error message warning me that I am trying to overwrite the Bootloader range! That means to say I cannot use the converted MIOS.syx file for the upload. If so how do I overcome this error? ??? BTW how do I insert images on this posting/reply Thanks Regards Shum

Hi Thorsten and Michael, I started from scratch again and burnt the bootloder v1_2_pic18542 into the pic. Plug it into the core and power on and I got the upload request. I reconvert the MIOS hex to syx, at the end of the conversion there is an error message that says "you are trying to overwrite the Bootloader range! If you are using a 64k pic device add -mem_64k!" If I upload the MIOS it would overwrite the bootloader is'nt it. Is there something I must do first before converting MIOS hex to syx? ??? Ps I have the images but how I can attach them to this posting? Hi Stry_one I take it that you are a Japanese food fan! ;) Regards Shum

Hi Thorsten, Thanks for the advice. Yes all the links of J3 are closed. How can I tell if the PC interface is running at incorrect baudrate. For information, I tried uploading the MIOS from different PC but also failed. Is it likely that the problem is in the conversion of the HEX to SYX file? Thorsten could you send me the MIOS syx file through email so that I can try it on the core again. Tell me, if it were the power supply (12v at 500 mA) or the USART problem, should I not have problem with the old pic16f877? Think I will leave this project aside to clear my mind. I will start afresh to check all the steps I had taken to troubleshoot. By the way Stryd_one, I miss typed the word MIOS as MISO. Perhaps I have had to much of Japanese food recently. Thanks for the help everyone and with best regards. Shum

Hi Thersten, Thanks a lot for your help through the email. I have taken too much of your time already so I come to the forum to seek assistance. The core I built is based on MBHP CORE V2b © T.Klose 2002-06-23. Initially I used the pic16f877-20 with the old midibox64 firmware to control the B4 synth. However, I am trying to migrate to the new pic with mios as it provides more memory and features. The problem that I am having is similar to the one posted by Digispunk. The core with the pic18f452 is with the bootloader burnt in and it sends out uploading request every 2 seconds. This seems that the core is functioning (LCD blank). However, I have problem uploading mios like what was mentioned by Digispunk. I do not know where I have gone wrong. The following was what I did; 1. Burnt bootloader V1_2 (new pic) 2. Plug pic in core and powed up - core sends out request message 3. Power off core. Open up Miso Studio and load mios v_1_9 hex file 4. Routed midi in/out accordingly 5. Checked the wait for uploading request box 6. Checked the with feedback from core 7. Click start on the Miso Studio 8. power up the core The result - Mios Studio receives sysx date with check sum without error for few blocks. Thereafter Mios Studio receives enexpected mios sysex message as such - F0 F0 F0 F0 7E F0 00 01, expected is 00 00 7E 40 00. After 3 times the upload stops. Thanks Shum

Hi, I have built the midibox64 core based on the new pic18f452 chip. To test if the core works, I pluged in my pic16f877 programmed with the old firmware, the LCD came to live and it works. This confirms the the core is ok. I burnt the bootloader_v1_2_pic18f452.hex into the pic18f452 using the MBHP burner without problem. The core sends out an upload request after power on. However when I upload the mios_v1_9_pic18f452.hex through the miosstudio, it somehow receives unexpected mios sysex message from the core and stops after awhile. I re-burnt the bootloader and uploaded the mios again, the problem ancountered. I am at a lost grateful someone can help, please Shum