NECTO Studio beta feedback
Re: NECTO Studio beta feedback
Hi,
Yes, please send me the project.
Regards,
Filip.
Yes, please send me the project.
Regards,
Filip.
Re: NECTO Studio beta feedback
Hi.filip wrote:Hi,
The legacy library pack from the mikroC PRO for ARM is included in the installation, so all libraries are present in the NECTO.
When I press "Shift+Ctrl+L" I got empty library manager, so I do not see any lib and can not add any lib to the project
Issue exist on two diff. computers(Windows 7 x64)
Legacy libs folder C:\NectoStudio\NectoStudio\compilers\ARM\mikroC\libs\legacy has only empty readme.txt file
So, maybe something wrong or I am fully idiot
Best Wishes.
Re: NECTO Studio beta feedback
Find legacy libs in the ...\AppData\Local\Mikroe\NectoStudio\libs\mikroC legacy STM\Data\STM\
But why I do not see any lib in the Library manager?
But why I do not see any lib in the Library manager?
Re: NECTO Studio beta feedback
Hi,
Can you please attach the screenshot of the library manager after you create a new project ?
Regards,
Filip.
Can you please attach the screenshot of the library manager after you create a new project ?
Regards,
Filip.
Re: NECTO Studio beta feedback
Hello Filip.
Here few steps what I did:
New project -> Designer-> TFT Board 5 -> Template with generic board with STM32F401RC.
Here few steps what I did:
New project -> Designer-> TFT Board 5 -> Template with generic board with STM32F401RC.
- Attachments
-
- TFT_test.PNG (80.67 KiB) Viewed 5322 times
Re: NECTO Studio beta feedback
Hi,
Designer-type projects are dependent of the mikroSDK 2.0. If you choose Generic board in the Profile Template, it will not include
the mikroSDK, resulting in the situation that you have (the project cannot be compiled as the compiler expects mikroSDK to be included).
Currently in the Beta, you can use use the Fusion v8 template board and adjust it in the code for your own needs. We plan to make this customizable so you can adjust the board more easily.
Regards,
Filip.
Designer-type projects are dependent of the mikroSDK 2.0. If you choose Generic board in the Profile Template, it will not include
the mikroSDK, resulting in the situation that you have (the project cannot be compiled as the compiler expects mikroSDK to be included).
Currently in the Beta, you can use use the Fusion v8 template board and adjust it in the code for your own needs. We plan to make this customizable so you can adjust the board more easily.
Regards,
Filip.
Re: NECTO Studio beta feedback
Hi.
Sorry, with Fusion v8 template board also doesn't works
I mast to import my old project with FT812 chip TFT(have sent my project to you).
I understand for now, new compiler is not include many features.
I am asking to add custom TFTs as was in previous version.
Sorry, with Fusion v8 template board also doesn't works
I mast to import my old project with FT812 chip TFT(have sent my project to you).
I understand for now, new compiler is not include many features.
I am asking to add custom TFTs as was in previous version.
- Attachments
-
- TFT_test_2.PNG (327.88 KiB) Viewed 5297 times
Re: NECTO Studio beta feedback
Hi Filip.
Do U have any news about how to import my old project to the new NECTO Studio?
Best Wishes.
Do U have any news about how to import my old project to the new NECTO Studio?
Best Wishes.
Re: NECTO Studio beta feedback
Hi,
We will support the FT8xx controllers in some of the next updates of the NECTO Studio, I will have more precise information soon.
In general, the new Visual TFT AI will have different code generation than the old Visual TFT, the code and file structure will be changed so converting old Visual TFT projects may be not be so straightforward.
Regards,
Filip.
We will support the FT8xx controllers in some of the next updates of the NECTO Studio, I will have more precise information soon.
In general, the new Visual TFT AI will have different code generation than the old Visual TFT, the code and file structure will be changed so converting old Visual TFT projects may be not be so straightforward.
Regards,
Filip.
Re: NECTO Studio beta feedback
Nice.
Help assistant do not show info about troubles while import old projects.
Again , I am purchased thing that doesn't works
This project do not so important and I can waiting, I hope you are will find solution soon.
I do not have license for old compiler and have did my project on friend computer, but my friend now is far away.
Best Wishes.
Help assistant do not show info about troubles while import old projects.
Again , I am purchased thing that doesn't works
This project do not so important and I can waiting, I hope you are will find solution soon.
I do not have license for old compiler and have did my project on friend computer, but my friend now is far away.
Best Wishes.
-
- Posts: 1
- Joined: 07 May 2020 06:09
Re: NECTO Studio beta feedback
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 different folder outside Mikroelektronika example folder.
3. Build in mikroC -> OK. Close project.
4. Import to NECTO -> OK.
5. Clean project -> Build project -> fails on linking:
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 different folder outside Mikroelektronika example folder.
3. Build in mikroC -> OK. Close project.
4. Import to NECTO -> OK.
5. Clean project -> Build project -> fails on linking:
- filip.grujcic
- Posts: 822
- Joined: 14 May 2018 08:34
Re: NECTO Studio beta feedback
Hello,
Could you post a screenshot of the error that you are getting in NECTO when trying to compile this project?
Regards,
Could you post a screenshot of the error that you are getting in NECTO when trying to compile this project?
Regards,
Filip Grujcic
-
- Posts: 2
- Joined: 09 Mar 2024 13:18
Re: NECTO Studio beta feedback
I've been dealing with this frustrating issue where pressing "Shift+Ctrl+L" brings up an empty library manager in NectoStudio. It's happening on both of my computers running Windows 7 x64, and I can't seem to figure out why. I've checked the legacy libs folder, but it only contains a readme.txt file.
Is anyone else experiencing this problem? I'd really appreciate any advice or insights you can offer. I'm feeling a bit lost trying to troubleshoot this on my own. Thanks a bunch, vidmate.
Is anyone else experiencing this problem? I'd really appreciate any advice or insights you can offer. I'm feeling a bit lost trying to troubleshoot this on my own. Thanks a bunch, vidmate.
- IvanJeremic
- mikroElektronika team
- Posts: 316
- Joined: 05 Sep 2022 14:32
Re: NECTO Studio beta feedback
Hi,
The new version of Necto won't run correctly on OS below Windows 10.
Try using Necto on a newer OS.
Regards,
Ivan.
The new version of Necto won't run correctly on OS below Windows 10.
Try using Necto on a newer OS.
Regards,
Ivan.