Jump to content

Recommended Posts

Posted

Hi Everyone !

When I bought my first PIC - my friend programmed it on a prof. programmer.

When I put it into the socket (CORE) I was getting the 'sign of life' from PIC. But when I tried to send MIOS via MIDI something messed up and

it started to send some pitch and reset data (weird..). So I built MBPH_BURNER and  I tried to program it again (since my friend couldn't program it again for me :( )

Now - when I try do burn bootstraploader into my PIC18F452 it verifies it as ok.

But when I read my chip - the config bytes are different from those from bootstraploader.hex

(they are always  2600 0F0F 0100 0081 C00F E00F 400F). I tried it on 4 different PIC's - alway the same result.

When I put PIC into the CORE's socket there is no "sign of life" and my MIDI IN port do not read anything (my MIDI is working fine - I've made loopback tests).

So what could be the problem? Is it the false CONFIG or did something blown-up when I tried to upload MIOS via MIDI ?

I checked PCB - it seems to be ok.

Please help me if You can, cause I cannot sleep anymore because of this ;)

best regards, smycza

Posted

Hi,

you can ignore this mismatch, in the .hex file all unimplemented bits in the config sector are 1, but the PIC returns 0 for such bits

Best Regards, Thorsten.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...