Here is another AI app “I” created in HTML. This one took a bit more time as I had to look up a lot of data for the AI to pars through. Because the data set is fairly big and I wanted to be able to change it later The zip file has a main index file and several folders that will need to be unzipped in one folder and run localy from your PC.
Ok What this app does, your left panel you will have Config, EEPROM Map, and Pin Conflicts. The Config is a great little tool for setting your micro-controller fuses quickly if you aren’t leaving it up to gcbasic. Simple scroll to your IC or type in the search 16f18857 will bring up that pics configs. Once you set them all you can use the COPY button on the right or save the text out a .gcb file. Next we have one of my favorite ones, EEPROM Maping. I made this because I hate having to remember when programming where I placed certain data, what variables I use and how much EEPROM I have left. Here you can create a variable name, you can have automatic allocation or manual position data, you can mix and match and set what type. Byte, word , long, string. Once again when you are done you can copy the text or save a .gcb file. AVR’s, PIC’s and a few others are included. Everything I could find for gcbasic. The next one is a pin conflict mapper. This one is self explanatory just play with it. This is what I eventually decided to break out into a single app. The PIC18F57Q43 PCB/code Layout app that I’ve posted on the forum. I wanted a better way to lay the chip out for each project that you could copy the idea easily with AI to another chip you want to use. Give it a try and let me know of any bugs so I can keep improving it. Let's keep PIC'n
Could this approach replace PICInfo and AVRInfo? I can share all the data sources for these tools. I want to replace these tools as the licensing for the Dev Tools is very expensive.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Posible, it would be an intresting project to copy with AI . I'd make it a project and then save the data so you can continue to build it out with AI. Much of the data I pulled to make this was out of the gcb chip data, there are other gaps I had to pull in from other places. I've mostly been making little helper apps like this for everything I do. I'm still learning GCB and I've started learing GamBas3 on linux. I've switched over to linux fully and am developing on that platform.
Last edit: Craig Fendley 21 minutes ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here is another AI app “I” created in HTML. This one took a bit more time as I had to look up a lot of data for the AI to pars through. Because the data set is fairly big and I wanted to be able to change it later The zip file has a main index file and several folders that will need to be unzipped in one folder and run localy from your PC.
Ok What this app does, your left panel you will have Config, EEPROM Map, and Pin Conflicts. The Config is a great little tool for setting your micro-controller fuses quickly if you aren’t leaving it up to gcbasic. Simple scroll to your IC or type in the search 16f18857 will bring up that pics configs. Once you set them all you can use the COPY button on the right or save the text out a .gcb file. Next we have one of my favorite ones, EEPROM Maping. I made this because I hate having to remember when programming where I placed certain data, what variables I use and how much EEPROM I have left. Here you can create a variable name, you can have automatic allocation or manual position data, you can mix and match and set what type. Byte, word , long, string. Once again when you are done you can copy the text or save a .gcb file. AVR’s, PIC’s and a few others are included. Everything I could find for gcbasic. The next one is a pin conflict mapper. This one is self explanatory just play with it. This is what I eventually decided to break out into a single app. The PIC18F57Q43 PCB/code Layout app that I’ve posted on the forum. I wanted a better way to lay the chip out for each project that you could copy the idea easily with AI to another chip you want to use. Give it a try and let me know of any bugs so I can keep improving it. Let's keep PIC'n
Interesting.
Could this approach replace PICInfo and AVRInfo? I can share all the data sources for these tools. I want to replace these tools as the licensing for the Dev Tools is very expensive.
Posible, it would be an intresting project to copy with AI . I'd make it a project and then save the data so you can continue to build it out with AI. Much of the data I pulled to make this was out of the gcb chip data, there are other gaps I had to pull in from other places. I've mostly been making little helper apps like this for everything I do. I'm still learning GCB and I've started learing GamBas3 on linux. I've switched over to linux fully and am developing on that platform.
Last edit: Craig Fendley 21 minutes ago