Just out of curiosity, what are you trying to do with the pic32?

On 2011-10-23, at 9:56 AM, Electron <electron2k4@infinito.it> wrote:

>=20
> Hi again,
>=20
> neverminds.. I had a .C and a .S file with the same name (actually v001.C=
 and v001.S), the system was creating two .o files, overwriting the second,=
 causing this fault.
>=20
> MPLAB should warn the user in this case in my opinion..
>=20
> Anyway, it's solved now.
>=20
> Many thanks anyway :D I hope it's useful to somebody else thus I'm report=
ing my experience.
>=20
> Cheers,
> MarI/O
>=20
>=20
>=20
>> Hi,
>> I'm trying to set up a Workspace to do some MPLAB SIM sessions on a=20
>> virtual PIC32 to experiment with this MPU both in asm and C.
>>=20
>> When I have created the Workspace, I did these steps:
>>=20
>> Project Wizard > Next
>> Device PIC32MX460F512L
>> Active Toolsuite: Microchip PIC32 C-Compiler Toolsuite
>> I enabled Store tool locations in Project
>> Next
>> Create New Project File (I specified the path and filename)
>> Then I created and added two blank source files, one .S and the other .C
>> I've put in the .C one this small source:
>>=20
>> ---
>>=20
>> #include <p32xxxx.h>
>>=20
>> int main(void) {
>>  return 0;
>> }
>>=20
>> ---
>>=20
>> If I build as a library then no errors, but if I build as a normal=20
>> target I get:
>>=20
>> ----------------------------------------------------------------------
>> Debug build of project `C:\Coding\PIC32\v001.mcp' started.
>> Language tool versions: pic32-as.exe v1.12, pic32-gcc.exe v1.12,=20
>> pic32-ld.exe v1.12, pic32-ar.exe v1.12
>> Preprocessor symbol `__DEBUG' is defined.
>> Sun Oct 23 15:33:21 2011
>> ----------------------------------------------------------------------
>> Clean: Deleting intermediary and output files.
>> Clean: Deleted file "C:\Coding\PIC32\v001.o".
>> Clean: Done.
>> Executing: "C:\Programmi\MPLab\MPLAB C32 Suite\bin\pic32-gcc.exe"=20
>> -mprocessor=3D32MX460F512L -c -MMD -MF"v001.d" -D__DEBUG "v001.S"=20
>> -o"v001.o" -Wa,--defsym=3D__DEBUG=3D1
>> Executing: "C:\Programmi\MPLab\MPLAB C32 Suite\bin\pic32-gcc.exe"=20
>> -mprocessor=3D32MX460F512L -x c -c "v001.C" -o"v001.o" -MMD -MF"v001.d"=
=20
>> -D__DEBUG -g
>> Executing: "C:\Programmi\MPLab\MPLAB C32 Suite\bin\pic32-gcc.exe"=20
>> -mprocessor=3D32MX460F512L "v001.o" "v001.o" -o"v001.elf"=20
>> -Wl,-L"C:\Programmi\MPLab\MPLAB C32=20
>> Suite\lib",-L"C:\Programmi\MPLab\MPLAB C32=20
>> Suite\pic32mx\lib",--defsym=3D__MPLAB_BUILD=3D1,--defsym=3D__MPLAB_DEBUG=
=3D1,-
>> Map=3D"v001.map"
>> v001.o: In function `main':
>> C:\Coding\PIC32/v001.C:34: multiple definition of `main'
>> v001.o:C:\Coding\PIC32/v001.C:34: first defined here
>> Link step failed.
>> ----------------------------------------------------------------------
>> Debug build of project `C:\Coding\PIC32\v001.mcp' failed.
>> Language tool versions: pic32-as.exe v1.12, pic32-gcc.exe v1.12,=20
>> pic32-ld.exe v1.12, pic32-ar.exe v1.12
>> Preprocessor symbol `__DEBUG' is defined.
>> Sun Oct 23 15:33:22 2011
>> ----------------------------------------------------------------------
>> BUILD FAILED
>>=20
>> Any help please? I want to play with the PIC32 simulator :-)
>>=20
>> I actually have a Starter Kit board too, but I wanna start from=20
>> scratch, and not using that board, but the MPLAB SIM.
>>=20
>> Thanks a lot.
>>=20
>> Cheers,
>> Mario
>=20
> --=20
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.