Would you like to react to this message? Create an account in a few clicks or log in to continue.

You are not connected. Please login or register

pic12f675 SDCC debuge

2 posters

Go to page : Previous  1, 2, 3  Next

Go down  Message [Page 2 of 3]

26pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 3:02 pm

MedTronic



arcachofo wrote:
MedTronic wrote:
arcachofo wrote:
MedTronic wrote:here is all ziped files
Attachment failed...

sorry sir
Maybe you are missing one step: https://youtu.be/qPB9ktplj5E?t=56

sorry sir again
here it is
Attachments
pic12f675 SDCC debuge - Page 2 AttachmentBlink.zip
code zip files
You don't have permission to download attachments.
(8 Kb) Downloaded 1 times

27pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 3:32 pm

arcachofo

arcachofo

Thanks.

28pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 4:07 pm

arcachofo

arcachofo

The alternative method using lst file does not work with this lst file.

Problem with gputils could be an error with path separators.
Try with this one and let me know if there is any change:
https://drive.google.com/file/d/1bVKuAm3AxjR_jVbCTQf8i-hvUGSzggHR/view?usp=sharing

29pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 5:05 pm

MedTronic



arcachofo wrote:The alternative method using lst file does not work with this lst file.

Problem with gputils could be an error with path separators.
Try with this one and let me know if there is any change:
https://drive.google.com/file/d/1bVKuAm3AxjR_jVbCTQf8i-hvUGSzggHR/view?usp=sharing

opssss
with your new version there is no hex file

i found the following resulte with debuge button pressed

-------------------------------------------------------
Executing:
"D:/SDCC/bin/sdcc" --use-non-free -mpic14 -p12f675 -o"D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\" "D:\SimulIDE\SimulIDE_1.1.0-SDCC_test\examples\Micro\Pic\MedTronic\C_Codes\SDCC\pic12f675\Blink\Blink.c"

D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.asm:84:Message[1304] Page selection not needed for this device. No code generated.
message: Using default linker script "C:\Program Files\gputils\lkr\12f675_g.lkr".
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation of section "UDL_idata_0" failed, relocating to a shared memory location.
warning: Relocation of section "IDD_idata_0" failed, relocating to a shared memory location.

-------------------------------------------------------
Executing:
"D:/SDCC/bin/sdcc" --use-non-free -mpic14 -p12f675 -o"D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\" "D:\SimulIDE\SimulIDE_1.1.0-SDCC_test\examples\Micro\Pic\MedTronic\C_Codes\SDCC\pic12f675\Blink\Blink.c"

D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.asm:84:Message[1304] Page selection not needed for this device. No code generated.
message: Using default linker script "C:\Program Files\gputils\lkr\12f675_g.lkr".
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation of section "UDL_idata_0" failed, relocating to a shared memory location.
warning: Relocation of section "IDD_idata_0" failed, relocating to a shared memory location.


Error: Hex file doesn't exist:
D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.hex
-------------------------------------------------------

Starting Debbuger...

-------------------------------------------------------
Executing:
"D:/SDCC/bin/sdcc" --use-non-free -mpic14 -p12f675 -o"D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\" "D:\SimulIDE\SimulIDE_1.1.0-SDCC_test\examples\Micro\Pic\MedTronic\C_Codes\SDCC\pic12f675\Blink\Blink.c"

D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.asm:84:Message[1304] Page selection not needed for this device. No code generated.
message: Using default linker script "C:\Program Files\gputils\lkr\12f675_g.lkr".
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation of section "UDL_idata_0" failed, relocating to a shared memory location.
warning: Relocation of section "IDD_idata_0" failed, relocating to a shared memory location.


Error: Hex file doesn't exist:
D:/SimulIDE/SimulIDE_1.1.0-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.hex

Error Starting Debugger

30pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 5:40 pm

arcachofo

arcachofo

I didn't change anything at all about the compiling.
There is something weird here.

Are you sure that the hex file was actually generated before?
or maybe it was an old hex file already existing there?

31pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 6:21 pm

MedTronic




the vedio is clear

32pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 6:28 pm

arcachofo

arcachofo

But in the first example the hex file is already there.
Does it work if you delete all files in folder "build"?

33pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 6:52 pm

MedTronic





the answer is yes the vedio is clear

34pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 7:00 pm

arcachofo

arcachofo

I see...
This is really weird, the command is exactly the same and the output from sdcc is exactly the same...

35pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 7:10 pm

arcachofo

arcachofo

What if you run sdcc with -V ?
Maybe there is some information there.

36pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 7:28 pm

MedTronic



arcachofo wrote:What if you run sdcc with -V ?
Maybe there is some information there.

the new version with -V argument

37pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 7:47 pm

arcachofo

arcachofo

All seems ok, the exact same output.

The only thing I can remotely imagine is that for some reason gplink does not like dots in the path?
That does not make much sense, gpasm is working ok with that path.
But this issue does not make any sense in any case.

38pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 10:51 pm

MedTronic



arcachofo wrote:All seems ok, the exact same output.

The only thing I can remotely imagine is that for some reason gplink does not like dots in the path?
That does not make much sense, gpasm is working ok with that path.
But this issue does not make any sense in any case.

i chang the folder name with the new version and the hex file is generated and the code is run but also i can't debuge the source code step by step the output pannel is
SDCC-PIC Compiler successfully loaded.

-------------------------------------------------------
File: D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/Blink.c

-------------------------------------------------------
-------------------------------------------------------

Starting Debbuger...

-------------------------------------------------------
Executing:
"D:/SDCC/bin/sdcc" --use-non-free -mpic14 -V -p12f675 -o"D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\" "D:\SimulIDE\SimulIDE-SDCC_test\examples\Micro\Pic\MedTronic\C_Codes\SDCC\pic12f675\Blink\Blink.c"

D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.asm:84:Message[1304] Page selection not needed for this device. No code generated.
message: Using default linker script "C:\Program Files\gputils\lkr\12f675_g.lkr".
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation of section "UDL_idata_0" failed, relocating to a shared memory location.
warning: Relocation of section "IDD_idata_0" failed, relocating to a shared memory location.
+ D:\SDCC\bin\sdcpp.exe -nostdinc -Wall -std=c11 -D__SDCC_PROCESSOR="12f675" -D__SDCC_PIC12F675 -D__SDCC_PIC14_STACK_SIZE=14 -obj-ext=.o -D__SDCC_CHAR_UNSIGNED -D__SDCC_USE_NON_FREE -D__SDCCCALL=0 -D__SDCC=4_2_0 -D__SDCC_VERSION_MAJOR=4 -D__SDCC_VERSION_MINOR=2 -D__SDCC_VERSION_PATCH=0 -D__SDCC_REVISION=13081 -D__SDCC_pic14 -D__STDC_NO_COMPLEX__=1 -D__STDC_NO_THREADS__=1 -D__STDC_NO_ATOMICS__=1 -D__STDC_NO_VLA__=1 -D__STDC_ISO_10646__=201409L -D__STDC_UTF_16__=1 -D__STDC_UTF_32__=1 -isystem "D:\SDCC\bin\..\include\pic14" -isystem "D:\SDCC\bin\..\include" -isystem "D:\SDCC\bin\..\non-free\include\pic14" -isystem "D:\SDCC\bin\..\non-free\include" "D:\SimulIDE\SimulIDE-SDCC_test\examples\Micro\Pic\MedTronic\C_Codes\SDCC\pic12f675\Blink\Blink.c"
+ C:\PROGRA~1\gputils\bin\gpasm.exe -o "D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.o" -c "D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink".asm
+ C:\PROGRA~1\gputils\bin\gplink.exe -I"D:\SDCC\bin\..\lib\pic14" -I"D:\SDCC\bin\..\non-free\lib\pic14" -I"D:\SDCC\bin\..\lib\pic14" -I"D:\SDCC\bin\..\non-free\lib\pic14" -w -r -o "D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink" "D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.o" "libsdcc.lib" "pic12f675.lib"


FirmWare Uploaded to p12F675-1(p12F675)
D:/SimulIDE/SimulIDE-SDCC_test/examples/Micro/Pic/MedTronic/C_Codes/SDCC/pic12f675/Blink/build\Blink.hex


Searching for variables... 0 variables found

Mapping Flash to Source... 0 lines mapped

Debugger Started

please help me

best regards
MedTronic

39pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 07, 2023 11:56 pm

arcachofo

arcachofo

i chang the folder name with the new version and the hex file is generated and the code is run
Good to know.

You at least can compile, I can't make SDCC to work in Linux.
SDCC for PICs has been abandoned for years.

And this is a bug in the compiler (never solved as far as I know):
"Page selection not needed for this device. No code generated."
Look here:
https://sourceforge.net/p/sdcc/discussion/1865/thread/aa77f0a86a/


40pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 1:29 am

arcachofo

arcachofo

Try this one:
https://drive.google.com/file/d/1i9CdAXrOxkVRpTcjgx5nayI4Uw3JEzw6/view?usp=sharing

This one uses the lst file instead of gpvc.

41pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 7:30 pm

MedTronic



arcachofo wrote:
i chang the folder name with the new version and the hex file is generated and the code is run
Good to know.

You at least can compile, I can't make SDCC to work in Linux.
SDCC for PICs has been abandoned for years.

And this is a bug in the compiler (never solved as far as I know):
"Page selection not needed for this device. No code generated."
Look here:
https://sourceforge.net/p/sdcc/discussion/1865/thread/aa77f0a86a/




Peace be upon you, my dear friend
I tried several previous versions of your wonderful program and found the version in the following video that succeeded in making the compilation and degube with sdcc for pic.
I think that this will benefit you, because it is the same device with the same version of Windows and the same everything, and success of debuge step by step was achieved.

42pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 7:48 pm

arcachofo

arcachofo

I think that this will benefit you, because it is the same device with the same version of Windows and the same everything, and success of debuge step by step was achieved.
Nice to know.
But that version has other problems, for example: try to compile some file spaces in the path.

The main difference is about how path are processed, I will have a look.

In any case did you try the version linked in the post above?

43pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 8:07 pm

MedTronic



arcachofo wrote:
I think that this will benefit you, because it is the same device with the same version of Windows and the same everything, and success of debuge step by step was achieved.
Nice to know.
But that version has other problems, for example: try to compile some file spaces in the path.

The main difference is about how path are processed, I will have a look.

In any case did you try the version linked in the post above?

I will test know give me only five minute

arcachofo likes this post

44pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 8:24 pm

MedTronic



[quote="MedTronic"]
arcachofo wrote:
I think that this will benefit you, because it is the same device with the same version of Windows and the same everything, and success of debuge step by step was achieved.
Nice to know.
But that version has other problems, for example: try to compile some file spaces in the path.

The main difference is about how path are processed, I will have a look.

In any case did you try the version linked in the post above?

I will test know give me only five minute[/quote





Now is better than befor but please tell me whats worng with pic12f675? and why it is working with pic16f628 only? let's check more

45pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 9:15 pm

arcachofo

arcachofo

Now is better than befor but please tell me whats worng with pic12f675?
You are using the wrong compiler, it must be SDCC-PIC

MedTronic likes this post

46pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 10:14 pm

MedTronic



Thank you very much for your effort and your wonderful effort, and now we have been able to overcome this problem, and with this wonderful cooperation, we can overcome all the problems facing us, God willing.
May God grant you success and thank you very much, my dear friend Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy Very Happy

arcachofo and KerimF like this post

47pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 08, 2023 10:17 pm

arcachofo

arcachofo

Glad to know it is working now and thanks to you for all the testing.

MedTronic likes this post

48pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Mon Nov 13, 2023 9:43 pm

MedTronic



arcachofo wrote:Glad to know it is working now and thanks to you for all the testing.  

Dear my friend the variables not displayed can you please dispaly the variables at the MCU monitor

thanks in advanced

Best Regards

49pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Tue Nov 14, 2023 1:19 pm

arcachofo

arcachofo

You are right, variables are not detected.
I will have a look.

MedTronic likes this post

50pic12f675 SDCC debuge - Page 2 Empty Re: pic12f675 SDCC debuge Wed Nov 22, 2023 6:28 pm

arcachofo

arcachofo

This issue is probably solved at Rev 2055.

Sponsored content



Back to top  Message [Page 2 of 3]

Go to page : Previous  1, 2, 3  Next

Permissions in this forum:
You cannot reply to topics in this forum