News:

Let's find out together what makes a PIC Tick!

Main Menu

Compiler says it has finished but NO hex file?

Started by Ecoli-557, Jan 17, 2025, 12:06 AM

Previous topic - Next topic

Ecoli-557

Recently while compiling - with no errors - there does not seem to be a hex file generated.
There are .eer, .lst, .mci, .pbe files.
The .err file says "ETHERNET-1\CODE\A.S 162 : Warning level superseded by command line value. (2)" which I have no idea what that is telling me.
The ""ETHERNET-1\CODE" is directory stuff, no idea on the rest.
Some help or insight here please?

John Drew

#1
I don't think you had a successful compile as there's an assembler error.There is an error in your source somewhere..
Positron produces an ASM file first for the MPLAB assembler to create a HEXfile.
No HEX is produced if a compile/assembler fails.
John

JohnB

Just by way of explanation of the files generated:
.pbe file is the results of an attempted compiler and is the file used by the IDE to display the results.
.lst and .asm files are produced by the compiler prior to assembly.
.mci files carry meta data for each source file.  Items such as last position of cursor, version number etc.
.hex file is the assembled code programmed into the PIC.
JohnB

John Drew

If your code isn't too long you could post it and someone will have a look and spot the error for you. It can be difficult when starting out with a new compiler.

Ecoli-557

Thanks to All who responded on this.  I am learning each day from the group here.
Code is currently 2,081 lines and is too large to share.
I cancelled the editor and went to bed, brought it up this morning and it compiled fine.  Perhaps some resources were in short supply?
I deeply appreciate the info on the files generated and hope I can make better use of them in the future.
For now, everything is fine, just fine.
Thanks and Regards!

Ecoli-557

Well, I still get the error message in the .err file stating "Warning Level superseded by command line value. (2)"
And I cannot compile even after exiting the IDE and getting back in.
What a Warning Level and how can I look to see how to correct it?
-Dazed and Confused.......

trastikata

If it is not a proprietary code, could you archive to a ZIP file the entire folder and post it here?

Ecoli-557

Thank you for your interest Trastikata, but it is for the moment.

John Lawton


Fanie

Quote from: Ecoli-557 on Jan 17, 2025, 02:59 PMI cancelled the editor and went to bed, brought it up this morning and it compiled fine.

I think it's a matter of some people get punished immediately.

John Drew

Ecoli,
As a strategy when I have similar problems I comment out large chunks of code (and if necessary any calls to them).
If a compile is successful you know the problem is in the commented code. If not remove the comment marks and choose another section to comment out etc etc.
This approach works.
John

Ecoli-557

Thanks John, I have used that in the past and it does indeed work.
Seems to be something in the PC that the compiler does not care for; on a different machine it compiles fast and with no errors.
I think it is something in the machine..........

Stephen Moss

Quote from: Ecoli-557 on Jan 21, 2025, 07:40 PMThanks John, I have used that in the past and it does indeed work.
Seems to be something in the PC that the compiler does not care for; on a different machine it compiles fast and with no errors.
I think it is something in the machine..........
If it is a issue just to a specific PC a couple of things you could try are...
Put Positron as an exception on you Antivirus software in case that is causing some kind of problem and
Try uninstalling, then ensure you are using an account will full admin rights and re-install for all users and/or set the Positron.exe file to run as administrator in case it is some weird kind of file permission thing that is not allowing the compiler to write to the relevant folder.

flosigud

When I  had Avast antivirus it interfered often with compilation. The message was just "Compilation errors" and next try was usually successful. I now use Windows Defender which is totally trouble free.

This is different. There is an error message. You will find the this error in the lst file. I have had errors like this number of times and it is always a subtle mistake on my behalf.

Ecoli-557


John Drew

I've just dealt with a friend's laptop.
He had Avast installed. He couldn't send emails with Outlook even though the machine received emails.
Removed Avast and activated Defender. Problem solved.
I wouldn't touch Avast with a barge pole.
John

top204

#16
I have also had problems with Avast, so I got rid of it.

It has a nasty method of deleting new files, regardless if they are valid or not.

At one time, a message could be enabled, so it popped up when a new file was created and asked whether it can scan it or delete it, but with compilers, everytime a compilation takes place, new files are created, so it was popping up messages left right and centre, and removing files for no reason! Also, when altering the compilers, the new files from the C++ compiler were being blocked.

It was also giving false, best guess, signals for virus' in the compilers, and I know for certain they do not have any! Then they update in a few days or weeks and the virus guesses go away, but this causes lots of problems with people actually believing them!

It also has a nasty method, 'and a con', of warning of problems on the machine that are not actually there, but "The Bought Software will Remove Them". What a con, and it is somethng that most, 'so called', free anti-virus programs do. And again, people actually believe the crooks, so buy the dreadful con-artists software!!

I totally agree John. Keep well away from Avast.