Hopefully someone can explain to me the difference with the Search path window on Compiler version 4.0 and version 3.6 Here is version 3.6 one like it has been with all previous versions of the Pascal compiler Search Paths PIC32 Pascal 3.6.jpg Here is the version of the search path window with 4.0 S...

Good point,

I'll hook up my oscilloscope and see what I can determine about stability of oscillator. Will let you know.

Still do not know the cause, but was able to finally get the boot section of the affected chip programmed with the USB HID bootload code. I took a board with a chip that had programmed successfully with the USB HID bootload code and then read the code and bootcode from that chip back to the programm...

Using the programmer to reads the chip after downloading the USB HID bootloader code reveals the problem. The first screen shows the chips boot area with good USB HID bootload code. Good bootload code.jpg The second screen shows the affected chip read after loading the USB HID code to the chip. The ...

I have encountered a strange event 3 times (out of hundreds) when using the USB HID bootloader app. I program the chip using the programmer with the USB HID bootload code. Then I connect a micro b USB plug to the onboard socket and attempt to load the application code. Here is what happened on the 3...

Hi Petar, Yes, heard from Filip who repeated that eret does work. Unfortunately, I can not get the code to resume after the wait command using the eret. The fast blink LED code never appears to be executed as it simply burns stead and even the slow blink never operates again. That indicates to me th...

Hi Petar,

Just realized that when talking about the return I referred to 'erie' as the return cmd when I should have typed 'eret". That embarrassment aside, my code did have it correct as "eret' and that code did not work.

Sorry bout that

Ed

Many thanks, Petar

As I mentioned, it all appears to work except the resumption of code execution after the "Wait" command. Since the IF RCON code in the example is straight forward it would seem the only thing to question is whether the "eret" command works in Pascal.

Ed

Well, some success after many attempts, but not yet what I wanted. This code does reset after WDTO and then using a "goto" label command does jump past the "Wait" command in the code and resumes code execution. The SLOW Blink occurs then the "Wait" command holds the PC until a WDT reset occurs then ...

If I understand the section 9 Watch Dog Timer correctly, it appears there is a way to resume code execution after a "Wait" command if the Osccon is set correctly. This "return" requires code to do a check of RCON to determine whether a WDT interrupt occurred and whether the MCU was in "Sleep" or "Id...

I have a WDT reset procedure that works as advertised. After the WDT timeout interval expires my PIC32MX795F512L chip reboots and starts the entire program over. That much works, my quest is to have the Program Counter jump to an address that is not at restart of the code and run from that point. I ...

Hi qweiczz, I found that my entire problem was not using the latest version of the USB HID bootloader code that came with Mikro Pascal Pro 4.0. Mikro made a change in the source code of the bootloader which makes it work with Windows 10. No change needed in PID or VID or anything else in the code. I...

I agree, in the interim, just glad we have users like you on the list willing to share. Otherwise, I would still be stuck on this problem. Can't tell you how many "fixes" I tried on Windows 10 which did not solve the problem, but then it was a "me" problem in not thinking that a new version of the c...

VCC pointed out to me that is not the Timer delay that is crucial rather its the interval where the need was to reduce the delay from a total of 20msec to just 1 msec as shown in the Compiler version4.0 code. Ok, Thanks VCC Yes, I see where in their latest code Mikro has reduced it from the Two 10ms...

Ok, Thanks VCC Yes, I see where in their latest code Mikro has reduced it from the Two 10msec delays to one 1msec delay. Sorry, my mistake, thought it was the timer delay. end; Delay_1ms(); if timer = 0 then // Do we have a timeout? begin Result := 0; // Yes, return with do application code. Exit; e...