surei

Hallo Thorsten, thanks for the answer. Too bad, though! But at least it works with XP32 ;-) Best regards Reiner

Hallo Thorsten, many thanks for your answer. Actually, I did search, but perhaps not thoroughly enough, sorry. It did turn up a large number of things, but nothing seemed to answer the question. Anyway, I was wrong about the boot message (meaning the MIOS copyright message). It actually displayed he first eight characters of each line of it. It did look funny, but it didn't occured to me it was wrong. So all is cleared up, and as you said, it's easy to work around it once you know it behaves that way. So the thingy is working fine now. Thanks Reiner

After testing with the other application it showed the same behaviour, only eight characters are displayed. But I found out what's happening: The driver is treating the 16 characters as if they are two lines of eight characters each! Hence, when setting the cursor position to 0x40, it prints on the right hand side of the display. Not quite what I would expect, but I can certainly live with that. Makes me wonder though why the MIOS boot message comes out using all 16 characters ?? BTW: The datasheet says its a KS0066 or compatible Many thanks Reiner

Hi all, I just got my PIC USB board working. On an XP32 notebook the PIC was recognised with the bootloader loaded, and I was able to upload the PIC USB application. Then, after a reset, the device gets recognised as a USB audio device, and the driver installed properly. So I guess it is basically working correctly. Now I do want to use this thing on a machine running x64. But now it doesn't get recognised as a USB audio device, but Windows says its a MBHP USB PIC, followed by USB composite device. It then shows the driver install dialog, but I do not know what driver I can install and how. Hence the question: Should this work in x64, and if, how do I get it to work? Many thanks Reiner

no, its a different application, but I can try that this evening.

Hi, I connected a 16x1 character display (standard LCD 16x1 from Reichelt) to a core, and I can only get the first 8 digits to work. Interestingly enough, when booting, the MIOS message uses all 16 characters (so hardware problems can be safely excluded), but once the application loads, only 8 digits work. Also, when rebooting after uploading the application, it only displays "rebootin" (the 'g' missing, as it is the ninth character). Any idea? BTW, the 16x2 display from Reichelt is working fine on another core modul, and I did not have any problems getting that to work as expected. Thanks for your help Reiner

Mistery solved, and again a silly mistake! I wired the 220Ohm resistor from Pin 4 of MIDI Out to 0V instead of +5V. Now it works fine, thanks for your patience! Best regards Reiner

HalloThorsten, it is a Saffire LE, and it is working fine with another MIDIbox. However, I just did the INOUTtest shortening Rx and Tx on the board and it fails miserably. I sent some simple controller messages out using MIDIox, and got backtotal garbage. So where do I look next? Thanks so far (now I know it can't be the PIC) Reiner

That would certainly be a logical explanation, but how could this be? The PIC was preburned by SmashTV with ID 000 000 000 0001, so everything default except the Device-ID. Besides, shouldn't the MIDI In fail also in this case? Since I can upload applications and Mos to the PIC with Mios studio (in manual mode), the MIDI In is obviously working. What's the easiest way to check this setting? Thanks again Reiner

I'm using the 10MHz for the PIC18F452, which I think is correct, right? I shtere an easy way to check for the baudrate? Can't use MIOS-Studio for testing, since it cannot read the input. I also tried reburning the chip with the PIC burner, using the bootloader that comes with the MIOS 1.9f download. The burner claimed success and when plugging it backI do get these garbled messages every two seconds. So where else could the baudrate be set? THanks for your help Reiner

Actually I did try it, and I did not get anything when I switched the polarity. Reiner

Well, silly me! I put a 10Mhz crystal on the board for the PIC18F4550, but it needs a 20MHz. Changing that should solve the issue. Thanks Reiner

Hi, I have build the PIC USB, since I can live with the documented bugs (I don't plan to send any sysex with it). I burned the microchip USB bootloader onto the PIC (4550) with the burner, and it verified OK. WHen I connect it to the PC via the USB cable, the HowTo says Windows should find the new device and ask for a driver. However, nothing happens. Is there any way I can debug this? The hardware is simple enough to be checked by eye, and none of the connections is missing. The reset button also doesn't help, but I would hope for the bootloader to start running after powering up (via USB) anyway. Voltages on the clock pins are somewhere between 0 and 5, so I assume the clock is working. BTW, does anybody know if the microchip USB driver for this works on 64? If not I guess I cannot upload the application to the chip, correct? If I upload it from a different PC, will the PIC USB application work on X64? (It is using a standard Windows driver, isn't it?) Any ideas? Best regards Reiner

Hi all, I just put together a small circuit based on the MIDIbox PIC-core that is suspposed to just read in a few pots and put this out via MIDI. In addition, I put a second PIC for the USB out on the same VERO-board, but that's another story. The PIC was preburned by SmashTV, so I expect it to be fine. In my attempt to solve the problem, I reburned the bootloader into it anyway using the PIC burner (which I had built to burn the 4550 chip for the USB out), but the problem remains. Here is what happens: The MIDI in and out do show something, MIDI in works fine, as I can upload MIOS and application using MIDIStudio, when using manual mode (not waiting for requests fromPIC). MIDI OUT is producing nonsense though. Instead of the normal upload request from the bootloader I get "FF FF FD", and that's it. It does repeat every two seconds as it should, and the string is always identical, so there is no random error here. Loading an application that is just supposed to send the same message every time a pot is turned, will sen a message every time I turn the pot, but again it is entirely different from what I have programmed it to send. This time the message is changed at random. I do assume a hardware problem here. Obviously the polarity must be correct, otherwise I would not get anything. I do not have a scope to check the signals. Any idea? Many thanks Reiner