Jump to content

Recommended Posts

Posted

I connect core via gameport. Till yesterday I was able to upload apps. Then I connected both DIN modules and soldered encoders. After that my MB has started to behave strangely. I thought it was core not configured. But when I tried to upload new main.hex, i wasn't able. I disconnected DINs and still no luck.

Done troubleshooting excluding steps involving optocoupler, as I do not have it connected, as I use 1:1 gameport connection.

Shortening pins on game port connector works. Shortening RX TX pins works. Cable is OK. I do recieve upload request after start up.

Could it be that I fried some portion of PIC? Is there a way to check it?

EDIT: One more thing I noticed, when i disconnect power I get one or combination of following.

 00000AE8  10  --     FE    --    --   --  ---  Active Sensing
 000023B6  10  --     FC    --    --   --  ---  Stop                 
 000023B8  10  --     FF    --    --   --  ---  System Reset
 000449BE  10  --     F8    --    --   --  ---  Timing Clock 

Is it normal?

Posted

Success!

It seems I really messed up PIC. After replacing it and some debugging I now have 99.9% working MidiBox. Have to replace one multiplexer before it is 100% :)

Posted

You wrote, that the old PIC sends an upload request during startup. This means, that you should be able to upload MIOS and the application again, right?

Maybe the upload was errornous during the first try, MIOS Studio normaly reports this, did you notice any special message?

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...