Who sees my stupid mistake?

[RuudNL]

The 16384+12 is correct, I have used that before.
The calculation is: (1.000.000/Baudrate) - 20 , so 1.000.000 / 31250 = 32 -20 = 12.
For inverted output set bit 14, = 16384.
But even with a different baudrate I don't get any output.

I did a quick test to trace the problem.
With this code, nothing 'toggles':

Progstart: 
  if PORTB.0 = 1 then 
    Toggle PORTB.6
  endif  

Debounce:
  Pause 20                                       ' ? shorter ?
  If PORTB.0=1 then
    goto Debounce                                ' Button still pressed?
  endif  
  Goto Progstart

So I suspect the problem is in the line (and similar lines)

  If PORTB.0=1 then

Although I don't see what could be wrong with this...

[Demon]

If I don't touch programming for a while, I start with blinking a LED to make sure I have the basics working right (config, circuit, programming, etc).

[Demon]

...
If PORTB.0=1
...

You're assuming it can read port B properly.

I'd start even easier, just blink a LED, nothing else, then build from that.

[RuudNL]

So nobody can spot a mistake in my sample code?
Strange, because this line is handled correctly:

If (PORTB.0=1) or (PORTB.1=1) or (PORTB.2=1) or (PORTB.3=1) or (PORTB.4=1) then
.....

[Demon]

I pulled out one of my old 16F628 programs from mothballs, only thing I notice, you have no CONFIG statements.


EDIT: I used this with DEFINE OSC 20

@ __CONFIG _HS_OSC & _WDT_OFF & _PWRTE_ON & _BODEN_ON & _MCLRE_ON & _LVP_OFF & _CP_OFF

[RuudNL]

I set the config parameters in the programmer (as usual).
The values you mentioned are the defaults in my programmer, except the HS mode, that I set manually.
The point is that everything (almost) works.
If I create a loop that does nothing else than: serout2 xxx, delay 1000, I get MIDI information every second.
My main suspect is that the switch(es) are not read correctly in: if PORTB.x =1 then ...

[Demon]

Is this the "read modify write" problem?
(I have to look that up whenever I encounter weird problems)

[Demon]

I set the config parameters in the programmer (as usual)...

What if you set them in the program? Maybe something is wonky with your programmer config. (total wild guess, just eliminating stuff)

[Demon]

...If I create a loop that does nothing else than: serout2 xxx, delay 1000, I get MIDI information every second.
My main suspect is that the switch(es) are not read correctly in: if PORTB.x =1 then ...

Blinking a LED confirms if your timing is running at the speed you think it's running at.

I usually go for LED 1/2 second OFF, 1/2 second ON, just to know my OSC is running as it's supposed to.

EDIT: Hm, yeah, but you're getting a SEROUT every second already, so not sure what else to check.

[RuudNL]

I never had problems setting the config parameters in the programmer, but I will try that anyway...
I have a feeling that the problem is in the line:

  if PORTB.0 = 1 then   '<---- this line?
    Serout2 PORTB.7, 16384+12, [144, 44, 127]    ' Rewind
  endif

The strange thing is that the switch status IS correctly read in this part:

Debounce:
  Pause 20                                          ' ? shorter ?
  If (PORTB.0=1) or (PORTB.1=1) or (PORTB.2=1) or (PORTB.3=1) or (PORTB.4=1) then
    PORTB.6 = 1                                   ' ADDED TO CHECK!! 
    goto Debounce                                ' Button still pressed?
  else
    PORTB.6 = 0                                   ' ADDED TO CHECK!!
  endif  
  Goto Progstart

So PORTB.6 is high as long as a button is pressed.

And a loop Serout xxx/ Pause 1000 spits out a burst of MIDI data every second, so it doesn't look it is a config problem.