Search found 24 matches
- 20 Dec 2019 15:03
- Forum: IDE Beta Testing
- Topic: NECTO Studio beta feedback
- Replies: 29
- Views: 9883
Re: NECTO Studio beta feedback
Hi filipe, I am sure, below is the build output from the project I attached (double-checked the .bin file and it is dated correctly after building so everything works good). Note that this is on mikroC Pro version 4.9.1, if that has any significance. I did not have to copy any files or set paths for...
- 18 Dec 2019 11:19
- Forum: IDE Beta Testing
- Topic: NECTO Studio beta feedback
- Replies: 29
- Views: 9883
Re: NECTO Studio beta feedback
Attached zip contains a sample project that fails to build for me. Steps: 1. Opened "USB HID Bootloader.mcpar" project (C:\Users\Public\Documents\Mikroelektronika\mikroC PRO for ARM\Examples\ST\Other\USB HID Bootloader\Projects\STM32F407VG) in mikroC PRO ARM. 2. Cloned by saving project to a differe...
- 16 Dec 2019 12:04
- Forum: IDE Beta Testing
- Topic: NECTO Studio beta feedback
- Replies: 29
- Views: 9883
Re: NECTO Studio beta feedback
Sure, MCUs are STM32 F407VG and F415RG.
- 14 Dec 2019 10:07
- Forum: IDE Beta Testing
- Topic: NECTO Studio beta feedback
- Replies: 29
- Views: 9883
NECTO Studio beta feedback
Hi Mikroe team, Thanks for the NETCO Studio beta, looks like a promising IDE and I particularly like the default dark theme and the more modern look and feel. Here is some, I hope, constructive feedback plus issues that I encountered in my so far brief testing session under Windows 10 (1909). Feedba...
- 20 Dec 2016 18:37
- Forum: Development Boards
- Topic: Mini M4 STM32 crystal?
- Replies: 1
- Views: 1678
Mini M4 STM32 crystal?
Just wondering what the stability specs are for the 16 Mhz crystal on this board?
Thanks.
Thanks.
- 14 Dec 2016 12:54
- Forum: mikroC PRO for ARM General
- Topic: Bootloader size vs filesize
- Replies: 1
- Views: 2299
Bootloader size vs filesize
I'm making a customized bootloader out of the mikro C USB HID bootloader example, among other things to make the F415 (Mini M4) pace at 168 MHz. The bootloader binary is then to be combined with application code programmed using a different development environment and the combo is to be flashed onto...
- 21 Jan 2016 15:25
- Forum: mikroC PRO for ARM General
- Topic: USBDev_CDCSendData() 64 byte limit?
- Replies: 4
- Views: 9181
Re: USBDev_CDCSendData() 64 byte limit?
How is it going with this?
- 18 Jan 2016 15:47
- Forum: mikroC PRO for ARM General
- Topic: USBDev_CDCSendData() 64 byte limit?
- Replies: 4
- Views: 9181
Re: USBDev_CDCSendData() 64 byte limit?
Hi Filip, Project attached. I have modified it minimally for demo purposes. At the top of VCP_Example.c there is a definition CHUNKSIZE and a variable ADD_DELAY. CHUNKSIZE=64 and ADD_DELAY=0 : The long string is not printed in my terminal window CHUNKSIZE=64 and ADD_DELAY=1 : The long string is prin...
- 17 Jan 2016 14:21
- Forum: mikroC PRO for ARM Wish List
- Topic: [WISH]Code editor improvements
- Replies: 1
- Views: 4443
[WISH]Code editor improvements
Apologies if this has been requested before but a quick forum search didn't turn up any hits. When right-clicking on a variable or function call in the code editor, in the pop-up menu; 1. Make a distinction (i.e. add the latter) between "Find declaration" and "Find definition" as these have two diff...
- 17 Jan 2016 13:45
- Forum: mikroC PRO for ARM General
- Topic: UART library problem
- Replies: 0
- Views: 5191
UART library problem
I have a Adafruit Ultimate GPS connected to a Mini M4 STM32, GPS Rx=>pin PC10 (Tx) and GPS Tx=>PC11 (Rx) with common GND. I cannot seem to get any data out of the RX pin using the mikroC 4.7.0 UART library. Below are some of the code I have tried. In these examples Data LED is toggled if any data is...
- 15 Jan 2016 08:43
- Forum: mikroC PRO for ARM General
- Topic: USBDev_CDCSendData() 64 byte limit?
- Replies: 4
- Views: 9181
Re: USBDev_CDCSendData() 64 byte limit?
Anyone at mE who can provide some insight on this?
- 13 Jan 2016 11:02
- Forum: mikroC PRO for ARM General
- Topic: VCP example, Unresolved extern OTG_FS_GRXSTSPR
- Replies: 6
- Views: 3669
Re: VCP example, Unresolved extern OTG_FS_GRXSTSPR
Hi triac, This issue was a confirmed problem in version 4.7.0. As a workaround I was advised via support ticket to add the following to the respective device defs file, e.g. defs\STM32F407VG.c and defs\STM32F415RG.c . This made it compile without errors. sfr far unsigned long volatile OTG_FS_GRXSTSP...
- 12 Jan 2016 14:58
- Forum: mikroC PRO for ARM General
- Topic: System clock confusion
- Replies: 3
- Views: 3269
Re: System clock confusion
Ah, yes that produced a better result, thanks. Slightly related, in the help file there is a reference to unsigned int Get_Fosc_Per_Cyc() as a built in routine but calling this function generates Undeclared identifier... compiler error. Same goes for LoWord() and HiWord() functions. (mC ARM 4.7.0)
- 10 Jan 2016 09:58
- Forum: mikroC PRO for ARM General
- Topic: USBDev_CDCSendData() 64 byte limit?
- Replies: 4
- Views: 9181
USBDev_CDCSendData() 64 byte limit?
I'm trying to understand USBDev_CDCSendData() function because I need to be able to reliably send more than 64 bytes of consecutive data from MCU to PC. By chunking a larger buffer into 64 byte pieces logic tells me this should work. Something, however, smells funny. I'm using the STM32F4 Discovery ...
- 07 Jan 2016 11:32
- Forum: mikroC PRO for ARM General
- Topic: System clock confusion
- Replies: 3
- Views: 3269
System clock confusion
I'm experimenting with my STM32F4 Disco, project settings; STM32F407VG,168MHz, HSI/HSE on, PLLM=8, PLLN=336, PLLP=2, PLLQ=7. This gives me a SYSCLK of 168 MHz in STM32CubeMX. Further settings, Main PLL=HSE Oscillator, System clock switch=PLL, APB1/=4, APB2/=2, MCU clock output 1=PLL, MCU clock outpu...