Let's find out together what makes a PIC Tick!
Started by normnet, Mar 11, 2021, 11:51 PM
Quote from: LeonJ on Jun 07, 2021, 07:52 AMHi Norm,Will Fineline run on XP as a VM on a Mac Mini under Parallels7 (older version)Leon
Quote from: John Drew on Jun 07, 2021, 09:07 AMVery smooth and fast Norm. The help/fineline manual doesn't come up for me. The other help functions work fine, I especially like the fine lines for If/Endif. My most common error is messing nested If...Endif pairs.The PDF operation is very fast too. Which programming language did you use?Best wishesJohn
Quote from: See_Mos on Jun 07, 2021, 02:36 PMHi Norm, I have been testing your editor and have a couple of problems.With the device name and XTAL in the main code I cannot make it display the SFR's or bitnames. I tried looking in options > Proton IDE to get SFR's as suggested by the popup message box but cannot see anything obvious?When the device name, XTAL (and required registers) are in the .INC file which I use for most of my projects compilation is OK but the editor does not pick up the device name
Quote from: See_Mos on Jun 09, 2021, 10:36 AMSFR's or bit names I found very useful in the original compiler. It save a lot of time searching through the data sheets.clicking on a register in the Code Explorer pane brings up the SFR viewer and then you can paste the bit names directly into the code.
Quote from: normnet on Jun 10, 2021, 03:39 AMLooks cool! I'm not exactly sure how to source all the data. Perhaps its derived from the data sheets?
Quote from: Stephen Moss on Jun 10, 2021, 10:26 AMThe bit names are stored in .BNF files, for Proton they are stored in C:\Program Files (x86)\ProtonIDE\Plugin\CompilerBitnames but there are only 154 so not all devices are covered. For Positron I guess it would be something like C:\Program Files (x86)\Positron\Plugin\CompilerBitnames.There was an application written by Harm DeVeres (not sure about the spelling) that would extract BNF data from device PDF data sheet and I am currently re-writing my own BNF file generator that uses the MPLABX files as a source. The BNF files supplied with the compiler and those generated by Harm' application generally provide a description of each bit name (hover mouse over the bit name in the viewer it to see it). My application will only include bit name (and register) descriptions if Microchip have included it in the source files, so most files will not have that data but if it is only the Bit Names that are of primary interest then it is not an issue. Despite the lack of Bit descriptions my BNF files have other potential advantages...1) Not having to download the datasheet for each device mean it would take about 90 minutes to generate a BNF file for all of the supported devices, less it if does not process device that already have BNF files. So is much faster than downloading and processing the datasheets would be.2) My BNF files have extra data that indicate the number of bits to display in the register rows for the current device (Mechanique IDE only shows 8 regardless of register size) and how many rows to display for the register. Normally that would be 1 for a stand alone register but could be 2 or 3 for joined registers of 16, 24, 32 or 48 bits, i.e. A 16 bit timer value in an 8 bit device uses two registers TMR1L & TMR1H but if a joined equivalent exists can be access as 16 bit register called TMR1, therefore the BNF viewer should show two 8 bit rows for register TMR1 (one row for TMR1L & one for TMR1H) whereas in a 16 bit device it would display one 16 bit row.