Thanks for your response.

I am using mikroC Pro for ARM v.6.2.0-D, and the Mini-M4 module.

However, I think the was happening for ealier versions.

It happens with all the projects where I start with the HID library example, and start off using the .cfg file that comes with that.

I am no MPU expert, but it seems strange to me that the MikroC GUI overwrites my .cfg file in a way that stops the MPU from functioning with HID library. As a work around I set my .cfg file as read only. Strangly, the GUI only complains about this occasionally. However, I would like to understand wh...

That worked, but I wish I understood why, because I am still trying to get my product it work from the original data base.

Can you confirm that all the configuration bits are stored in the .cfg, and there is nothing that can get transfered via the IDE from past projects when I load a new one?
Thanks

Did not seem to help.

I loaded the file ok from project->edit project->load.

Then I did compile and HID bootload

No HID showed up.

Re-loaded the original hex, and it worked.

It has been several years, so I am rusty on the MIni-M4 STM32. After updating the Compiler (old one has problems with update Windows) I can't get compiled hex file to run, even from demo projects. However, the hex files that come with the demo projects work ok. I am including HID_Read_Write_Interrup...

That did not work, but I do have some questions to check my setup is correct. 1. "_I2C_400KHZ" is not found as a macro, so I am using 400000. Is this an error in the library documentation? 2. Currently, I do no setup for the I2C GPIO except for the I2C2_Init_Advanced. Should I be configuring these G...

After using ST/Link to program I notice that I am unable to use the bootloader. I get "USB HID device is not in bootloader mode" from the bootloader tool. I have tried loading and verifying MikroElektronika bootloader project through ST/Link. This worked, but is there a way to use ST/Link without ov...

I get good results with this FPGA I2C on other projects. However, I can re-check.

The problem is that the M4 is just not pulling down the I2C pins. So at this point the FPGA is just not receiving the expected input from the M4.

Have others reported anything like this?

Mini-M4 as stated.

The I2C goes to an FPGA, but I don't think the issue is on that side, because:

[ ] This port is tested with other equipment.
[ ] The problem is during M4 I2C transmit.

I am noticing an occasional intermittent fail in I2C_Write, which is apparently caused by the occasional intermittent fail of I2C2_Start. I2C2_Start is called, but nothing changes on SCL and SDA, and 0 is returned during the fail event. SCL and SDA remain high. This only happens with >100KHz operati...

It's a pain to manually go through the clicks to program over and over again, always with the same files. Why not have command line arguments so this can be one click? Or at least make it compatible with a robot like AutoHotkey so that the buttons can be pressed by a script. Please make the life of ...

Could you add more information on how this works?

I.e. USB_Break interrupts an HID_Write:

[ ] is stopped half way through a transmit?
[ ] what happens to the buffer next time it is called?

Is there a place to get this?

Any pointers to how to remove the bootloader for normal uploading/debug?

Is there a fast way to turn off the bootloader so that in the application the program can run without the bootloader delay?