Michael Kalus
writes:
> Hi.
>
> Never split a winning team :-)
> Michael
>
No fear, one can't separate a man from his shadow ;-)
Regards, Enoch.
>
> Am 18.05.2014 um 20:38 schrieb Matthias Trute:
>
>> Hi Enoch,
>>
>>> I understand the reason for the change in trunk@1584 macros.asm, that
>>> is
Hi.
Never split a winning team :-)
Michael
Am 18.05.2014 um 20:38 schrieb Matthias Trute:
> Hi Enoch,
>
>> I understand the reason for the change in trunk@1584 macros.asm, that
>> is, to put things "behind the curtains". However, you have created
>> another forward reference warning, an unneces
Hi Enoch,
> I understand the reason for the change in trunk@1584 macros.asm, that
> is, to put things "behind the curtains". However, you have created
> another forward reference warning, an unnecessary annoyance to a
> diligent programmer:
Diligent and annoyed programmer, you are? H
>
Matthias Trute writes:
> Hi Paolo,
>
>> magno gaudio nuntio vobis:
>> Habemus HEX (and epp.hex)!!
>
> Great!
>
>>
>> Now begins the fun.
>
> Absolutly!
>
>>
>> I apologize to have been annoying to someone.
>
> You're welcome.
>
>> The reason why I haven't do it before is that it was written for
Hi Paolo,
> magno gaudio nuntio vobis:
> Habemus HEX (and epp.hex)!!
Great!
>
> Now begins the fun.
Absolutly!
>
> I apologize to have been annoying to someone.
You're welcome.
> The reason why I haven't do it before is that it was written for Linux and I
> thought was harder for me.
> I
Hi Paolo,
On 05/17/2014 04:47 PM, Paolo Garro wrote:
> Hi everybody,
> magno gaudio nuntio vobis:
> Habemus HEX (and epp.hex)!!
Cool!
> Installed version 5.3, I start from the "appl/template" folder and recompile
> it.
> Then, step by step, I changed things. Now it compiles for my atmega16.
I'
Hi everybody,
magno gaudio nuntio vobis:
Habemus HEX (and epp.hex)!!
Now begins the fun.
I apologize to have been annoying to someone.
> You are the one that wants to use some other ordering and run into trouble
> with it.
My ordering is the same as you propose.
> You're very welcome to critiz
Hi Paolo,
> Just a hint:
> new users like me don't know the story of the project nor deeper clues to
> win the game against compiler.
> I just read the official docs, create an environment suitable to use it on
> windows and play.
> The docs are not aligned with the last release.
> >From "amfort
Hi Erich,
I really appreciate your answer.
I did found renamed words but was not sure to make the right thing using
them.
I will check the history and try to learn from there.
Just a hint:
new users like me don't know the story of the project nor deeper clues to
win the game against compiler.
I
Hi Paolo,
On 05/15/2014 11:03 PM, Paolo Garro wrote:
> Hi Erich,
> I disable the dropbox link thinking nobody was interested...
> Here is a new one:
> https://www.dropbox.com/sh/pa3k267ldncxun5/AABZV_7GtfS3GMqsUBKmk5G0a
>
> Thank you for the trace of operations but my procedure already fails at
Hi Erich,
I disable the dropbox link thinking nobody was interested...
Here is a new one:
https://www.dropbox.com/sh/pa3k267ldncxun5/AABZV_7GtfS3GMqsUBKmk5G0a
Thank you for the trace of operations but my procedure already fails at
compile time.
I never get a working pair of hex files!!
Please ha
Hi Paolo,
On 05/14/2014 08:58 PM, Paolo Garro wrote:
> Hi Matthias,
> thank you for the suggestion, I will try your way.
>
>> I would have to spent quite some time to
>> make it working.
>
> No, you only need a working make utility installed.
> I modify the directory structure to allow compiling
Hello Mattias,
Matthias Trute writes:
> Hi Paolo,
>
>> To avoid the redefinition error of USART_B_VALUE and USART_C_VALUE I
>> create a local “drivers” folder with a modified copy of
>> usart_common.asm. Using .set instead of .equ without modifying the
>> original.
>
> Cool. I've never changed th
Paolo
-Messaggio originale-
From: Matthias Trute
Sent: Wednesday, May 14, 2014 7:37 PM
To: amforth-devel@lists.sourceforge.net
Subject: Re: [Amforth] ATmega16 and ATmega128
Hi Paolo,
> I follow the sample on the official doc "amforth.pdf" to compile a system
> for my MCUs but it
Hi Paolo,
> I follow the sample on the official doc "amforth.pdf" to compile a system
> for my MCUs but it doesn't work.
> There is a huge list of missed words.
I'd suggest to start with the new release 5.3 and try to rebuilt
one of the samples from the appl/ directory. If that works, you
cat sta
you give me the files to compile
it?
Have you downloaded the folder from the dropbox link?
Any help would be greatly appreciated.
Paolo
-Messaggio originale-
From: Matthias Trute
Sent: Tuesday, May 13, 2014 9:11 PM
To: amforth-devel@lists.sourceforge.net
Subject: Re: [Amforth] ATmega1
Hi Paolo,
> To avoid the redefinition error of USART_B_VALUE and USART_C_VALUE I
> create a local “drivers” folder with a modified copy of
> usart_common.asm. Using .set instead of .equ without modifying the
> original.
Cool. I've never changed the settings away from 8N1 ;)
Thank you for testing.
Hello,
I have resumed an old project and I would run it in amforth.
I would start with a simple system with a serial terminal but I’m not able to
get rid of compile errors.
To avoid the redefinition error of USART_B_VALUE and USART_C_VALUE I create a
local “drivers” folder with a modified copy o
18 matches
Mail list logo
