Jump to content

Recommended Posts

Posted

Hello all,

 

I almost completed my MB6582 and I am stuck at testing the main board.

My idea is testing the PICs are running before inserting the precious SIDs.

 

I flashed all 4 chips with "setup_mb6582.hex", but nothing happen on the LCD...

 

I also flashed the 1kHz test FW --> nothing... :no:

 

Supply voltage is OK on all pins and MCLR (pin 1) is high as expected.

 

Cannot see any waveform at the oscillator's pins (10MHz XTAL and 33pF caps are OK).

I would say the internal oscillator is not set for external xtal...

 

Anyone got a similar problem starting from blank PICs?

 

Thank you,

 

Walter

Posted

I got the PICs as free samples several years ago from Microchip.

 

I can successfully erase, program and verify them through Pickit3 & MPLAB IPE.

 

Maybe I am wrong, but I assumed I just need to flash the "setup_mb6582.hex" FW to make them working in the MB6582...

 

Initially I was in doubt about the LCD (although it works fine on another circuit) and I decided to flash the 1kHz test FW to check basic activity on the PICs.

As said, nothing happens...

Posted

Oops! In this case I misunderstood...

 

Therefore there is no way to flash the PICs with the MB6582 application directly?

 

If not, I still have to find out a suitable USB-to-MIDI converter...

 

Any advice?

It read most of the (cheap) converters are not good...

Posted

If you can flash the MB6582 hex, you can flash the bootloader hex (and then upload the MB6582 app, and many other midibox apps, via midi). See here for more info:

http://ucapps.de/mios_bootstrap.html

 

You can download the bootloader (mios_v1_9h.zip) here:

http://ucapps.de/mios_download.html

 

As to the USB-MIDI interface, there's a non-exhaustive white list:

http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_whitelist

 

...and black list:

http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist

Posted (edited)

jjonas is right but doesn't give you enough information.  It's been a long time that I have done this, but looking at the code this is what I see.  In the  mios_v1_9h.zip file are directories for each supported PIC.  As you select your path, you will come to a "BURNER" directory.  This is the one that must be programmed first.  The hex file is something like "bootloader_v1_2b_pic18f4620.hex".  It should contain all the CONFIG parameters needed to set the oscillator options in the PIC.  After that you can then program the MIOS hex file for v1.9h  which is in the "MIDI" directory and called something like "mios8_v1_9h_pic18f4620.hex".

 

Note: programming this way gives and ID value of " #define PICID_DEVICE_ID   0x00 "

If I am wrong, someone please respond.

 

Pete

Edited by kpete
Posted

Hi all,

 

it seems a neverending story... Very strange I am the only one facing with these problems!

 

I successfully flashed the bootloader into all the 4 PICs via Pickit3. The 10MHz clock is OK --> so far, so good.

 

I installed MIOS Studio V2 and I connected the MIDI connectors to the PC.

 

I uploaded MIOS8 on the CORE1 PIC and the upload seems working fine: CORE1 is detected by MIOS Studio.

 

Problem #1: if I reset the board and re-launch MIOS, CORE1 is no longer detected...

 

Problem #2: I am not able to upload MIOS8 into all PICs by leaving them on their MB6582 sockets. Also acting on J11 to assign the MIDI port to a different PIC has no effect. The only way to upload MIOS is moving the PICs in turn on CORE1 site...

Posted

There's a hex file you can send via MIOS to change the headers. Once each has the correct ID you can address the intended PIC using the "Device ID" box on the middle-left of MIOS studio. I always query the PIC to make sure the transfer works properly before uploading hex.

Posted

Something is going the right way...

 

Let me summarize my steps up to now, in case it could help somebody else:

 

1) All PICs flashed with the bootloader (BURNER folder): http://ucapps.de/mios/mios_v1_9h.zip

 

2) MIOS8 loaded into all PICs via MIOS Studio (MIDI folder): http://ucapps.de/mios/mios_v1_9h.zip

 

3) Assigned different IDs (0 through 3) by loading the pre-compiled HEX I found here: http://ucapps.de/mios/change_id_v1_9g.zip

 

4) Uploaded MB6582 application (setup_MB6582.hex): http://ucapps.de/mios/midibox_sid_v2_044.zip

 

 

Steps #1 through #3 have been performed by placing each PIC on CORE1 socket in turn.

 

Step #4 has been performed after placing each PIC on their respective CORE socket.

 

At power-on I get the MB6582 messages on the LCD, but only 2nd and 3rd rows are used...

 

After uploading MIOS8 1st and 2nd rows were showing the message, therefore I guess the problem is now setting properly the LCD for 20x4.

 

Please correct me if I am wrong.

Posted

Another doubt...

 

According to what is written here

http://www.midibox.org/dokuwiki/doku.php?id=wilba_mb_6582

under Q&A, only the master (ID=0) has to be loaded with MB-SIV V2.

The slaves should be "cloned" by the master via CAN.

 

I connected the LCD to each slave and I still get messages from the change-ID application ("New ID Header: 0000...0001").

Is this correct?

 

Or do I have to upload MB-SID V2 into the slaves also?

 

Sorry to bother you all with all these silly questions... :sad:

Posted

From memory you have to get the SID application on every Core individually at the first install. Afterwards you can "clone" updates via CAN (I guess CAN isn't configured otherwise).

 

Nearly there I think!  :flowers:

Posted

Uploaded MB-SID V2 on all the PICs via MISO Studio.

 

Now the slaves show "CS not enabled!", while the master shows again the MB-SID menu, but limited to rows 2 & 3...  :sick:

 

I am working on the mother board only now, no control board connected... Is this a problem?

Posted (edited)

Isn't it normal that CS isn't enabled for the slaves? The CS can only control/be controlled by one PIC at a time, and that data is forwarded to the others when required (as far as I know). I don't know what's happening with the LCD sorry, but you should check the wiring.

Edited by latigid on
Posted

The display is a Wintek WM-C2004R, using a HD44780 equivalent.

 

The LCD is good, as the message correctly starts at 1st row when the MIOS8 is loaded...

 

8-bit operation should be considered in case the LCD freezes... not my case... 

 

Here is what I see:

 

ROW #1: "                                 "

ROW #2: "E002|PInt Ld  Chn. 1"

ROW #3: "1---|Lead Patch        "

ROW #4: "                                 "

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...