Jump to content

Recommended Posts

Posted

I am trying to upload MIOS onto a 18F4620. MIOS Studio receives the upload requests OK.

When I try to upload, I get this :

Starting upload of mios_v1_9f_pic18f4620.hex

Hex file contains code in MIOS range, forcing reboot!

Received Upload Request

Sending block 00000400-000004FF

Received Checksum: 54 - OK

etc....

So it seems to be flashing ok. But when I reboot the PIC, it just goes back to displaying upload requests every few seconds. I've tried uploading an application too, and that didn't make any difference.

What could be wrong? Can the PIC be set to read-only?

Posted

Well, after uploading MIOS you should receive an upload request every 2s - that's normal.

However once you upload an application it should only send the one upload request. Can you please try and upload a test application, and post the *whole* log here and it's results?

Posted

OK, here's the log after trying to upload an application (the revision ID test program : http://www.ucapps.de/mios/revision_id_v1a.zip) :

Starting upload of main.hex

Received Upload Request

Sending block 00003000-000030FF

Received Checksum: 38 - OK

Sending block 00003100-000031FF

Received Checksum: 60 - OK

Sending block 00003200-000032FF

Received Checksum: 40 - OK

Sending block 00003300-000033FF

Received Checksum: 60 - OK

Upload process complete

Then I reboot, and the upload requests just keep coming.

Trying to upload MIOS gives a "Upload process complete" message too.

Posted

In the chat, we worked out that rasteri was using a nonstandard burner to burn the bootloader to his PICs. We suspect the bootloader has not been burned correctly (PIC is mis-configured)

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