I only use trunk lazarus, I cannot tell you if this is also available in
the release versions.
MiR
Am 21.05.14 13:48, schrieb Justin Smyth:
Do I need lazarus 1.2.2 or will latest trunk work ?
I am using this on a vm on my server which is connected to the
microprocessor board. , so it will only be used for this ,, my own dev
machine is on my laptop
-----Original Message-----
From: Michael Ring [mailto:[email protected]]
Sent: Wednesday, 21 May 2014 9:35 PM
To: Lazarus mailing list
Subject: Re: [Lazarus] How to tell debugger what executable to use ?
Project->Compiler Options->other
You can add those settings in Custom options control
Target Os (embedded) and Target CPU family can be set in
Project->Compiler Options->Config and Target
The compiler can be set in
Project->Compiler Options->Compiler Commands, in Compiler Command edit
Project->field
Use the Test button to see if all is complete.
Unfortunaltely the debugger cannot be set on project level, you need to set
it in
Tools->Options->Debugger
and set it back when you want to debug a windows project.
Am 21.05.14 13:12, schrieb Justin Smyth:
I'd like to know more , I am doing the same thing but from windows
for a NXP LPC 1343 board.
I have recently got FPC 2.6.4 svn -27804 running on Lazarus 1.3 win32
i386 Trunk ( SVN 45035 )
I don't see this version having much debugging for embedded arm plus
for my chipset I am missing the -w switch I need to pass to
ppcrossarm.exe ( I have to tell lazarus on win32)
The chipset I am using is - LPC1343FBD48
I have to pass this to fpc / ppcrossarm
-Parm -Tembedded -WpLPC1343FBD48 -Cparmv7m <myprogram.pp>
Do you have any clues on how to set up lazarus to pass in the -w
command to the compiler ?
Kind Regards
Justin
-----Original Message-----
From: Koenraad Lelong [mailto:[email protected]]
Sent: Wednesday, 21 May 2014 8:22 PM
To: Lazarus mailing
Subject: [Lazarus] How to tell debugger what executable to use ?
Hi,
I'm trying to use lazarus as a debugging-frontend for arm-embedded.
I managed to configure lazarus to compile my source into
arm-embedded-code for the STM32F103-processor.
My next step is to configure lazarus to debug the code.
When I do nothing, the debugger complains that project1 does not exist
(used path is OK), which is true because that file really does not
exist and should not exist. It's an *elf-file* (extension : .elf) that
should be used.
If I use gdb-cli I also have to use the elf-file. So how do I tell
lazarus to use that elf-file ?
I configured lazarus to use arm-none-eabi-gdb as debugger, connect to
localhost, port 3333. Which is the port openocd uses to let the
debugger have control.
I'm using lazarus 1.2.2, and fpc svn 27738 as arm-embedded-compiler.
On a linux-machine.
P.S. is there a way to send "monitor" commands to the debugger ? That
way I could program my chip.
Thanks,
Koenraad..
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
