Hi,
it might be too late to the party, but here it is:
https://libstock.mikroe.com/projects/vi ... mqttclient
Please let me know if it is of any use.
Thank you

Fix confirmed.
Thank you

Not sure how/what worked in the past, but now, installing the driver in a 64-bit Windows does not work with the above mentioned steps. It seems that Windows doesn't like modifying the inf file (it displays an error about invalid hash). The board can be installed as a different device though, with th...

Hi mikroe team,
since the upgrade to passport.mikroe.com, the user icons on Libstock are not displayed anymore. The icon can be uploaded successfully to https://passport.mikroe.com/ and it seems it stays there as it should, it's just not displayed on Libstock.

Thank you

Hi mikroe team, as the end of 2023 is not that far, I have a few questions about the support of Pascal compilers in Necto. (similar questions for Basic users) 1. Which of the PIC, dsPIC, PIC32 compilers will be supported this year for Pascal+Necto? 2. Are these compilers the same as PRO compilers, o...

Hi, I made a comparison between openMikroBootloader and HIDBootloader. They both seem to be doing the same thing. See attached screenshots. The only differences are a few addresses, as expected. :| Edit (a bit of progress): what I've failed to notice before, is that the desktop application is sendin...

Hi, I had similar problems with PIC32MX250F128D and PIC32MX270F256D. This happened 10 years ago and a month ago with two different mikroProgs and only with new, unprogrammed devices. It looks like they are blocked somehow (or maybe some protection bits are blocking the programming process). What is ...

I remember having to set UART baud rate to 256000, both on PIC side and on PC side. That was the highest baud rate available on FT232R.

So.. I was a bit wrong about letting the IDE fill in the EBase value. If you set it to 0x9FC00000 in ProjectSettings, the project can be compiled. Also, the calculations from bootloader_core.mpas seem fine. There is one more thing I had to change. It was the code size, from the USER_BOOTLOADER_SIZE ...

I'll kind of give up for now, as I have to work on some other stuff. If you leave this to mikroe and they don't respond next week, you may have to create a new thread, where others don't respond. Otherwise mikroe think(s) the thread is "handled" and won't look at it.

There are many calculations for addresses and sizes, which used to work. I don't know now if they are still valid. For example, in bootloader_user.mpas, there is USER_BOOTLOADER_SIZE in bootloader_common.mpas, there is USER_BOOTLOAD_ADDRESS Usually, the calls to SetOrg (see bootloader_core.mpas) wil...

Same old problem, the definition files contain wrong constants:

in mpas file, you have to set:
in mlk file, you have to set:

the only problem that I have is when bootloader connects to PC, I select hex file and in message box it shows "parsing hex file" and it just stops there... I had some problems with a different (simple) flavour of this parser, when I tried to load a hex file for ARM (see the PIC32MemStatistics tool ...

Hi, probably you've copy-pasted the project and changed the device only. As I can see from project settings, both projects have the EBase address set to 9FC01000. Please create a new (empty) project, from scratch with PIC32MX170F256D and let the IDE set the EBase for you. Copy that value and set it ...

Hi, there is an old project, writtent in FreePascal, maybe it helps: https://forum.mikroe.com/viewtopic.php?f=93&t=54346&p=253932&hilit=openmikrobootloader#p253932 The compiler used back then, was the official FP + Lazarus. FP was at version 2.x.x, which AFAIK, didn't support Unicode, natively. Now,...