how to Reset PIC chip without resetting bootstrap!?

[SynnyS]

Hi guys, I've built myself a Ain+Core as a sort of cv to midi converter to control ableton live with a huge project with large buttons and switches. (for me eductaion)

Now i know that i've uploaded mios correctly as i received the correct sysex message afterwards when powering up the core.

But since then i've uploaded the main.syx from midibox64 v 2.4 zip and some controller info and everything went wrong.

i think i've uploaded everything about 5 a 10 times, so i haven't got a clou what the hell is inside that pic at the moment.

Just yesterday morning it was spitting out random sysex at a very very hight rate, that was because i forgot to clamp j5b to the ground.

but now i clamped all the 32 inputs but one, to the ground and i hooked up a little pot moeter of 10k to that 1 input.

when i power up the core now, it gives one sysex msg. nothing happens. then when i move the potmeter just for  little bit.

It gives out midi data again, but this time not random. In my case it spits reverb depth (in midi ox), but continuous! is doenst stop giving out that data!

all at a very low level. between 00 and 04  and occasionly a 7F.

My question : is there a way to completely reset the pic chip without deleting the bootstrap loader, coz i don't have a pic burner....

2nd question..: does any body have an idea, or a good suggestion for me what to do alternately?

My frustrations are beginning to grow coz i have a dead line on friday and an even bigger dead line next wednesday so it has to work, very very soon....

anybody body please help!!?

[Wisefire]

send a dummy program through midi..

[stryd_one]

Sounds very interesting :)

When you upload MIOS (the Operating system, not the application) that will clear the PIC and bring it back to new. Then you can upload the application (MB64) you should be all good. If it still does this, you might have a problem with some solder joints. Do you have a multimeter there?

[SynnyS]

Sounds very interesting :)

When you upload MIOS (the Operating system, not the application) that will clear the PIC and bring it back to new. Then you can upload the application (MB64) you should be all good. If it still does this, you might have a problem with some solder joints. Do you have a multimeter there?

Ooh that's something i didn't know! I'll try is out from the start! thnx, and yes i do have a multi meter ;)

[audiocommander]

My question : is there a way to completely reset the pic chip without deleting the bootstrap loader, coz i don't have a pic burner....

MIOS is separated into 2 different bootstrap-loaders, the first one is burnet into the chip, and the second one is part of MIOS and active for about 2 seconds (when you see the copyright message). If you send another appliction (eg one c-app of the download section) in these two seconds by SysEx, you'll have a shiny new program on the chip :)

Alternatively you could upload MIOS itself again, but that would be a bit of an overkill if MIOS itself isn't damaged. ;)

Test with one of the default applications (from the download-section)! If everything works as expected (AINs & DINs sending signals and so on...) you'll know for sure if it's the hard- or the software.

2nd question..: does any body have an idea, or a good suggestion for me what to do alternately?

Yes there is:

1. Look to the Wiki. In the part "application development" is a link to a C-Debugger (called AC-Sim) class. If you develop your C-project in an Integrated Development Enviroment (IDE), you can easily attach another target and test your application in a graphical debugger or check MIOS Output from a command-line utility. This is a bit of work in the beginning, but it's worth gold if you struggle with some unknown contents of your variables.

2. Check out MIOSStudio. It has a Debug-Interface, where you can stop the User_Timer and call different MIOS-function (unfortunately just MIOS-handlers, not your own). You can also dump the RAM of the PIC. If you're smart enough (I'm not ;D) you can see the contents of your variables there :)

My frustrations are beginning to grow coz i have a dead line on friday and an even bigger dead line next wednesday so it has to work, very very soon....

MIOS and MBHP are a great platform, but I found it difficult in the past having too less time to experiment and try out things. A Microcontroller sometimes behaves differently than a PC and programming has to be more precise and effective... Take yourself a bit more time with the next project and you'll surely have more fun :)

Best regards,

Michael

EDIT:

some overlaps with stryd_one, but I'm sure, anyone can live with it...

(hey stryd_one... you're the second time faster than me :(

I think I'm going to take a coffe break and wait for you finished your forum walkthrough ;D )

[SynnyS]

So i tried to upload mios again thru mios studio, this is what i get in return :S

these are just the last few lines

Sending block 00007D00-00007DFF

Received error code 01: Less bytes than expected have been received

Received unexpected MIOS SysEx message = 00007E400323F7  expected = 00007E4000

Received error code 03: Checksum mismatch

Sending block 00007E00-00007EFF

Received unexpected MIOS SysEx message = 00007E400300F7  expected = 00007E4000

Received unexpected MIOS SysEx message = 00007E404E6E55035476751A050E567B5A7A345017404E7F614C05037E0D60757F436008712E1C5103427F0E0D1A1D264E295045283A4E6E55035476751A050E567B5A7A345017404E7F614C05037E0D603C5F707603637F07701E0F7F4A1D40073D4268732C120047143C350754300770634538753771570003403D00081C01680021601B3B7E0B5E6671241D77371C5D4107401D580200102E6013617F003F7A7000411003076C0000022000000012000000011000000009000000004800000004400007401D580200102E6013617F003F7A7000412465311B6D7723255C67101329147A4C4020012100283432210B4A20016E433A190645605149342E2568173E5A0E0351F7  expected = 00007E4000

Received unexpected MIOS SysEx message = 000E27413A09093F7557780354523A032C01073A2C2036400A0E7518403D00081D016C6A7A6E17302970024034483820F7  expected = 00007E4000

Received error code 03: Checksum mismatch

Sending block 00007F00-00007FFF

Received unexpected MIOS SysEx message = 00007E400332F7  expected = 00007E4000

Received unexpected MIOS SysEx message = 00007E400310F7  expected = 00007E4000

Received acknowledgement response

Upload process complete

[TK.]

Which file of the update package is uploaded here?

Did you read the comments in README.txt?

Best Regards, Thorsten.

[SynnyS]

this was the main.syx file...

[audiocommander]

every project has a main.syx file.

even your own application has a main.syx file if you didn't change the default name.

So i tried to upload mios again thru mios studio, this is what i get in return :S

mios itself is called "mios_v1_9_pic18f452.hex" or "mios_v1_9_update_without_installed_mios.hex" or ...

so you couldn't have uploaded mios, 'cause it's definitely not called main.syx.

please take a look at http://www.midibox.org/dokuwiki/doku.php?id=application_development to see what is called MIOS and what is called an application ;)

Regards, Michael