Sign in

username:

password:



Not a member?

Search Comp.Arch.Embedded



Search tips

embedded by Keywords

68HC11 | 68HC12 | 8051 | 8052 | ARM | ARM7 | Asic | AT91 | AT91RM9200 | Atmel | AVR | AVRStudio | Bootloader | CFP | CompactFlash | Cygnal | Cypress | Dataflash | DSP | eCos | EEPROM | Embedded Linux | Emulator | Endian | Ethernet | Firewire | FPGA | Freescale | GCC | GNUARM | GSM | H8 | HDLC | I2C | Infineon | Interrupts | Java | JTAG | LCD | LED | LPC2000 | MCU | Microchip | MMC | MPLAB | MSP430 | PC104 | PCB | PCI | PCMCIA | PowerPC | Rabbit | RS232 | RS485 | RTOS | SBC | SDRAM | Sensor | SPI | STK500 | UART | UML | USART | USB | Verilog | VHDL | VxWorks | Xilinx

Ads

Discussion Groups

Discussion Groups | Comp.Arch.Embedded | key steps to get c-file debugging info into AVRStudio 4

There are 13 messages in this thread.

You are currently looking at messages 10 to 13.

Re: key steps to get c-file debugging info into AVRStudio 4 - Richard M. - 02:30 16-03-05

Meindert Sprang wrote:

>"Richard M." <r...@imagecraft.com> wrote in message
>news:1...@corp.supernews.com...
>  
>
>>Not sure what you mean here. We switched to use HTML Webwork help on V7,
>>    
>>
>
>Mmm..... and now it takes 6 seconds on my 2.4GHz machine to show the first
>help page, as opposed to less than 1 second in V6.... But apart from that: a
>great compiler and IDE! :-)
>
>Meindert
>
>  
>
Don't you know we get kickback from Microsoft and Intel!! :-)

Unfortunately, old WinHelp is not "recommended" by Microsoft anymore,  
that plus other reasons (we can now maintain more or less single source 
Help source amongst all the products that we support with some 
"conditional" text) so we have to switch. Framemaker/Webwork combo is 
not ideal, but it does solve some problems. Sorry for the slow down though.

-- 
// richard
http://www.imagecraft.com



Re: key steps to get c-file debugging info into AVRStudio 4 - Meindert Sprang - 03:15 16-03-05

"Richard M." <r...@imagecraft.com> wrote in message
news:1...@corp.supernews.com...
> Don't you know we get kickback from Microsoft and Intel!! :-)

Really? :-))

> Unfortunately, old WinHelp is not "recommended" by Microsoft anymore,
> that plus other reasons (we can now maintain more or less single source
> Help source amongst all the products that we support with some
> "conditional" text) so we have to switch. Framemaker/Webwork combo is
> not ideal, but it does solve some problems. Sorry for the slow down
though.

I see. Well thanks for explaining. I can see the benefits: we also maintain
a single-source codebase for 6 products...

Meindert




Re: key steps to get c-file debugging info into AVRStudio 4 - Carsten - 10:35 16-03-05

On Tue, 15 Mar 2005 18:11:30 -0000, "Joe"
<f...@hotmail-spammers-paradise.com> wrote:

>I would embrace you and give you a guy-to-guy hug if I could but reach out.
>
>That's done it!


>As you said, use: -gdwarf-2
>(elf-dwarf2 wasn't recognised by the compiler)
>

Glad to be able to help out ..

You cound/should actually have gone to the
 www.avfreaks.net in the forum -> AVR GCC section.

The avr-libc maintainer and the WinAVR maintainer is verry active
there.

Btw: There are at least one correction to the "Memory usage script" ,
used by WinAVR to tell about free/used resources on the chip compiled
for.

Regards
Carsten

previous | 1 | 2