Hi, i took the code from slaa208 and made minimal modifications for using an M24C08 but only writing works without problems; reading nearly never works. The reading functions hangs at while ((~I2CIFG) & ARDYIFG); // wait until transmission is finished Changing the pullups (1k, 3k3, 11k) and the clock did not help. Any idea what may be the reason? Regards, Rolf
I2C EEPROM: Write works, Read not
Started by ●July 30, 2005
Reply by ●July 30, 20052005-07-30
Hi Rolf, Was this on a 1610/1611/1612? I guess it would not be on a 169. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and now MAXQ processors > -----Original Message----- > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] > Sent: 30 July 2005 09:57 > To: msp430@msp4... > Subject: [msp430] I2C EEPROM: Write works, Read not > > > Hi, > > i took the code from slaa208 and made minimal modifications > for using an > M24C08 but only writing works without problems; reading > nearly never works. > > The reading functions hangs at > > while ((~I2CIFG) & ARDYIFG); // wait until transmission is finished > > Changing the pullups (1k, 3k3, 11k) and the clock did not help. > Any idea what may be the reason? > > Regards, > > Rolf > > > > ------------------------ Yahoo! Groups Sponsor > --------------------~--> <font face=arial size=-1><a > href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=> 1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org > ">Get Bzzzy! (real tools to help you find a job) Welcome to > the Sweet Life - brought to you by One Economy</a>.</font> > -------------------------- > ------~-> > > . > > > Yahoo! Groups Links > > > > > > > >
Reply by ●July 30, 20052005-07-30
I've found that only the 169 works well with I2C. Two identical boards, one with a 169, the other with a 1611, do not exhibit the same I2C behavior when driven by the hardware I2C. Bit-bashed, they both work. I haven't tried a 168 though. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, AVR and now MAXQ processors > -----Original Message----- > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] > Sent: 30 July 2005 14:30 > To: msp430@msp4... > Subject: RE: [msp430] I2C EEPROM: Write works, Read not > > > Hi, > > the original code was for an 169. I'm using an 168 which only > has 12 kiB less flash but the same peripherals. > Other things like the UART1 do work without problems. > > Regards, > > Rolf > > > msp430@msp4... schrieb am 30.07.05 15:41:23: > > > > Hi Rolf, > > > > Was this on a 1610/1611/1612? I guess it would not be on a 169. > > > > -- > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > CrossWorks > > for MSP430, ARM, AVR and now MAXQ processors > > > > > -----Original Message----- > > > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] > > > Sent: 30 July 2005 09:57 > > > To: msp430@msp4... > > > Subject: [msp430] I2C EEPROM: Write works, Read not > > > > > > > > > Hi, > > > > > > i took the code from slaa208 and made minimal modifications for > > > using an > > > M24C08 but only writing works without problems; reading > nearly never > > > works. > > > > > > The reading functions hangs at > > > > > > while ((~I2CIFG) & ARDYIFG); // wait until transmission > is finished > > > > > > Changing the pullups (1k, 3k3, 11k) and the clock did not help. > > > Any idea what may be the reason? > > > > > > Regards, > > > > > > Rolf > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > > > --------------------~--> <font face=arial size=-1><a > > > href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7 > > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=> > > 1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org > > > ">Get Bzzzy! (real tools to help you find a job) Welcome to the > > > Sweet Life - brought to you by One Economy</a>.</font> > > > -------------------------- > > > ------~-> > > > > > > . > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > --------------------~--> <font face=arial size=-1><a > href="http://us.ard.yahoo.com/SIGh2bmj4g/M62131.6882499.7 > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP22741004 > /A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org > ">Get Bzzzy! (real tools to help you find a job) Welcome to > the Sweet Life - brought to you by One Economy</a>.</font> > -------------------------- > ------~-> > > . > > > Yahoo! Groups Links > > > > > > > >
Reply by ●July 30, 20052005-07-30
Hi,
the original code was for an 169. I'm using an 168 which only has 12 kiB
less flash but the same peripherals.
Other things like the UART1 do work without problems.
Regards,
Rolf
msp430@msp4... schrieb am 30.07.05 15:41:23:
>
> Hi Rolf,
>
> Was this on a 1610/1611/1612? I guess it would not be on a 169.
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks for MSP430, ARM, AVR and now MAXQ processors
>
> > -----Original Message-----
> > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...]
> > Sent: 30 July 2005 09:57
> > To: msp430@msp4...
> > Subject: [msp430] I2C EEPROM: Write works, Read not
> >
> >
> > Hi,
> >
> > i took the code from slaa208 and made minimal modifications
> > for using an
> > M24C08 but only writing works without problems; reading
> > nearly never works.
> >
> > The reading functions hangs at
> >
> > while ((~I2CIFG) & ARDYIFG); // wait until transmission is
finished
> >
> > Changing the pullups (1k, 3k3, 11k) and the clock did not help.
> > Any idea what may be the reason?
> >
> > Regards,
> >
> > Rolf
> >
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> > --------------------~--> <font face=arial size=-1><a
> > href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7
> 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=>
> 1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org
> > ">Get Bzzzy! (real tools to help you find a job) Welcome to
> > the Sweet Life - brought to you by One Economy</a>.</font>
> > --------------------------
> > ------~->
> >
> > .
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> .
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
Reply by ●July 30, 20052005-07-30
Hi,
i flashed the same file on an 169 and the hangup is gone for minute.
During this minute i could write and read bytes like 0x12 without problems
but after that minute the bug is back!
Than i flashed another new 169 but the problem is reproducible.
Any ideas?
Regards,
Rolf
msp430@msp4... schrieb am 30.07.05 16:32:16:
>
> I've found that only the 169 works well with I2C. Two identical
boards,
> one with a 169, the other with a 1611, do not exhibit the same I2C
> behavior when driven by the hardware I2C. Bit-bashed, they both work.
> I haven't tried a 168 though.
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks for MSP430, ARM, AVR and now MAXQ processors
>
> > -----Original Message-----
> > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...]
> > Sent: 30 July 2005 14:30
> > To: msp430@msp4...
> > Subject: RE: [msp430] I2C EEPROM: Write works, Read not
> >
> >
> > Hi,
> >
> > the original code was for an 169. I'm using an 168 which only
> > has 12 kiB less flash but the same peripherals.
> > Other things like the UART1 do work without problems.
> >
> > Regards,
> >
> > Rolf
> >
> >
> > msp430@msp4... schrieb am 30.07.05 15:41:23:
> > >
> > > Hi Rolf,
> > >
> > > Was this on a 1610/1611/1612? I guess it would not be on a 169.
> > >
> > > --
> > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> > CrossWorks
> > > for MSP430, ARM, AVR and now MAXQ processors
> > >
> > > > -----Original Message-----
> > > > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...]
> > > > Sent: 30 July 2005 09:57
> > > > To: msp430@msp4...
> > > > Subject: [msp430] I2C EEPROM: Write works, Read not
> > > >
> > > >
> > > > Hi,
> > > >
> > > > i took the code from slaa208 and made minimal modifications
for
> > > > using an
> > > > M24C08 but only writing works without problems; reading
> > nearly never
> > > > works.
> > > >
> > > > The reading functions hangs at
> > > >
> > > > while ((~I2CIFG) & ARDYIFG); // wait until transmission
> > is finished
> > > >
> > > > Changing the pullups (1k, 3k3, 11k) and the clock did not
help.
> > > > Any idea what may be the reason?
> > > >
> > > > Regards,
> > > >
> > > > Rolf
> > > >
> > > >
> > > >
> > > > ------------------------ Yahoo! Groups Sponsor
> > > > --------------------~--> <font face=arial
size=-1><a
> > > >
href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7
> > > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=>
> > > 1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org
> > > > ">Get Bzzzy! (real tools to help you find a job)
Welcome to the
> > > > Sweet Life - brought to you by One
Economy</a>.</font>
> > > > --------------------------
> > > > ------~->
> > > >
> > > > .
> > > >
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > .
> > >
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> > --------------------~--> <font face=arial size=-1><a
> > href="http://us.ard.yahoo.com/SIGh2bmj4g/M62131.6882499.7
> > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP22741004
> > /A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org
> > ">Get Bzzzy! (real tools to help you find a job) Welcome to
> > the Sweet Life - brought to you by One Economy</a>.</font>
> > --------------------------
> > ------~->
> >
> > .
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> .
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
Reply by ●July 31, 20052005-07-31
I'd get a digital osciloscope on hands (with some memory or a Logic
Analyser
with over 32MHz driven clock to have enough time resolution) to capture a
whole communication and check what is wrong. If it is a hardware issue
(according Paul's observations) this is the only way to understand it and
be
able to create a workaround.
Unless, of course, someone else had the same problem and has the solution...
but since no one is posting that I believe you will need to handle it
yourself.
If it turns to be a hardware problem I will rise my "TI BUG ALERT" to
orange
or, maybe, red...8-)
-Augusto
-----Original Message-----
From: msp430@msp4... [mailto:msp430@msp4...] On Behalf Of
rolf.freitag@rolf...
Sent: Saturday, July 30, 2005 3:39 PM
To: msp430@msp4...
Subject: RE: [msp430] I2C EEPROM: Write works, Read not
Hi,
i flashed the same file on an 169 and the hangup is gone for minute. During
this minute i could write and read bytes like 0x12 without problems but
after that minute the bug is back! Than i flashed another new 169 but the
problem is reproducible.
Any ideas?
Regards,
Rolf
msp430@msp4... schrieb am 30.07.05 16:32:16:
>
> I've found that only the 169 works well with I2C. Two identical
> boards, one with a 169, the other with a 1611, do not exhibit the same
> I2C behavior when driven by the hardware I2C. Bit-bashed, they both
> work. I haven't tried a 168 though.
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks
> for MSP430, ARM, AVR and now MAXQ processors
>
> > -----Original Message-----
> > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...]
> > Sent: 30 July 2005 14:30
> > To: msp430@msp4...
> > Subject: RE: [msp430] I2C EEPROM: Write works, Read not
> >
> >
> > Hi,
> >
> > the original code was for an 169. I'm using an 168 which only
> > has 12 kiB less flash but the same peripherals.
> > Other things like the UART1 do work without problems.
> >
> > Regards,
> >
> > Rolf
> >
> >
> > msp430@msp4... schrieb am 30.07.05 15:41:23:
> > >
> > > Hi Rolf,
> > >
> > > Was this on a 1610/1611/1612? I guess it would not be on a 169.
> > >
> > > --
> > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> > CrossWorks
> > > for MSP430, ARM, AVR and now MAXQ processors
> > >
> > > > -----Original Message-----
> > > > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...]
> > > > Sent: 30 July 2005 09:57
> > > > To: msp430@msp4...
> > > > Subject: [msp430] I2C EEPROM: Write works, Read not
> > > >
> > > >
> > > > Hi,
> > > >
> > > > i took the code from slaa208 and made minimal modifications
for
> > > > using an
> > > > M24C08 but only writing works without problems; reading
> > nearly never
> > > > works.
> > > >
> > > > The reading functions hangs at
> > > >
> > > > while ((~I2CIFG) & ARDYIFG); // wait until transmission
> > is finished
> > > >
> > > > Changing the pullups (1k, 3k3, 11k) and the clock did not
help.
> > > > Any idea what may be the reason?
> > > >
> > > > Regards,
> > > >
> > > > Rolf
> > > >
> > > >
> > > >
> > > > ------------------------ Yahoo! Groups Sponsor
> > > > --------------------~--> <font face=arial
size=-1><a
> > > >
href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7
> > > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=>
> > > 1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org
> > > > ">Get Bzzzy! (real tools to help you find a job)
Welcome to the
> > > > Sweet Life - brought to you by One
Economy</a>.</font>
> > > > --------------------------
> > > > ------~->
> > > >
> > > > .
> > > >
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > .
> > >
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> > --------------------~--> <font face=arial size=-1><a
> > href="http://us.ard.yahoo.com/SIGh2bmj4g/M62131.6882499.7
> > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP22741004
> > /A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org
> > ">Get Bzzzy! (real tools to help you find a job) Welcome to
> > the Sweet Life - brought to you by One Economy</a>.</font>
> > --------------------------
> > ------~->
> >
> > .
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> .
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
.
Yahoo! Groups Links
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.6/59 - Release Date: 27/7/2005
Reply by ●July 31, 20052005-07-31
Hi, > I'd get a digital osciloscope on hands (with some memory or a Logic Analyser > with over 32MHz driven clock to have enough time resolution) to capture a > whole communication and check what is wrong. ok, i'll check it when i have an oscilloscope. But i tested again this morning, after > 5 h power down (with 90 Ohm between Vcc and ground) and immediately after power on the bug is reproducible: In the first minute reading and writing works but after one minute only writing works. Pressing the reset button does not help and 10 minute or less power down does not help! It must be a hardware bug which is only reset by a long time power down. And the bug must be in the MSP because i can see the first bug free minute when i change the MSP within the first 10 minutes of power-down, where a simple power down does not reset the bug in a board with with an unchanged MSP. I tested with F168 and two F169, both revision B. Now i made up my mind and decided to use an MMC/SDC because they have dozens of more MB which can also be used for data logging and i also have done an MMC/SDC driver which is well tested with two dozen of different cards. Regards, Rolf > Unless, of course, someone else had the same problem and has the solution... > but since no one is posting that I believe you will need to handle it > yourself. > > If it turns to be a hardware problem I will rise my "TI BUG ALERT" to orange > or, maybe, red...8-) > > -Augusto > > > -----Original Message----- > From: msp430@msp4... [mailto:msp430@msp4...] On Behalf Of > rolf.freitag@rolf... > Sent: Saturday, July 30, 2005 3:39 PM > To: msp430@msp4... > Subject: RE: [msp430] I2C EEPROM: Write works, Read not > > > > Hi, > > i flashed the same file on an 169 and the hangup is gone for minute. During > this minute i could write and read bytes like 0x12 without problems but > after that minute the bug is back! Than i flashed another new 169 but the > problem is reproducible. > > Any ideas? > > Regards, > > Rolf > > > msp430@msp4... schrieb am 30.07.05 16:32:16: > > > > I've found that only the 169 works well with I2C. Two identical > > boards, one with a 169, the other with a 1611, do not exhibit the same > > I2C behavior when driven by the hardware I2C. Bit-bashed, they both > > work. I haven't tried a 168 though. > > > > -- > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks > > for MSP430, ARM, AVR and now MAXQ processors > > > > > -----Original Message----- > > > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] > > > Sent: 30 July 2005 14:30 > > > To: msp430@msp4... > > > Subject: RE: [msp430] I2C EEPROM: Write works, Read not > > > > > > > > > Hi, > > > > > > the original code was for an 169. I'm using an 168 which only > > > has 12 kiB less flash but the same peripherals. > > > Other things like the UART1 do work without problems. > > > > > > Regards, > > > > > > Rolf > > > > > > > > > msp430@msp4... schrieb am 30.07.05 15:41:23: > > > > > > > > Hi Rolf, > > > > > > > > Was this on a 1610/1611/1612? I guess it would not be on a 169. > > > > > > > > -- > > > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > > > CrossWorks > > > > for MSP430, ARM, AVR and now MAXQ processors > > > > > > > > > -----Original Message----- > > > > > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] > > > > > Sent: 30 July 2005 09:57 > > > > > To: msp430@msp4... > > > > > Subject: [msp430] I2C EEPROM: Write works, Read not > > > > > > > > > > > > > > > Hi, > > > > > > > > > > i took the code from slaa208 and made minimal modifications for > > > > > using an > > > > > M24C08 but only writing works without problems; reading > > > nearly never > > > > > works. > > > > > > > > > > The reading functions hangs at > > > > > > > > > > while ((~I2CIFG) & ARDYIFG); // wait until transmission > > > is finished > > > > > > > > > > Changing the pullups (1k, 3k3, 11k) and the clock did not help. > > > > > Any idea what may be the reason? > > > > > > > > > > Regards, > > > > > > > > > > Rolf > > > > > > > > > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > > > > > --------------------~--> <font face=arial size=-1><a > > > > > href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7 > > > > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=> > > > > 1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org > > > > > ">Get Bzzzy! (real tools to help you find a job) Welcome to the > > > > > Sweet Life - brought to you by One Economy</a>.</font> > > > > > -------------------------- > > > > > ------~-> > > > > > > > > > > . > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > > > --------------------~--> <font face=arial size=-1><a > > > href="http://us.ard.yahoo.com/SIGh2bmj4g/M62131.6882499.7 > > > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP22741004 > > > /A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org > > > ">Get Bzzzy! (real tools to help you find a job) Welcome to > > > the Sweet Life - brought to you by One Economy</a>.</font> > > > -------------------------- > > > ------~-> > > > > > > . > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > . > > > Yahoo! Groups Links > > > > > > > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.338 / Virus Database: 267.9.6/59 - Release Date: 27/7/2005 > > > > > > . > > > Yahoo! Groups Links > > > > > > >
Reply by ●July 31, 20052005-07-31
Ralf, Please check with the European Product Information Centre of TI I heard from a similar issue and they solved it.. or had a work around... Tel. +49 (8161) 80 3311 or epic@epic... .... ask for the MSP430 specialist... Cheers, Ferry -----Original Message----- From: msp430@msp4... [mailto:msp430@msp4...] On Behalf Of rolf.freitag@rolf... Sent: Sunday, July 31, 2005 05:36 PM To: msp430@msp4... Subject: RE: [msp430] I2C EEPROM: Write works, Read not Hi, > I'd get a digital osciloscope on hands (with some memory or a Logic Analyser > with over 32MHz driven clock to have enough time resolution) to capture a > whole communication and check what is wrong. ok, i'll check it when i have an oscilloscope. But i tested again this morning, after > 5 h power down (with 90 Ohm between Vcc and ground) and immediately after power on the bug is reproducible: In the first minute reading and writing works but after one minute only writing works. Pressing the reset button does not help and 10 minute or less power down does not help! It must be a hardware bug which is only reset by a long time power down. And the bug must be in the MSP because i can see the first bug free minute when i change the MSP within the first 10 minutes of power-down, where a simple power down does not reset the bug in a board with with an unchanged MSP. I tested with F168 and two F169, both revision B. Now i made up my mind and decided to use an MMC/SDC because they have dozens of more MB which can also be used for data logging and i also have done an MMC/SDC driver which is well tested with two dozen of different cards. Regards, Rolf > Unless, of course, someone else had the same problem and has the solution... > but since no one is posting that I believe you will need to handle it > yourself. > > If it turns to be a hardware problem I will rise my "TI BUG ALERT" to orange > or, maybe, red...8-) > > -Augusto > > > -----Original Message----- > From: msp430@msp4... [mailto:msp430@msp4...] On Behalf Of > rolf.freitag@rolf... > Sent: Saturday, July 30, 2005 3:39 PM > To: msp430@msp4... > Subject: RE: [msp430] I2C EEPROM: Write works, Read not > > > > Hi, > > i flashed the same file on an 169 and the hangup is gone for minute. During > this minute i could write and read bytes like 0x12 without problems but > after that minute the bug is back! Than i flashed another new 169 but the > problem is reproducible. > > Any ideas? > > Regards, > > Rolf > > > msp430@msp4... schrieb am 30.07.05 16:32:16: > > > > I've found that only the 169 works well with I2C. Two identical > > boards, one with a 169, the other with a 1611, do not exhibit the same > > I2C behavior when driven by the hardware I2C. Bit-bashed, they both > > work. I haven't tried a 168 though. > > > > -- > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks > > for MSP430, ARM, AVR and now MAXQ processors > > > > > -----Original Message----- > > > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] > > > Sent: 30 July 2005 14:30 > > > To: msp430@msp4... > > > Subject: RE: [msp430] I2C EEPROM: Write works, Read not > > > > > > > > > Hi, > > > > > > the original code was for an 169. I'm using an 168 which only > > > has 12 kiB less flash but the same peripherals. > > > Other things like the UART1 do work without problems. > > > > > > Regards, > > > > > > Rolf > > > > > > > > > msp430@msp4... schrieb am 30.07.05 15:41:23: > > > > > > > > Hi Rolf, > > > > > > > > Was this on a 1610/1611/1612? I guess it would not be on a 169. > > > > > > > > -- > > > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk > > > CrossWorks > > > > for MSP430, ARM, AVR and now MAXQ processors > > > > > > > > > -----Original Message----- > > > > > From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] > > > > > Sent: 30 July 2005 09:57 > > > > > To: msp430@msp4... > > > > > Subject: [msp430] I2C EEPROM: Write works, Read not > > > > > > > > > > > > > > > Hi, > > > > > > > > > > i took the code from slaa208 and made minimal modifications for > > > > > using an > > > > > M24C08 but only writing works without problems; reading > > > nearly never > > > > > works. > > > > > > > > > > The reading functions hangs at > > > > > > > > > > while ((~I2CIFG) & ARDYIFG); // wait until transmission > > > is finished > > > > > > > > > > Changing the pullups (1k, 3k3, 11k) and the clock did not help. > > > > > Any idea what may be the reason? > > > > > > > > > > Regards, > > > > > > > > > > Rolf > > > > > > > > > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > > > > > --------------------~--> <font face=arial size=-1><a > > > > > href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7 > > > > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=> > > > > 1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org > > > > > ">Get Bzzzy! (real tools to help you find a job) Welcome to the > > > > > Sweet Life - brought to you by One Economy</a>.</font> > > > > > -------------------------- > > > > > ------~-> > > > > > > > > > > . > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > > > --------------------~--> <font face=arial size=-1><a > > > href="http://us.ard.yahoo.com/SIGh2bmj4g/M62131.6882499.7 > > > 825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP22741004 > > > /A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org > > > ">Get Bzzzy! (real tools to help you find a job) Welcome to > > > the Sweet Life - brought to you by One Economy</a>.</font> > > > -------------------------- > > > ------~-> > > > > > > . > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > . > > > Yahoo! Groups Links > > > > > > > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.338 / Virus Database: 267.9.6/59 - Release Date: 27/7/2005 > > > > > > . > > > Yahoo! Groups Links > > > > > > > . Yahoo! Groups Links
Reply by ●July 31, 20052005-07-31
rolf.freitag@rolf... wrote: >Hi, > > > >>I'd get a digital osciloscope on hands (with some memory or a Logic Analyser >>with over 32MHz driven clock to have enough time resolution) to capture a >>whole communication and check what is wrong. >> >> > >ok, i'll check it when i have an oscilloscope. >But i tested again this morning, after > 5 h power down (with 90 Ohm between Vcc >and ground) and immediately after power on the bug is reproducible: In the first >minute reading and writing works but after one minute only writing works. >Pressing the reset button does not help and 10 minute or less power down does not help! > >It must be a hardware bug which is only reset by a long time power down. >And the bug must be in the MSP because i can see the first bug free minute when i >change the MSP within the first 10 minutes of power-down, where a simple power >down does not reset the bug in a board with with an unchanged MSP. >I tested with F168 and two F169, both revision B. > I'm sorry to butt in, but you cannot simply jump to these conclusions. there is no sound basis for them. To me the repetitiveness of the time frame suggest that it is more an accumulating bug that is trashing the stack, or that at this point in time you encounter a value that causes corruption. It definitely cannot simply be dismissed as hardware, without some preknown cause or condition, such as a bug report on the IIC or similar known defect.. It is far less likely that hardware will have failures that repeat so accurately time wise. Too mnay things are variable in the hardware between seemingly apparent similar runs, especially as it repeats with different parts. Time related errors like this are nearly always software related since this is the only thing which alwasy does exactly the same thing exactly the same way each time it runs. Al > >Now i made up my mind and decided to use an MMC/SDC because they have dozens >of more MB which can also be used for data logging and i also have done an MMC/SDC >driver which is well tested with two dozen of different cards. > >Regards, > >Rolf > > > > >>Unless, of course, someone else had the same problem and has the solution... >>but since no one is posting that I believe you will need to handle it >>yourself. >> >>If it turns to be a hardware problem I will rise my "TI BUG ALERT" to orange >>or, maybe, red...8-) >> >>-Augusto >> >> >>-----Original Message----- >>From: msp430@msp4... [mailto:msp430@msp4...] On Behalf Of >>rolf.freitag@rolf... >>Sent: Saturday, July 30, 2005 3:39 PM >>To: msp430@msp4... >>Subject: RE: [msp430] I2C EEPROM: Write works, Read not >> >> >> >>Hi, >> >>i flashed the same file on an 169 and the hangup is gone for minute. During >>this minute i could write and read bytes like 0x12 without problems but >>after that minute the bug is back! Than i flashed another new 169 but the >>problem is reproducible. >> >>Any ideas? >> >>Regards, >> >>Rolf >> >> >>msp430@msp4... schrieb am 30.07.05 16:32:16: >> >> >>>I've found that only the 169 works well with I2C. Two identical >>>boards, one with a 169, the other with a 1611, do not exhibit the same >>>I2C behavior when driven by the hardware I2C. Bit-bashed, they both >>>work. I haven't tried a 168 though. >>> >>>-- >>>Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks >>>for MSP430, ARM, AVR and now MAXQ processors >>> >>> >>> >>>>-----Original Message----- >>>>From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] >>>>Sent: 30 July 2005 14:30 >>>>To: msp430@msp4... >>>>Subject: RE: [msp430] I2C EEPROM: Write works, Read not >>>> >>>> >>>>Hi, >>>> >>>>the original code was for an 169. I'm using an 168 which only >>>>has 12 kiB less flash but the same peripherals. >>>>Other things like the UART1 do work without problems. >>>> >>>>Regards, >>>> >>>>Rolf >>>> >>>> >>>>msp430@msp4... schrieb am 30.07.05 15:41:23: >>>> >>>> >>>>>Hi Rolf, >>>>> >>>>>Was this on a 1610/1611/1612? I guess it would not be on a 169. >>>>> >>>>>-- >>>>>Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk >>>>> >>>>> >>>>CrossWorks >>>> >>>> >>>>>for MSP430, ARM, AVR and now MAXQ processors >>>>> >>>>> >>>>> >>>>>>-----Original Message----- >>>>>>From: rolf.freitag@rolf... [mailto:rolf.freitag@rolf...] >>>>>>Sent: 30 July 2005 09:57 >>>>>>To: msp430@msp4... >>>>>>Subject: [msp430] I2C EEPROM: Write works, Read not >>>>>> >>>>>> >>>>>>Hi, >>>>>> >>>>>>i took the code from slaa208 and made minimal modifications for >>>>>>using an >>>>>>M24C08 but only writing works without problems; reading >>>>>> >>>>>> >>>>nearly never >>>> >>>> >>>>>>works. >>>>>> >>>>>>The reading functions hangs at >>>>>> >>>>>>while ((~I2CIFG) & ARDYIFG); // wait until transmission >>>>>> >>>>>> >>>>is finished >>>> >>>> >>>>>>Changing the pullups (1k, 3k3, 11k) and the clock did not help. >>>>>>Any idea what may be the reason? >>>>>> >>>>>>Regards, >>>>>> >>>>>>Rolf >>>>>> >>>>>> >>>>>> >>>>>>------------------------ Yahoo! Groups Sponsor >>>>>>--------------------~--> <font face=arial size=-1><a >>>>>>href="http://us.ard.yahoo.com/SIGh7q6pqc/M62131.6882499.7 >>>>>> >>>>>> >>>>>825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP=> >>>>>1122724605/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org >>>>> >>>>> >>>>>>">Get Bzzzy! (real tools to help you find a job) Welcome to the >>>>>>Sweet Life - brought to you by One Economy</a>.</font> >>>>>>-------------------------- >>>>>>------~-> >>>>>> >>>>>>. >>>>>> >>>>>> >>>>>>Yahoo! Groups Links >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>>. >>>>> >>>>> >>>>>Yahoo! Groups Links >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>>------------------------ Yahoo! Groups Sponsor >>>>--------------------~--> <font face=arial size=-1><a >>>>href="http://us.ard.yahoo.com/SIGh2bmj4g/M62131.6882499.7 >>>>825260.1510227/D=groups/S05005378:TM/Y=YAHOO/EXP22741004 >>>>/A(89191/R=0/SIGr90krvo/*http://www.thebeehive.org >>>>">Get Bzzzy! (real tools to help you find a job) Welcome to >>>>the Sweet Life - brought to you by One Economy</a>.</font> >>>>-------------------------- >>>>------~-> >>>> >>>>. >>>> >>>> >>>>Yahoo! Groups Links >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>>. >>> >>> >>>Yahoo! Groups Links >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >>. >> >> >>Yahoo! Groups Links >> >> >> >> >> >> >> >> >>-- >>No virus found in this outgoing message. >>Checked by AVG Anti-Virus. >>Version: 7.0.338 / Virus Database: 267.9.6/59 - Release Date: 27/7/2005 >> >> >> >> >> >>. >> >> >>Yahoo! Groups Links >> >> >> >> >> >> >> >> >> > > > > > >. > > >Yahoo! Groups Links > > > > > > > > > >
Reply by ●July 31, 20052005-07-31
Hi,
> Time related errors like
> this are nearly always software related since this is the only thing
> which alwasy does exactly the same thing exactly the same way each time
> it runs.
it's not uptime related because a reset does not help; it's supply
voltage time related.
After 10 minutes power down it does not work but after 5 hours power down it
works
(for one minute).
And i'm using a stack checking function which shows that there is no stack
overflow.
Regards,
Rolf
