|
LDmicro Forum - Can someone compile LDmicro and fix a bug? |
|||
|
|
|
(you are viewing a thread; or go back to list of threads)
Can someone compile LDmicro and fix a bug? (by MGP)
The reason is that the program memory of a 16F1512 (2k) and a 16F1516 (8k) are both currently set to 2k, while a 16F1516 has 8k of memory. They are very good and inexpensive controllers that I use regularly. Best regards and thanks.
(no subject) (by Andre)
On Sunday I'll try tinkering with it and see if it works; I'm still learning to understand the code.
https://cq.cx/ladder-forum.pl?...parent=11837&tt=1766058873 In this thread I tried to add the PIC16F630 but no one responded.
(no subject) (by MGP)
Thank you, take your time.
I do have a 16F1516 to test, but I don't have a 16F630 because they look a lot like a 16F628a and don't have an ADC onboard, which makes them less attractive.
(no subject) (by Andre)
Which version are you using?
(no subject) (by MGP)
I'm using the latest version 5.4.1.1 which can be found on Github.
https://github.com/LDmicro/LDmicro
(no subject) (by MGP)
I've also done some searching, and I think these changes should be sufficient.
The screenshot is from mcutable.h and shows the memory capacity of the controllers. It was copied from the 16F1512 to the 16F1516 but wasn't changed to the correct numbers. The numbers in the curly brackets indicate the RAM locations. I can't compile LDmicro; it took me days, but my knowledge isn't extensive enough. If you'd like to try it, I'd do a test. Thanks.
(no subject) (by Andre Luiz (Brazil))
I'm still learning to understand and program
(no subject) (by Andre Luiz (Brazil))
Print
(no subject) (by MGP)
Andre, thank you very much, it works, great job!
LDmicro compiled a program without any problems that couldn't be compiled on a PIC16F1512 due to insufficient memory, but now it does. Perhaps you could rename this version to LDmicroV5.4.1.2 and repost it here, so we can refer to this thread in the future. If I can ever do you a favor in return, please don't hesitate to ask. Thanks again.
(no subject) (by Andre)
I still don't know how to do that, use GitHub, rename it to a new version. If anyone wants the modified files, I can send them one by one. I'll learn this stuff. I'm adding the Microchip microcontrollers I have, like the PIC16F630, PIC16F676, etc. I even looked at LDMicro32, but I couldn't compile it.
(no subject) (by MGP)
I only meant on this forum.
I don't know how to handle GitHub either and you'll probably have to log in with a password we don't have and we haven't heard anything from Ihor N. yet. We only need the .exe file; the code is for specialists ;-) Your version is listed below so you don't have to. You can add other controllers; you only need to post the .exe file with the adjusted numbering and, if necessary, a text file with the changes. Best regards
(no subject) (by Ziggy)
Have You had contact with Ihor lately?
(no subject) (by MGP)
I haven't heard from him since the war in Ukraine, which is very unfortunate for all of us.
I hope he's doing well; he's a very competent person.
(no subject) (by José)
Hello MGP
I have rebuilt ldmicro 5.4.1.1 (english version by default) from sources with VC++. If you are still interested, I can make some modifications... Best regards José
(no subject) (by MGP)
Thanks for the offer, but for now I have no further requests.
I'll keep it in mind if I need you ;-) It's a shame I can't compile LDmicro myself with VC++; I get more than 100 errors, and then VC++ quits automatically. But as long as LDmicro works properly, I'm a happy man. Regards
(no subject) (by José)
That's not so easy...
At first trial I also had a lot of errors ! There are many files, not always well ordered, and compiling in IDE requires some special VC++ options. BR
(no subject) (by Andre Luiz (Brazil))
Regarding the optimization of ldmicro, was there a topic where discussions were held about what was done? I was looking and there are blocks that can be optimized, but I haven't checked in depth if this could break some PICs. For MGP, yesterday I had 165 errors when compiling to exe in Visual Studio, but two errors were responsible for the 165 errors, such as McuAs being listed as McuAS, and addressing in the mcutable file being in the wrong location. As I mentioned, I'm understanding the structure of ldmicro and, as Ihor has put in a lot of work, I've already added 3 PIC microcontrollers that I have, but I haven't been able to test it yet. Now, when I modify it, I will change the version because there is a version.h file.
For JOSE, I couldn't compile your ldmicro32, could you give more tips? The ldmicro is all ready with cmake.
(no subject) (by José)
Hi Andre
Keep in mind that ldmicro has become a very complex software, dealing with many kinds of targets, and you should beware before touching the structure of the code... And adding new targets requires some tests if you want to be efficient. The lesser tests the more bugs... I have tested your new exe file, but I can't run it for lack of a VC DLL (MSVCP140.DLL) what means some things are not linked to the executable ; it usually not occured and may require some linking options ? To compile my ldmicro32, I don't use a make file but work directly into the IDE of VC++, by configuring project properties. Some of the properties I noticed are (in french version of VC++ 2010): Général -> Jeu de caractères = Non défini Linkeur -> Entrée -> dépendances supplémentaires: ajouter user32.lib gdi32.lib comctl32.lib comdlg32.lib advapi32.lib C/C++ -> Préprocesseur -> définitions: ajouter _CRT_SECURE_NO_WARNINGS (désactiver warnings deprecated) et LDLANG_FR (langue FR pour les menus et boites) et NOMINMAX (pour un pb avec std::max) C/C++ -> Entêtes précompilées: sans entêtes précompilées Répertoires VC++ -> Include: ajouter src src/ldlog/include src/common/gsl-lite/include src/common/stringarray src/common/utils Not sure it's exhaustive... José
(no subject) (by José)
To run ldmicro-V5.4.1.2.exe
I had to join Vcruntime140.dll and Msvcp140.dll (versions 2022) to the executable...
(no subject) (by MGP)
Strange, I can do everything I want.
I tested it on my Win7 and Win11 computers. José, perhaps others also having these problems, and perhaps you could recompile this version so it works for you too. Then we'll have a version for everyone. Anyway, thanks for your help. Regards
(no subject) (by Andre Luiz (Brasil))
I have Windows 11 and Visual Studio 2022 with default settings, which must be why, since I don't have any other Windows and I only modified the memory, there wouldn't be a problem. I will run the new versions on a virtual machine.
(no subject) (by José)
Hello
When Visual Studio is installed, it installs redistribuable files under windows, among which these DLLs. That's probably why it works for you, Andre, without pb. Concerning MGP, maybe he has another installed software developped in VS which has installed compatible DLLs. Look at: https://learn.microsoft.com/en...-to-redistribute?view=msvc-170 But that's not a pb for me since, as MGP said, I have rebuilt ldmicro 5.4.1.2 on my system (Old VC++ under Win 10) and it works as usual. I just let know that ordinary users may encounter this pb. I don't know if it can be solved in modern VS by adding linking options. Following the good idea of Andre, I ran both versions in a Virtual Win 7 machine on which I just have a few softs installed not supported under Win 10: - the version compiled with old VC++ works - the version compiled with VS 2022 claims for DLLs and doesn't start I Note that exe size is bigger in the first case Best regards José
(no subject) (by MGP)
José, I'm from Belgium (Brussels for non-Europeans), and I think the Win versions aren't much different from yours.
It's a shame my knowledge doesn't extend far enough to compile LDmicro, but I'm too old to start over.
Post a reply to this comment:
|
|
|