Hi Jan,
> Chuck,
>
> When I won't to run at a higher baud rate should I compile again?
That would probably be the easiest way.
Technically it is not needed however. The serial
settings come from the VALUE baud (check with e.g.
\ I use 38400 instead of 9600
amforth 4.9 ATmega1284P 16000 kHz
Hello Jan,
On 05/07/2012 04:29 PM, Jan Kromhout wrote:
> When I won't to run at a higher baud rate should I compile again?
Yes, when you want to change the baudrate, you need to edit your
duemilanove.asm file
.equ BAUD = 9600
reassemble amforth and flash it onto the controller again.
Cheers,
Chuck,
When I won't to run at a higher baud rate should I compile again?
Jan
Op 7 mei 2012, om 15:57 heeft Charles Summers het volgende geschreven:
> You did very well in working through the problem. I'm thrilled that you've
> got things running now.
> Don't hesitate to ask me anything you thi
You did very well in working through the problem. I'm thrilled that you've
got things running now.
Don't hesitate to ask me anything you think I might be able to help you
with. I will probably ask you some questions in the near future on running
fig-forth on the microKim ;)
cheers,
-chuck
On Mon,
Hi Chuck
I am glad that the problem is solved.
I am not in real time a programmer but a mechanical engineer who is writing
optimization tools for dispatching powerplants.
But my hobby is electronics, and the arduino.
Cheers,
Jan
Jan kromhout
Sacharovlaan 3
3223HM Hellevoetsluis-NL
Op 7 mei 20
Hi Jan,
Great to hear that you've got amForth running!
I'm a software QA guy in real life, so I'd be very interested in seeing the
steps you took on Windows tat did NOT work and the steps you took on OSX
that DID work. It might save others from a similar fate :)
cheers,
-chuck
On Mon, May 7, 2012
Hello,
Thanks to all people how have response to my questions.
I have now a running system.
Special tanks to Chuck and Paulo.
I have put the hex files and store them into the directory of avrdude under the
arduino.
Flashed to the Arduino under the OSX, and voila a working AMForth.
Try the sam
Thank,
I need only avrdude, because I compile all in avr studio 5 under windows.
So I need only to transfer the hex files etc. with avrdude to my Arduino Uni.
I think that the problems occurs with flossing, because I get a "working" hex
files from a member.
On his arduino it was working.
So I wi
On 2012/05/06, at 21:52, Jan Kromhout wrote:
> Thanks Paulo,
>
> Could sommething going wrong with the burner?
> Can you give me a hint how to do this on the OSX.
> I have not yet the experiance.
>
> Cheers,
>
> Jan kromhout
> Sacharovlaan 3
> 3223HM Hellevoetsluis-NL
>
My preference goes t
Thanks Paulo,
Could sommething going wrong with the burner?
Can you give me a hint how to do this on the OSX.
I have not yet the experiance.
Cheers,
Jan kromhout
Sacharovlaan 3
3223HM Hellevoetsluis-NL
Op 6 mei 2012 om 22:27 heeft Paulo Ferreira het volgende
geschreven:
>
> On 2012/05/06,
On 2012/05/06, at 20:00, Erich Waelde wrote:
> Hello,
>
> On 05/06/2012 08:12 PM, Jan Kromhout wrote:
>>
>> If I understand correctly the best is to buy some bare 328p chips,
>> and flash them without tatching the lock bits.
>
> If fuses and "lock bits" refer to the same thing, then
> no: "bar
Hello,
Again thanks for the response.
Yes I know that the boot loader is removed.
Stil I am try now for about 14 days to get a running AMforth.
These are my settings.
I need the B5 otherwise I get errors. Running XP under Parallels on my IMAC
Lion.
Try also different computers, no good result!
Hello,
On 05/06/2012 08:12 PM, Jan Kromhout wrote:
>
> If I understand correctly the best is to buy some bare 328p chips,
> and flash them without tatching the lock bits.
If fuses and "lock bits" refer to the same thing, then
no: "bare chips" and arduino boards are different things.
I personally
Hi Matthias,
Thanks for the quick response.
If I understand correctly the best is to buy some bare 328p chips, and flash
them without tatching the lock bits
This is perhaps the issue that my Amfort is not won't to run.
Cheers,
Jan
Op 6 mei 2012, om 19:16 heeft Matthias Trute het volgende ges
Hi Jan,
> When I take 2 new 328p with boot on it ( buy it recently from
> original supplier) then when I read the lock byte the should be the
> same? If my working version has an other number, because I did some
> stupid things, I always can set it back to the origional value with
> avrdude?
I've
Hi
When I take 2 new 328p with boot on it ( buy it recently from original
supplier) then when I read the lock byte the should be the same?
If my working version has an other number, because I did some stupid things, I
always can set it back to the origional value with avrdude?
Jan kromhout
Sach
Matthias,
thanks - yes - the bootloader space is used by amforth .. do not ask
me how much time I've spent tackling this, finally I thought my both
chips are dead... :) ... the D9 did the trick..
> foo
123 ok
Thanks,
Pito
- PŮVODNÍ ZPRÁVA -
Od: "Matthias Trute"
Komu: "Everything around a
Hi,
> Hi, after a year I'm trying to run the latest version on atmega32
> (11.0592Meg xtal). Compiling and flashing is ok, I get working
> system with one exception - I cannot add a new word - ie
>> : foo 123 . ;
> ok
>> words
> and it hangs here
Cannot reproduce:
> : foo 123 . ;
ok
> word
I had a similar problem with the uno until I saw I had left the flash
locked after I out on the forth image.
On May 6, 2012 7:51 AM, "pito" wrote:
> Hi, after a year I'm trying to run the latest version on atmega32
> (11.0592Meg xtal). Compiling and flashing is ok, I get working
> system with one
Hi, after a year I'm trying to run the latest version on atmega32
(11.0592Meg xtal). Compiling and flashing is ok, I get working
system with one exception - I cannot add a new word - ie
> : foo 123 . ;
ok
> words
and it hangs here, so I have to reflash eeprom, then I can see words
again (without f
20 matches
Mail list logo
