Hi,
>> \ older mcu's may need
>> [undefined] TCCR0B [if] TCCR0 constant TCCR0B [then]
>> [undefined] TIMSK0 [if] TIMSK constant TIMSK0 [then]
>>
>>
>> That would not even require any external tool at all
>>
>> Volunteers welcome ;) (be aware: its not that easy
>> as its seems to be). I just a
On 10/14/2012 05:01 AM, Matthias Trute wrote:
> Am 13.10.2012 22:51, schrieb Enoch:
>> On 10/13/2012 02:53 PM, Matthias Trute wrote:
>>> Hi,
>>>
We do still have a problem how to deal with hardware idiosyncrasies as
timer0.frt demonstrates. It should not be dealt with through the shell
>>
Am 13.10.2012 22:51, schrieb Enoch:
> On 10/13/2012 02:53 PM, Matthias Trute wrote:
>> Hi,
>>
>>> We do still have a problem how to deal with hardware idiosyncrasies as
>>> timer0.frt demonstrates. It should not be dealt with through the shell
>>> (re my ill thought #py idea).
>>>
>>> The generic f
On 10/13/2012 02:53 PM, Matthias Trute wrote:
> Hi,
>
>> We do still have a problem how to deal with hardware idiosyncrasies as
>> timer0.frt demonstrates. It should not be dealt with through the shell
>> (re my ill thought #py idea).
>>
>> The generic frt code should include some preprocessing in
Hi,
> We do still have a problem how to deal with hardware idiosyncrasies as
> timer0.frt demonstrates. It should not be dealt with through the shell
> (re my ill thought #py idea).
>
> The generic frt code should include some preprocessing instructions to
> produce MCU specific code, m4 perhaps?
On 10/13/2012 11:29 AM, Matthias Trute wrote:
> Hi,
>
>> What is your recommended practice?
>
> Very simple: Use what you like most. All tools
> that I include with amforth are the ones I consider
> useful for others as well. I do not enforce any of
> them.
>
> The shell has a few advantages ove
Hi,
> What is your recommended practice?
Very simple: Use what you like most. All tools
that I include with amforth are the ones I consider
useful for others as well. I do not enforce any of
them.
The shell has a few advantages over a dumb terminal
and I like to use it. YMMV.
Matthias
--
Hi Enoch,
On 10/11/2012 09:03 PM, Enoch wrote:
> This brings me to a more fundamental question which you, as Amforth's
> BDFL, I feel, need to address.
>
> Amforth-shell.py turns the use of frt "&34 constant PORTA" definitions
> in the code unnecessary as the shell script does these substitutions
Hello Matthias,
It was a short Python hacking, it turned out that I did not like it
myself too :-)
#py simply triggers the eval code in the patched amforth-shell.py.
Yes, the code sent to the device is being modified by the shell
according to the python expression that is embedded in the frt code
Enoch,
> Please find attached a patch to Keith's shell script for your
> consideration. I took the lazy approach of using Python's eval() option
> and it was quite easy:
I've difficulties to understand you approach. Do you change
the forth code, that gets sent to the controller with the
condition
Hello again Matthias,
Here's the patch at pastebin: http://pastebin.com/NbfGxU3C
Thanks, Enoch.
On 10/08/2012 01:36 PM, Matthias Trute wrote:
> Hi,
>
>> On the at90can128, for example, one has to introduce "TCCR0 constant
>> TCCR0B" before uploading lib/hardware/time0.frt
>>
>> How about exten
Hi Matthias,
Please find attached a patch to Keith's shell script for your
consideration. I took the lazy approach of using Python's eval() option
and it was quite easy:
Two variables:
avr - device name string
py - a truth value
1st method:
#py= avr=="at90can128"
#py? "% TCCR0 c!" if py
Hi,
> On the at90can128, for example, one has to introduce "TCCR0 constant
> TCCR0B" before uploading lib/hardware/time0.frt
>
> How about extending Keith's fantastic shell with conditional upload
> constructs such as:
>
> #ifdev at90can128
>% TCCR0 c! \ stop timer
> #else
>%
Hi,
On the at90can128, for example, one has to introduce "TCCR0 constant
TCCR0B" before uploading lib/hardware/time0.frt
How about extending Keith's fantastic shell with conditional upload
constructs such as:
#ifdev at90can128
% TCCR0 c! \ stop timer
#else
% TCCR0B c! \ sto
14 matches
Mail list logo
