Random Midi Messages (midibox64)

Testing/Troubleshooting
1

Hey there, I just built a core kit from smash tv. I tested it and I have been able to upload the MB64 app successfully. I am using 4 pots just to test it out and have the rest of the inputs grounded; no mux. I have verified connectivity with my multimeter and inputs A4-A7 are rightfully grounded.

My problem is that I am getting random midi messages. When i boot up the device, it boots up normal and without touching anything, my lcd display says:

[int] N ________

Reverb # 1    0_

So then i turn a knob and BLAM… random midi messages galore!

On bootup i get an upload request… then this after turning a knob in MIOS Studio.

00000000110663 ms | [bB 5D 21] Channel 12: CC Effects 3 Depth value: 33

00000000110664 ms | [bC 5D 21] Channel 13: CC Effects 3 Depth value: 33

00000000110666 ms | [bD 5D 21] Channel 14: CC Effects 3 Depth value: 33

00000000110666 ms | [bF 5D 21] Channel 16: CC Effects 3 Depth value: 33

00000000110675 ms | [bD 5D 22] Channel 14: CC Effects 3 Depth value: 34

00000000110677 ms | [b8 5D 23] Channel 9: CC Effects 3 Depth value: 35

00000000110680 ms | [b9 5D 23] Channel 10: CC Effects 3 Depth value: 35

00000000110681 ms | [bA 5D 23] Channel 11: CC Effects 3 Depth value: 35

00000000110682 ms | [bB 5D 23] Channel 12: CC Effects 3 Depth value: 35

00000000110683 ms | [bC 5D 23] Channel 13: CC Effects 3 Depth value: 35

00000000110684 ms | [bE 5D 23] Channel 15: CC Effects 3 Depth value: 35

00000000110685 ms | [bF 5D 23] Channel 16: CC Effects 3 Depth value: 35

00000000110690 ms | [bE 5D 24] Channel 15: CC Effects 3 Depth value: 36

00000000110693 ms | [bF 5D 24] Channel 16: CC Effects 3 Depth value: 36

00000000110697 ms | [b8 5D 24] Channel 9: CC Effects 3 Depth value: 36

00000000110699 ms | [b9 5D 24] Channel 10: CC Effects 3 Depth value: 36

00000000110700 ms | [bA 5D 24] Channel 11: CC Effects 3 Depth value: 36

00000000110701 ms | [bB 5D 24] Channel 12: CC Effects 3 Depth value: 36

00000000110702 ms | [bC 5D 24] Channel 13: CC Effects 3 Depth value: 36

00000000110702 ms | [bD 5D 24] Channel 14: CC Effects 3 Depth value: 36

00000000110708 ms | [bC 5D 26] Channel 13: CC Effects 3 Depth value: 38

00000000110711 ms | [bD 5D 26] Channel 14: CC Effects 3 Depth value: 38

I get a lot more than that. Any clues to what’s happening? I did a search on random midi messages, but I don’t see what I’m missing. I even checked the pins of A4-A7 to make sure they’re connected to Vss.

I’M STUMPED!

a little help please?

2

Until somebody better informed replies, it occurs to me that the default MB64 config uses muxed analogue in’s (via AIN modules).

Have you compiled your own version of MB64 and replaced: 

#define DEFAULT_MUX_ENABLED 1

with

#define DEFAULT_MUX_ENABLED 0

in main.inc?

3

i actually did that under “setup_midibox64.asm”

4

Sorry that’s what I meant, you are quite correct it is in setup_midibox64.asm!!!

I was just checking that you had compiled your own app and were not just using the downloaded version unchanged :slight_smile:

Sorry but I have never used unmuxed analogue inputs on my midibox projects so I can’t really offer any suggestions other than the things you have already tried, i’m sure somebody else will chime in though :slight_smile:

Phil

5

could someone at least tell me if this is a software issue or a hardware issue?  ???

i’ve inspected each solder point thoroughly to make sure i don’t have a hidden cold solder. but i really don’t think that is the issue because the actual pins of the chip have a connection with Vss --the ones that have no pots.

I’ve reread the code in the setup asm, but i don’t see an issue popping out at me. i have a hunch it has to do with the code. is it safe to remove complete blocks of the code. in other words, can i just have the code for the four pots and the lcd? that means taking out all the code for stuff i don’t use like DOUT, DIN, and AOUT?

Am I going in the right direction?

6

After making the change mentioned, did you re-compile the program?

I see at least six different controllers in your example results, that seems

to be a bit more than four. :slight_smile:

You mentioned there’s a lot more after that. How many different controllers/channels are there in your “random” messages?

Good Luck,

LyleHaze

7

why would i need to recompile? don’t I have to open it up in wordpad, edit it, and save it? then I just upload the hex file.

8

why would i need to recompile? don’t I have to open it up in wordpad, edit it, and save it? then I just upload the hex file.

errr… yes you need

are you expecting the .hex file to update magically by itself? Just have a look at the creating date of the file, you ll see it hasn t changed and it s probably older than the files you changed.

Also if you are using mios studio, you ll be warned that the new hex file has changed since the last upload.

There is plenty of info about how to compile and create new hex files.

Simone

9

If you want to understand why, perhaps you could study the difference between “interpreted” languages and “compiled” languages.

We are working here with a compiled language, and it will need to be re-compiled for any changes to take effect.

If it were an interpreted language, then it would work as you described.

On the bright side, I think it’s safe to say we found the problem. :slight_smile:

Once you get the compiler set up and working, you’ll be ready to get your MB64 working just the way you want it to. You’ll find everything you need in the FAQ pages of this website.

Have Fun,

LyleHaze