Hi,

Debugging with mikroProg is supported only in our compilers (mikroC/Basic/Pascal).
However, you should be able to program the hex generated by MCUXPresso or IAR Embedded Workbench using the mikroProg Suite for ARM application.

Kind regards,

Hi, I apologize for the inconvenience. One more thing that you can check (if you have set everything as in the above picture) is whether the mikroProg firmware is up to date: https://download.mikroe.com/documents/programmers-debuggers/mikroprog/pic-dspic-pic32/firmware/mikroprog-firmware-upgrade.pdf...

Hi,

Please refer to the following forum topic:
viewtopic.php?f=88&t=70964

Kind regards,

Hi,

Could you please try with the mikroBootloader tool from the compiler which has automatic MCU selection?

Kind regards,

Hi,

Please check if you have selected mikroSDK 2.0.0 in the first step of profile creation - step: Select SDK:
https://help.mikroe.com/index.htm?context=2720

Kind regards,

Hi,

Thank you for pointing this out. I've reproduced the same issue.
I've already forwarded this to our developers. I hope it will be fixed soon.
I apologize for the inconvenience caused by this.

Kind regards,

Hi,

Thank you for your feedback.
I'll forward this to our developers for consideration.
For now, Necto informs the user about updates for all available components.
I apologize for the inconvenience caused by this.

Kind regards,

Hi Marc, Could you please check the results in the USART Terminal within 5 seconds upon MCU reset? Please configure the USART Terminal as in the screenshot below and send me a screenshot of the terminal window. You should see "gggggggg...." as a response from MCU on the terminal within 5 seconds aft...

Hi,

It is possible with the mikroSDK2.0 library for this click board in Necto Studio.
So, I believe the project you noticed is written in Necto Studio.

The source code of this library is available here:
https://github.com/MikroElektronika/mik ... ter/clicks

Kind regards,

Hi,

Could you zip and attach a minimal project that reproduces this issue?

Kind regards,

Hi,

RA0 (configured as RST in code) is short connected to RE2 (RST pin from mikroBUS2 socket).

Kind regards,

Hi,

I've tested this on EasyPIC v7 as well, please check the picture below: So, I'd suggest you try this using a RiBUS click board.

Kind regards,

Hi,

I believe I've answered you on the helpdesk ticket you opened, so we can continue our conversation there.

Kind regards,

Hi, I suggest you call Ethernet_arpResolve function before calling Ethernet_sendUDP and then call Ethernet_sendUDP only if Ethernet_arpResolve returns != 0. Also, a global library variable Ethernet_userTimerSec is used to keep track of time for all client implementations (ARP, DNS, UDP, and DHCP). I...

Hi,

I just noticed in the picture you attached that the jumpers J14 (RA4, RA5) are not set for I/O but OSC. Please move it to the left position and try again (run the project that I've attached without the modifications).

Kind regards,