Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
See Also
Discussion Groups | LPC2000 | Winarm and sprintf
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
Winarm and sprintf - Taris - Oct 29 16:27:08 2009
I'am new in GCC compilers. How can i use sprintf function with WinArm gcc compiler
(Version 20060606). When i try use the sprintf function , comes next error:
-------- begin --------
arm-elf-gcc (GCC) 4.1.1 (WinARM)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiling: main.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=main.lst -std=gnu99 -MD -MP -MF .dep/main.o.d main.c -o main.o
Compiling: sysTime.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=sysTime.lst -std=gnu99 -MD -MP -MF .dep/sysTime.o.d sysTime.c -o sysTime.o
Compiling: uart.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=uart.lst -std=gnu99 -MD -MP -MF .dep/uart.o.d uart.c -o uart.o
Compiling: uartISR.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=uartISR.lst -std=gnu99 -MD -MP -MF .dep/uartISR.o.d uartISR.c -o uartISR.o
Compiling: armVIC.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=armVIC.lst -std=gnu99 -MD -MP -MF .dep/armVIC.o.d armVIC.c -o armVIC.o
Compiling: lpcWD.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=lpcWD.lst -std=gnu99 -MD -MP -MF .dep/lpcWD.o.d lpcWD.c -o lpcWD.o
Assembling: crt0.S
arm-elf-gcc -c -mcpu=arm7tdmi -I. -x assembler-with-cpp -DROM_RUN -Wa,-adhlns=crt0.lst,-gdwarf-2 crt0.S -o crt0.o
Linking: main.elf
arm-elf-gcc -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=main.o -std=gnu99 -MD -MP -MF .dep/main.elf.d main.o sysTime.o uart.o uartISR.o armVIC.o lpcWD.o crt0.o --output main.elf -nostartfiles -Wl,-Map=main.map,--cref -lc -lm -lc -lgcc -TLPC2103-ROM.ld
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(freer.o): In function `_malloc_trim_r':
mallocr.c:(.text+0x48): undefined reference to `_sbrk_r'
mallocr.c:(.text+0x64): undefined reference to `_sbrk_r'
mallocr.c:(.text+0x84): undefined reference to `_sbrk_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(makebuf.o): In function `__smakebuf':
makebuf.c:(.text+0x3c): undefined reference to `_fstat_r'
makebuf.c:(.text+0x110): undefined reference to `isatty'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(mallocr.o): In function `_malloc_r':
mallocr.c:(.text+0x424): undefined reference to `_sbrk_r'
mallocr.c:(.text+0x4cc): undefined reference to `_sbrk_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__sclose':
stdio.c:(.text+0xc): undefined reference to `_close_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__sseek':
stdio.c:(.text+0x30): undefined reference to `_lseek_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__swrite':
stdio.c:(.text+0x84): undefined reference to `_lseek_r'
stdio.c:(.text+0xac): undefined reference to `_write_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__sread':
stdio.c:(.text+0xd0): undefined reference to `_read_r'
collect2: ld returned 1 exit status
make.exe: *** [main.elf] Error 1
> Process Exit Code: 2
> Time Taken: 00:01
Best regards
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
-------- begin --------
arm-elf-gcc (GCC) 4.1.1 (WinARM)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiling: main.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=main.lst -std=gnu99 -MD -MP -MF .dep/main.o.d main.c -o main.o
Compiling: sysTime.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=sysTime.lst -std=gnu99 -MD -MP -MF .dep/sysTime.o.d sysTime.c -o sysTime.o
Compiling: uart.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=uart.lst -std=gnu99 -MD -MP -MF .dep/uart.o.d uart.c -o uart.o
Compiling: uartISR.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=uartISR.lst -std=gnu99 -MD -MP -MF .dep/uartISR.o.d uartISR.c -o uartISR.o
Compiling: armVIC.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=armVIC.lst -std=gnu99 -MD -MP -MF .dep/armVIC.o.d armVIC.c -o armVIC.o
Compiling: lpcWD.c
arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=lpcWD.lst -std=gnu99 -MD -MP -MF .dep/lpcWD.o.d lpcWD.c -o lpcWD.o
Assembling: crt0.S
arm-elf-gcc -c -mcpu=arm7tdmi -I. -x assembler-with-cpp -DROM_RUN -Wa,-adhlns=crt0.lst,-gdwarf-2 crt0.S -o crt0.o
Linking: main.elf
arm-elf-gcc -mcpu=arm7tdmi -I. -gdwarf-2 -DROM_RUN -Os -Wall -Wstrict-prototypes -Wcast-align -Wcast-qual -Wimplicit -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wstrict-prototypes -Wunused -Wa,-adhlns=main.o -std=gnu99 -MD -MP -MF .dep/main.elf.d main.o sysTime.o uart.o uartISR.o armVIC.o lpcWD.o crt0.o --output main.elf -nostartfiles -Wl,-Map=main.map,--cref -lc -lm -lc -lgcc -TLPC2103-ROM.ld
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(freer.o): In function `_malloc_trim_r':
mallocr.c:(.text+0x48): undefined reference to `_sbrk_r'
mallocr.c:(.text+0x64): undefined reference to `_sbrk_r'
mallocr.c:(.text+0x84): undefined reference to `_sbrk_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(makebuf.o): In function `__smakebuf':
makebuf.c:(.text+0x3c): undefined reference to `_fstat_r'
makebuf.c:(.text+0x110): undefined reference to `isatty'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(mallocr.o): In function `_malloc_r':
mallocr.c:(.text+0x424): undefined reference to `_sbrk_r'
mallocr.c:(.text+0x4cc): undefined reference to `_sbrk_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__sclose':
stdio.c:(.text+0xc): undefined reference to `_close_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__sseek':
stdio.c:(.text+0x30): undefined reference to `_lseek_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__swrite':
stdio.c:(.text+0x84): undefined reference to `_lseek_r'
stdio.c:(.text+0xac): undefined reference to `_write_r'
c:/winarm/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/lib\libc.a(stdio.o): In function `__sread':
stdio.c:(.text+0xd0): undefined reference to `_read_r'
collect2: ld returned 1 exit status
make.exe: *** [main.elf] Error 1
> Process Exit Code: 2
> Time Taken: 00:01
Best regards
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - rtstofer - Oct 29 18:20:10 2009
--- In l...@yahoogroups.com, "Taris"
>
> I'am new in GCC compilers. How can i use sprintf function with WinArm gcc compiler (Version 20060606). When i try use the sprintf function , comes next error:
>
You are required to provide the system level code to implement a number of functions. Heap management is one of them (_sbrk).
I tend to like the code in JCWren's demo program www.jcwren.com/arm. Look in syscalls.c. You don't need to implement all of that code.
Note high tightly _sbrk is tied to symbols defined in the linker script. You may need to modify both.
You can Google around for more info.
Richard
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: Winarm and sprintf - "Felipe de Andrade Neves L." - Oct 29 19:51:37 2009
Newlib is awsome, but it has high costs in code size (reeeealy high), also I
couldn't ger scanf to work.
2009/10/29 rtstofer
> --- In l...@yahoogroups.com, "Taris"
> wrote:
> >
> > I'am new in GCC compilers. How can i use sprintf function with WinArm gcc
> compiler (Version 20060606). When i try use the sprintf function , comes
> next error:
> > You are required to provide the system level code to implement a number of
> functions. Heap management is one of them (_sbrk).
>
> I tend to like the code in JCWren's demo program www.jcwren.com/arm. Look
> in syscalls.c. You don't need to implement all of that code.
>
> Note high tightly _sbrk is tied to symbols defined in the linker script.
> You may need to modify both.
>
> You can Google around for more info.
>
> Richard
>
>
>
[Non-text portions of this message have been removed]
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
couldn't ger scanf to work.
2009/10/29 rtstofer
> --- In l...@yahoogroups.com
>
> >
> > I'am new in GCC compilers. How can i use sprintf function with WinArm gcc
> compiler (Version 20060606). When i try use the sprintf function , comes
> next error:
> > You are required to provide the system level code to implement a number of
> functions. Heap management is one of them (_sbrk).
>
> I tend to like the code in JCWren's demo program www.jcwren.com/arm. Look
> in syscalls.c. You don't need to implement all of that code.
>
> Note high tightly _sbrk is tied to symbols defined in the linker script.
> You may need to modify both.
>
> You can Google around for more info.
>
> Richard
>
>
>
[Non-text portions of this message have been removed]
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - rtstofer - Oct 29 20:41:06 2009
--- In l...@yahoogroups.com, "Felipe de Andrade Neves L."
>
> Newlib is awsome, but it has high costs in code size (reeeealy high), also I
> couldn't ger scanf to work.
There are a lot of folks writing embedded applications who don't use newlib or any other canned library. There could be (probably are) licensing issues with newlib and I believe they have been discussed before. It's wasn't interesting to me because I don't do commercial development. Including printf() is expensive in terms of memory!
It is often easier to just write your own library functions. I tend to use the stuff from "The C Programming Language" by Kernighan/Ritchie and "Software Tools" by Kernighan/Plauger.
I know there are issues with re-entrancy but they only pop up if you have multiple tasks and most of my stuff doesn't use an RTOS.
Richard
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: Winarm and sprintf - "Felipe de Andrade Neves L." - Oct 29 23:38:53 2009
It is true, the better choice is to write a own library.. Someday I will.
2009/10/29 rtstofer
> --- In l...@yahoogroups.com, "Felipe de
> Andrade Neves L." wrote:
> >
> > Newlib is awsome, but it has high costs in code size (reeeealy high),
> also I
> > couldn't ger scanf to work.
> >
> > There are a lot of folks writing embedded applications who don't use newlib
> or any other canned library. There could be (probably are) licensing issues
> with newlib and I believe they have been discussed before. It's wasn't
> interesting to me because I don't do commercial development. Including
> printf() is expensive in terms of memory!
>
> It is often easier to just write your own library functions. I tend to use
> the stuff from "The C Programming Language" by Kernighan/Ritchie and
> "Software Tools" by Kernighan/Plauger.
>
> I know there are issues with re-entrancy but they only pop up if you have
> multiple tasks and most of my stuff doesn't use an RTOS.
>
> Richard
>
>
>
[Non-text portions of this message have been removed]
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
2009/10/29 rtstofer
> --- In l...@yahoogroups.com
> Andrade Neves L."
> >
> > Newlib is awsome, but it has high costs in code size (reeeealy high),
> also I
> > couldn't ger scanf to work.
> >
> > There are a lot of folks writing embedded applications who don't use newlib
> or any other canned library. There could be (probably are) licensing issues
> with newlib and I believe they have been discussed before. It's wasn't
> interesting to me because I don't do commercial development. Including
> printf() is expensive in terms of memory!
>
> It is often easier to just write your own library functions. I tend to use
> the stuff from "The C Programming Language" by Kernighan/Ritchie and
> "Software Tools" by Kernighan/Plauger.
>
> I know there are issues with re-entrancy but they only pop up if you have
> multiple tasks and most of my stuff doesn't use an RTOS.
>
> Richard
>
>
>
[Non-text portions of this message have been removed]
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - cfbsoftware1 - Oct 30 0:03:02 2009
--- In l...@yahoogroups.com, "Felipe de Andrade Neves L." wrote:
>
> It is true, the better choice is to write a own library.. Someday I will.
>
Don't put off until tomorrow what you can do today. The sooner you do it the more time and effort you will save in the long term.
When you do bite the bullet, make sure you avoid using the fragile format string-interpreting schemes as used by printf / fprintf / scanf etc. They are accidents just waiting to happen.
Any minimal time that you might save writing code which uses interfaces like this is quickly used up at testing time - and then some. In the worst case you might find yourself trying to sort out obscure runtime problems of your application's users on the other side or the world).
--
Chris Burrows
Armaide: LPC2xxx Integrated Development System
http://www.cfbsoftware.com/armaide
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
>
> It is true, the better choice is to write a own library.. Someday I will.
>
Don't put off until tomorrow what you can do today. The sooner you do it the more time and effort you will save in the long term.
When you do bite the bullet, make sure you avoid using the fragile format string-interpreting schemes as used by printf / fprintf / scanf etc. They are accidents just waiting to happen.
Any minimal time that you might save writing code which uses interfaces like this is quickly used up at testing time - and then some. In the worst case you might find yourself trying to sort out obscure runtime problems of your application's users on the other side or the world).
--
Chris Burrows
Armaide: LPC2xxx Integrated Development System
http://www.cfbsoftware.com/armaide
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: Winarm and sprintf - Dick Balaska - Oct 30 2:35:30 2009
Am 10/29/2009 8:40 PM, also sprach rtstofer:
> I tend to use the stuff from "The C Programming Language" by Kernighan/Ritchie
It's amazing that a 31 year old IT book is still relevant.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> I tend to use the stuff from "The C Programming Language" by Kernighan/Ritchie
It's amazing that a 31 year old IT book is still relevant.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: Winarm and sprintf - FreeRTOS Info - Oct 30 2:57:53 2009
rtstofer wrote:
>
> --- In l...@yahoogroups.com, "Felipe de Andrade Neves L."
>> Newlib is awsome, but it has high costs in code size (reeeealy high), also I
>> couldn't ger scanf to work.
>>
>> There are a lot of folks writing embedded applications who don't use newlib or any other canned library. There could be (probably are) licensing issues with newlib and I believe they have been discussed before. It's wasn't interesting to me because I don't do commercial development. Including printf() is expensive in terms of memory!
>
> It is often easier to just write your own library functions. I tend to use the stuff from "The C Programming Language" by Kernighan/Ritchie and "Software Tools" by Kernighan/Plauger.
>
> I know there are issues with re-entrancy but they only pop up if you have multiple tasks and most of my stuff doesn't use an RTOS.
>
> Richard
>
Search the files in the FreeRTOS download for a file called
printf-stdarg.c. This has a very light weight version of sprintf in it
(not written by me, but the version in the download has a couple of bugs
fixed). It is limited however, for example it does not manage %f, etc.
Regards,
Richard.
+ http://www.FreeRTOS.org
Designed for Microcontrollers. More than 7000 downloads per month.
+ http://www.SafeRTOS.com
Certified by TÜV as meeting the requirements for safety related systems.
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - Donald H - Oct 31 16:20:21 2009
--- In l...@yahoogroups.com, Dick Balaska
>
> Am 10/29/2009 8:40 PM, also sprach rtstofer:
> > I tend to use the stuff from "The C Programming Language" by Kernighan/Ritchie
> It's amazing that a 31 year old IT book is still relevant.
>
IT Book ???
You have never read have you ??!!!
don
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - rtstofer - Oct 31 16:31:51 2009
--- In l...@yahoogroups.com, "cfbsoftware1"
>
> --- In l...@yahoogroups.com, "Felipe de Andrade Neves L."
> >
> > It is true, the better choice is to write a own library.. Someday I will.
> > Don't put off until tomorrow what you can do today. The sooner you do it the more time and effort you will save in the long term.
>
> When you do bite the bullet, make sure you avoid using the fragile format string-interpreting schemes as used by printf / fprintf / scanf etc. They are accidents just waiting to happen.
>
> Any minimal time that you might save writing code which uses interfaces like this is quickly used up at testing time - and then some. In the worst case you might find yourself trying to sort out obscure runtime problems of your application's users on the other side or the world).
>
> --
> Chris Burrows
> Armaide: LPC2xxx Integrated Development System
> http://www.cfbsoftware.com/armaide
>
I don't want to imply that I have ever rewritten the C library or even a minor portion of it. When I start a project, I get the serial port to work first. Then I write a few put??? functions to output hex bytes, shorts and words. Next I write a putnum routine to output decimal values and add a few string routines.
I avoid sprintf, printf and scanf at every opportunity. I don't always use fopen, fclose, fget and fput either. I just don't want the overhead.
But my projects tend to be pretty simple and don't tend to have a lot of user interaction. Formatted IO is usually a minor portion of the work.
However, as I don't use JTAG, having the various string and put functions simplifies debugging.
Richard
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - cfbsoftware1 - Oct 31 18:33:37 2009
--- In l...@yahoogroups.com, "rtstofer" wrote:
> When I start a project, I get the serial port to work first. Then
> I write a few put??? functions to output hex bytes, shorts and
> words. Next I write a putnum routine to output decimal values and
> add a few string routines.
>
Makes sense. However, a half-decent development system should provide you with a means of doing simple puts like that without incurring the overheads of a general purpose all-singing and dancing IO library.
>
> However, as I don't use JTAG, having the various string and put functions simplifies debugging.
>
Yes indeed. We still haven't yet had to use JTAG or any sort of interactive debugging. Incredibly, that even includes the first time ever that the Oberon compiler was used to generate code for the LPC2xxx! Most of the credit for that has to go to Prof Wirth for his elegant design and (almost) bug-free original code.
--
Chris Burrows
CFB Software
Armaide: LPC2xxx Oberon-07 Development System
http://www.cfbsoftware.com
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> When I start a project, I get the serial port to work first. Then
> I write a few put??? functions to output hex bytes, shorts and
> words. Next I write a putnum routine to output decimal values and
> add a few string routines.
>
Makes sense. However, a half-decent development system should provide you with a means of doing simple puts like that without incurring the overheads of a general purpose all-singing and dancing IO library.
>
> However, as I don't use JTAG, having the various string and put functions simplifies debugging.
>
Yes indeed. We still haven't yet had to use JTAG or any sort of interactive debugging. Incredibly, that even includes the first time ever that the Oberon compiler was used to generate code for the LPC2xxx! Most of the credit for that has to go to Prof Wirth for his elegant design and (almost) bug-free original code.
--
Chris Burrows
CFB Software
Armaide: LPC2xxx Oberon-07 Development System
http://www.cfbsoftware.com
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - rtstofer - Oct 31 19:15:49 2009
> Yes indeed. We still haven't yet had to use JTAG or any sort of interactive debugging. Incredibly, that even includes the first time ever that the Oberon compiler was used to generate code for the LPC2xxx! Most of the credit for that has to go to Prof Wirth for his elegant design and (almost) bug-free original code.
>
I'm a huge fan of Prof Wirth's work. Pascal has always been one of my favorite languages. When I was messing around with 8051 clones, I bought a Pascal compiler for it http://users.iafrica.com/r/ra/rainier/ Very nice!
I haven't been following along with Oberon. Guess I'll have to play catch-up.
Richard
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Oberon / real time applications - cfbsoftware1 - Oct 31 20:41:51 2009
--- In l...@yahoogroups.com, "rtstofer" wrote:
>
> I'm a huge fan of Prof Wirth's work. Pascal has always been one of my favorite languages. When I was messing around with 8051 clones, I bought a Pascal compiler for it http://users.iafrica.com/r/ra/rainier/ Very nice!
>
> I haven't been following along with Oberon. Guess I'll have to play catch-up.
>
Thought I'd better start a new topic - this discussion has strayed away from WinArm and sprintf somewhat ;-)
A quick catch up of what Wirth has been working on most recently is here:
http://www.inf.ethz.ch/personal/wirth/Articles/Oberon.html
The earlier work he did with the model helicopters looked like a whole lot of fun! There are some videos on the net somewhere - if you're interested I'll track them down. In the meantime a presentation I attended at the 2007 Oberon Day in Zurich included some photos of the hardware used and the helicopters (they're not small!). You can download a copy here:
http://www.oberon-industry.ethz.ch/events/oberonday/presentations
Download the 'Oberon-based Autopilots...' pdf.
Now you can use the same compiler technology for LPC2xxx development!
--
Chris Burrows
CFB Software
Armaide: LPC2xxx Oberon-07 Development System
http://www.cfbsoftware.com/armaide
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
>
> I'm a huge fan of Prof Wirth's work. Pascal has always been one of my favorite languages. When I was messing around with 8051 clones, I bought a Pascal compiler for it http://users.iafrica.com/r/ra/rainier/ Very nice!
>
> I haven't been following along with Oberon. Guess I'll have to play catch-up.
>
Thought I'd better start a new topic - this discussion has strayed away from WinArm and sprintf somewhat ;-)
A quick catch up of what Wirth has been working on most recently is here:
http://www.inf.ethz.ch/personal/wirth/Articles/Oberon.html
The earlier work he did with the model helicopters looked like a whole lot of fun! There are some videos on the net somewhere - if you're interested I'll track them down. In the meantime a presentation I attended at the 2007 Oberon Day in Zurich included some photos of the hardware used and the helicopters (they're not small!). You can download a copy here:
http://www.oberon-industry.ethz.ch/events/oberonday/presentations
Download the 'Oberon-based Autopilots...' pdf.
Now you can use the same compiler technology for LPC2xxx development!
--
Chris Burrows
CFB Software
Armaide: LPC2xxx Oberon-07 Development System
http://www.cfbsoftware.com/armaide
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: Winarm and sprintf - Dick Balaska - Nov 1 1:34:08 2009
Am 10/31/2009 4:19 PM, also sprach Donald H:
> --- In l...@yahoogroups.com, Dick Balaska wrote:
>
>> Am 10/29/2009 8:40 PM, also sprach rtstofer:
>>
>>> I tend to use the stuff from "The C Programming Language" by Kernighan/Ritchie
>>>
>> It's amazing that a 31 year old IT book is still relevant.
>>
>>
>
> IT Book ???
>
> You have never read have you ??!!!
>
> don
>
>
Are you saying it's a children's book? 'Once upon a time there was a
friendly pointer. "Hello World", said the pointer. Are there any
functions that want to play with me? The pointer met up with the twins
*a and a[0] ...'
Or perhaps a mystery: 'The pointer dereferenced into the void of the
heap. Unaware that the adjacent byte had been written as an int, the
pointer dutifully returned the data unaware of the stream corruption
that would follow.'
dik
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> --- In l...@yahoogroups.com, Dick Balaska
>
>> Am 10/29/2009 8:40 PM, also sprach rtstofer:
>>
>>> I tend to use the stuff from "The C Programming Language" by Kernighan/Ritchie
>>>
>> It's amazing that a 31 year old IT book is still relevant.
>>
>>
>
> IT Book ???
>
> You have never read have you ??!!!
>
> don
>
>
Are you saying it's a children's book? 'Once upon a time there was a
friendly pointer. "Hello World", said the pointer. Are there any
functions that want to play with me? The pointer met up with the twins
*a and a[0] ...'
Or perhaps a mystery: 'The pointer dereferenced into the void of the
heap. Unaware that the adjacent byte had been written as an int, the
pointer dutifully returned the data unaware of the stream corruption
that would follow.'
dik
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - Donald H - Nov 1 10:47:26 2009
I question how this book is an IT book.
From: http://en.wikipedia.org/wiki/The_C_Programming_Language_%28book%29
"The C Programming Language has often been cited as a model for technical writing, due to the book's clear presentation and concise treatment. In just 228 pages (272 pages in the second edition), the book covers C comprehensively. Examples generally consist of complete programs of the type one is likely to encounter in daily usage of the language, _with an emphasis on system programming_. The technical details of C are balanced by the authors' observations on good programming practice, which are immediately illustrated with concrete, realistic examples. As the authors write in the preface to the second edition:[2]"
(My emphasis added.)
1) This is an embedded systems group.
2) C was created for systems programming, IT applications came years later.
This book is as much an IT book, as it is a "children's book" and "mystery", what are you thinking ??
don
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
From: http://en.wikipedia.org/wiki/The_C_Programming_Language_%28book%29
"The C Programming Language has often been cited as a model for technical writing, due to the book's clear presentation and concise treatment. In just 228 pages (272 pages in the second edition), the book covers C comprehensively. Examples generally consist of complete programs of the type one is likely to encounter in daily usage of the language, _with an emphasis on system programming_. The technical details of C are balanced by the authors' observations on good programming practice, which are immediately illustrated with concrete, realistic examples. As the authors write in the preface to the second edition:[2]"
(My emphasis added.)
1) This is an embedded systems group.
2) C was created for systems programming, IT applications came years later.
This book is as much an IT book, as it is a "children's book" and "mystery", what are you thinking ??
don
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: Winarm and sprintf - k5nwa - Nov 2 9:39:41 2009
At 04:33 PM 10/31/2009, you wrote:
>--- In l...@yahoogroups.com, "rtstofer" wrote:
> >
> >
> > When I start a project, I get the serial port to work first. Then
> > I write a few put??? functions to output hex bytes, shorts and
> > words. Next I write a putnum routine to output decimal values and
> > add a few string routines.
> >Makes sense. However, a half-decent development system should
>provide you with a means of doing simple puts like that without
>incurring the overheads of a general purpose all-singing and dancing
>IO library.
>
> >
> > However, as I don't use JTAG, having the various string and put
> functions simplifies debugging.
> >Yes indeed. We still haven't yet had to use JTAG or any sort of
>interactive debugging. Incredibly, that even includes the first time
>ever that the Oberon compiler was used to generate code for the
>LPC2xxx! Most of the credit for that has to go to Prof Wirth for his
>elegant design and (almost) bug-free original code.
>
>--
>Chris Burrows
>CFB Software
>Armaide: LPC2xxx Oberon-07 Development System
>http://www.cfbsoftware.com
Is there a utility that let's you download the files into the LPCxxxx
and then act as a terminal to receive debugging messages?
Cecil
K5NWA
www.softrockradio.org www.qrpradio.com
"Blessed are the cracked, for they shall let in the light."
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
>--- In l...@yahoogroups.com, "rtstofer"
> >
> >
> > When I start a project, I get the serial port to work first. Then
> > I write a few put??? functions to output hex bytes, shorts and
> > words. Next I write a putnum routine to output decimal values and
> > add a few string routines.
> >Makes sense. However, a half-decent development system should
>provide you with a means of doing simple puts like that without
>incurring the overheads of a general purpose all-singing and dancing
>IO library.
>
> >
> > However, as I don't use JTAG, having the various string and put
> functions simplifies debugging.
> >Yes indeed. We still haven't yet had to use JTAG or any sort of
>interactive debugging. Incredibly, that even includes the first time
>ever that the Oberon compiler was used to generate code for the
>LPC2xxx! Most of the credit for that has to go to Prof Wirth for his
>elegant design and (almost) bug-free original code.
>
>--
>Chris Burrows
>CFB Software
>Armaide: LPC2xxx Oberon-07 Development System
>http://www.cfbsoftware.com
Is there a utility that let's you download the files into the LPCxxxx
and then act as a terminal to receive debugging messages?
Cecil
K5NWA
www.softrockradio.org www.qrpradio.com
"Blessed are the cracked, for they shall let in the light."
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Winarm and sprintf - rtstofer - Nov 2 10:14:42 2009
--- In l...@yahoogroups.com, k5nwa
> Is there a utility that let's you download the files into the LPCxxxx
> and then act as a terminal to receive debugging messages?
>
> Cecil
I usually use lpc21isp for device programming (using Linux) and minicom for terminal IO. As a result, I have to exit minicom before reprogramming.
But that's because I don't read directions! Apparently, lpc21isp has a terminal - see the -term command line option. Duh!
I was playing with FlashMagic on WinXP a couple of days ago. It has a terminal window.
Richard
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: Winarm and sprintf - k5nwa - Nov 2 10:26:14 2009
At 09:14 AM 11/2/2009, you wrote:
>--- In l...@yahoogroups.com, k5nwa wrote:
>
> > Is there a utility that let's you download the files into the LPCxxxx
> > and then act as a terminal to receive debugging messages?
> >
> > Cecil
>
>I usually use lpc21isp for device programming (using Linux) and
>minicom for terminal IO. As a result, I have to exit minicom before
>reprogramming.
>
>But that's because I don't read directions! Apparently, lpc21isp
>has a terminal - see the -term command line option. Duh!
>
>I was playing with FlashMagic on WinXP a couple of days ago. It has
>a terminal window.
>
>Richard
Thanks
Cecil
K5NWA
www.softrockradio.org www.qrpradio.com
"Blessed are the cracked, for they shall let in the light."
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
>--- In l...@yahoogroups.com, k5nwa
>
> > Is there a utility that let's you download the files into the LPCxxxx
> > and then act as a terminal to receive debugging messages?
> >
> > Cecil
>
>I usually use lpc21isp for device programming (using Linux) and
>minicom for terminal IO. As a result, I have to exit minicom before
>reprogramming.
>
>But that's because I don't read directions! Apparently, lpc21isp
>has a terminal - see the -term command line option. Duh!
>
>I was playing with FlashMagic on WinXP a couple of days ago. It has
>a terminal window.
>
>Richard
Thanks
Cecil
K5NWA
www.softrockradio.org www.qrpradio.com
"Blessed are the cracked, for they shall let in the light."
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )