Re: [Amforth] My first I2C connection with amForth

[Erich W. <ew....@na...>]

Hello Jan,

you were faster than I could think of your problem.
Yes, /everything/ needs to be initialized on reset.
And yes, very strange things can happen, if you
miss one little thing.

Glad you found it!
Erich

Jan Kromhout writes:

> Hi,
>
> Also find the problem.
> In my program I use buffers: to create an array. Never thought that these will be cleared at a reset, and also the variables
> used in my program .
> After make an init and start this after a reset my application is working as it should.
>
> Cheers,
>
> Jan
>
>
>
>> Op 12 nov. 2018, om 19:30 heeft Jan Kromhout <kro...@ho...> het volgende geschreven:
>> 
>> Hi,
>> 
>> After a few days of trial and error, I finally managed to control the 12c-LCD mine.
>> A stupid interpretation caused the delay, eventually solved.
>> My tests are running well.
>> 
>> But now it comes. When I give a reset of the Arduino and afterwards I want to write a value to the LCD then it simply does not work.
>> After reset I init the I2C again. When I check with $38 i2c.ping? I get back the true (-1) value. The i2c.status is $f8, but I can’f fint the
>> meaning of this value.
>> 
>> When I check the I2C bus with logic analyser no activity.
>> 
>> Only when I re-load the application it does run again.
>> 
>> 
>> Any idea what that could cause?
>> 
>> Cheers,
>> 
>> Jan
>> 
>> 
>> 
>> _______________________________________________
>> Amforth-devel mailing list for http://amforth.sf.net/
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel


-- 
May the Forth be with you ...