Error : L6002U :could not open file main.o No such file or directory

I want to solve that problem .. Before some time it was working perfectly.. I have made some changes in that & after it is not compiling.. so what is the solution to solve the L6002U error..

What is it with the questions appearing at the moment?

At the risk of sounding impolite, I worry that the future of our occupation might be falling into an abyss.

So you need to start doing some work on it, then!

For a start, have you verified that the file main.o does actually exist?

"I have made some changes"

So if you go back to the previous, unmodified, version - does it work again?

"At the risk of sounding impolite, I worry that the future of our occupation might be falling into an abyss."

The competition doesn't seem too competitive.

So why not work 5 years more at a very lucrative rate before retiring? We might see similar rates as some developers got when returning back to fix Y2K issues in relic systems.

"I have made some changes in that & after it is not compiling.. so what is the solution to solve the L6002U error.."

Just a quick question - are you aware of the difference between "not compiling" and "not linking"?

Sorry for inconenience but I am just asking for help..No intention for rude behaviour.. In my project main.o file is not generating.. it is giving error during linking process.. So I just want to know what is the cause & the possible solution for the problem...

Thanks..

But you aren't asking for help in any way that is meaningful to anyone else.

You ask ""LoRa_Tx_L0\LoRa_Tx_L0.axf: error: L6002U: Could not open file lora_tx_l0\main.o: No such file or directory".

Please help me.. to solve the problem.."

From your question, it's obvious that the linker can't open the file. Which should be obvious to you too.

Based on the large amount of details you have posted, only you can figure out why it can't open the file.

If it isn't there, then the followup questions would be - doesn't it exist at all, or does it exist at some other location. None of us can answer that.

If it doesn't exist, then the followup questions would be:
- isn't the compiler trying to produce the file? Only you have the project file to check.
- is the compiler trying, but failing? Only you have the build log output to check.
- is the compiler managing, but storing at a different location? Only you have the project file and build log output to check.

There is zero indication in your post that you have actually attempted to check why the linker can't open the file.

This forum is not intended to be professional support by Keil support staff. It's intended for information sharing with other end users of Keil tools.

We have no interest in bending our backs backwards to try to draw out information from a person who don't bother to think for 10 seconds "what information would be valuable/required for anyone to be able to help me?".

You really must have already realized that we are not sitting beside you and seeing the same thing you see. All we see is what you post. And you post basically nothing of value since the only valuable information is that the file can't be found which should be just as informative to you.

Your question is: "my car doesn't start - why not?". We don't know if you have put in the ignition key. We don't know if the lights does come on on the dashboard when you turn the ignition key. We don't know if you hear any cranking. We don't know if you have run out of fuel. We don't know if you have just run the car through 1 meter of standing water. So such a question with no other facts would be rather frustrating to try to respond to.

So - never ask questions that is frustrating to even attempt to answer. Always start to think yourself, and then write a meaningful question with meaningful facts supplied. The best thing with spending a bit of time considering what information might be needed when asking the question is that you are likely to be able to actually solve your own problem by just collecting and looking at the available facts you have access to.

"In my project main.o file is not generating.. it is giving error during linking process.. "

The reason why I asked if you understand the difference between compilation and linking is because it's the compiler that will convert main.c or main.cpp into main.o. The linker will run at a later step and try to open main.o and possibly a number of other files when creating the actual binary/executable. This should give a big hint that it isn't enough to see this linker error message and be able to solve the problem. You either asked the linker to link a file that shouldn't have existed in the first place. Or your project build have already failed at an earlier stage - a stage we can't know anything about since you haven't mentioned anything.

In you later post you mention you made changes. You didn't mention what changes. So only you would have the information to consider how these changes would affect the build process. If you made changes to the project itself (such as changing file names/paths/...) or if you made changes to the source code that might have resulted in compilation errors. So it all falls back on you.

Hello Sir,

Sorry for not posting in details of the code. But I tried to find out what is the problem & why compiler is not generating main.o file.. Then after googling some web sources I found that cleaning some errors & warnings in the code may fix the problem. Then I tried that 7 it worked well.. Now code is running perfect..Thanks for your co operation & Guidence..