It worked normally in version 5.1.
It will not be compiled after the update to version 6.12.
Attached is a picture of the example file and the compile error window.
Search found 33 matches
- 27 May 2021 08:19
- Forum: mikroC PRO for ARM General
- Topic: Did not compile USB_HOST example
- Replies: 1
- Views: 910
- 06 Jun 2020 01:27
- Forum: Visual TFT General
- Topic: It is not built as Debug type.
- Replies: 3
- Views: 1268
Re: It is not built as Debug type.
The project is attached.
The mikroC 6.2 version does not download the FAT32 library.
I used the library provided by default
The mikroC 6.2 version does not download the FAT32 library.
I used the library provided by default
- 05 Jun 2020 03:09
- Forum: Visual TFT General
- Topic: It is not built as Debug type.
- Replies: 3
- Views: 1268
It is not built as Debug type.
Graphic controller : FT812
MCU : STM407VG
DEBUGER : CODE GRIP
It's good when you use internal memory.
When used as external memory, the "release" type is well generated.
The "debug" type is not created.
I attach a photo and a project.
Please review it.
MCU : STM407VG
DEBUGER : CODE GRIP
It's good when you use internal memory.
When used as external memory, the "release" type is well generated.
The "debug" type is not created.
I attach a photo and a project.
Please review it.
- 05 Mar 2020 09:45
- Forum: CODEGRIP programmer and debugger
- Topic: Compile Error with Change of Build Type
- Replies: 1
- Views: 1885
Compile Error with Change of Build Type
Codegrip debugger is in use.
The release type normally proceeds with the compilation.
However, an error occurs when composing in debug type.
Attach the picture
The release type normally proceeds with the compilation.
However, an error occurs when composing in debug type.
Attach the picture
- 16 Dec 2019 23:25
- Forum: ARM AI Compilers
- Topic: Necto Questions
- Replies: 12
- Views: 4567
Re: Necto Questions
I wonder if FT812 support is also in the plan..
- 16 Dec 2019 00:47
- Forum: CODEGRIP programmer and debugger
- Topic: Unable to debug.
- Replies: 9
- Views: 3135
Re: Unable to debug.
Thank you very much for your support.
Another debugger (ST-LINK) may have the project folder name created in a different language (Korean, Chinese...)
I could download it, but I don't think I can use Codegrip.
Change the folder name to English and work well.
Thank you
Another debugger (ST-LINK) may have the project folder name created in a different language (Korean, Chinese...)
I could download it, but I don't think I can use Codegrip.
Change the folder name to English and work well.
Thank you
- 12 Dec 2019 23:03
- Forum: CODEGRIP programmer and debugger
- Topic: Unable to debug.
- Replies: 9
- Views: 3135
Re: Unable to debug.
I am attaching an error message.
We bought two Codegrip.
Both have been tested, but both have the same symptoms. One debugger went through a firmware update.
The other one didn't firmware update proceed.
We bought two Codegrip.
Both have been tested, but both have the same symptoms. One debugger went through a firmware update.
The other one didn't firmware update proceed.
- 10 Dec 2019 23:17
- Forum: CODEGRIP programmer and debugger
- Topic: Unable to debug.
- Replies: 9
- Views: 3135
Re: Unable to debug.
Compile errors do not occur.
The target board is our product.
The target board is our product.
- 09 Dec 2019 22:53
- Forum: CODEGRIP programmer and debugger
- Topic: Unable to debug.
- Replies: 9
- Views: 3135
Re: Unable to debug.
Attached is the project.
There is no problem using Codegrip.
Thank you for your help.
There is no problem using Codegrip.
Thank you for your help.
- 06 Dec 2019 00:44
- Forum: CODEGRIP programmer and debugger
- Topic: Unable to debug.
- Replies: 9
- Views: 3135
Unable to debug.
Using SWD, the STM32F407 has a well-connected hardware. Operation and connection was checked using the CODEGRIP program. However, it is not programmed in the MIKRO_C compiler. Attached is the Debugger Setup screen. We've tried many ways, but we haven't found an answer. (We did update CODE GRIP)
- 06 Aug 2018 10:59
- Forum: Visual TFT General
- Topic: after update(VTFT,MIKRO C) we don't display external memory
- Replies: 6
- Views: 2162
Re: after update(VTFT,MIKRO C) we don't display external mem
We tried the same thing before, but tried again.(new project build to ver 6.0) But the results are not different. We have recommended 'mikore' products to our customers and they have purchased them. However, due to the same problem, we are no longer able to proceed. Older versions will work normally...
- 06 Aug 2018 09:43
- Forum: mikroC PRO for ARM General
- Topic: err message R6030
- Replies: 3
- Views: 1795
Re: err message R6030
The same symptom appears even if you install again after downloading. Microsoft's answer is reinstall or contact to the program's manufacture. We change the PC and I tried reinstalling several times. There is no problem in win10, but there was a problem in win7. The same contents seem to have been c...
- 03 Aug 2018 02:46
- Forum: Visual TFT General
- Topic: after update(VTFT,MIKRO C) we don't display external memory
- Replies: 6
- Views: 2162
Re: after update(VTFT,MIKRO C) we don't display external mem
We looked at the difference in the project as you requested.
but i did not find difference. Thank you for letting me know what went wrong.
but i did not find difference. Thank you for letting me know what went wrong.
- 03 Aug 2018 01:26
- Forum: mikroC PRO for ARM General
- Topic: err message R6030
- Replies: 3
- Views: 1795
err message R6030
Version 5.1 is no problem.
However, the compiler will not run after the update.
OS is Windows 7 SP1 , And I did try to run the compiler as Admin.
I have deleted the previous version and installed the new version (try to 3 times)
I attach err message img.
waiting to request , thank you
However, the compiler will not run after the update.
OS is Windows 7 SP1 , And I did try to run the compiler as Admin.
I have deleted the previous version and installed the new version (try to 3 times)
I attach err message img.
waiting to request , thank you
- 01 Aug 2018 23:36
- Forum: Visual TFT General
- Topic: after update(VTFT,MIKRO C) we don't display external memory
- Replies: 6
- Views: 2162
Re: after update(VTFT,MIKRO C) we don't display external mem
I would appreciate it if you let me know what is different.
Because the process of upgrading and downgrading the compiler is too complicated, i want more support
and I could not find anything else
Because the process of upgrading and downgrading the compiler is too complicated, i want more support
and I could not find anything else