• AVR Freaks

Helpful ReplyHot!new i2c errata in dsPIC33CK256

Page: 123 > Showing page 1 of 3
Author
picy2620
Super Member
  • Total Posts : 136
  • Reward points : 0
  • Joined: 2009/11/13 08:12:47
  • Location: Germany
  • Status: offline
2019/12/20 07:20:20 (permalink)
0

new i2c errata in dsPIC33CK256

Hi all,
 
FYI: just noticed that the i2c-module in the dsPIC33CK256 has an new published errata:
 
29. Module: I2C
All instances of I2C/SMBus may exhibit errors and
should not be used.
Work around
If I2C is required in the application, use a software
I2C implementation. An example I2C software
library is available from Microchip:
www.microchip.com/dsPIC33C_I2C_SoftwareLibrary
 
Does anyone expirienced issue with the i2c module? I use it since serveral months without any Problems.
#1
du00000001
Just Some Member
  • Total Posts : 3795
  • Reward points : 0
  • Joined: 2016/05/03 13:52:42
  • Location: Germany
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2019/12/20 07:44:41 (permalink)
5 (1)
If there's not (yet) more information, risk an eye on the CH's errata. I suppose these 2 families are close enough to share the peripheral errors.
Having done so: basically the I2Cs seem to be operational. It's just the "special cases" where errors arise.
 
Beyond that, we might have to wait for the next errata update.

PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
#2
picy2620
Super Member
  • Total Posts : 136
  • Reward points : 0
  • Joined: 2009/11/13 08:12:47
  • Location: Germany
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2019/12/20 07:56:11 (permalink)
0
But the  four (4) erratas of the CH Chips are already mentioned in the dsPIC33CK errata. So I think this is a different issue.
#3
Shuaah
Starting Member
  • Total Posts : 11
  • Reward points : 0
  • Joined: 2018/11/16 06:07:14
  • Location: 0
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2019/12/20 08:46:53 (permalink)
0
Has anyone been able to actually download the library? Both of the download links just take me to the Microchip home page.
#4
Jim Nickerson
User 452
  • Total Posts : 6688
  • Reward points : 0
  • Joined: 2003/11/07 12:35:10
  • Location: San Diego, CA
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2019/12/20 09:25:31 (permalink)
0
Shuaah
Has anyone been able to actually download the library? Both of the download links just take me to the Microchip home page.


same here Smile: Smile
#5
du00000001
Just Some Member
  • Total Posts : 3795
  • Reward points : 0
  • Joined: 2016/05/03 13:52:42
  • Location: Germany
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2019/12/20 09:34:01 (permalink)
0
My browser got the forwarding right:
https://www.microchip.com...3C_I2C_SoftwareLibrary
. . . but the file links are not yet up to date. Might require some more waiting ...
post edited by du00000001 - 2019/12/20 09:36:47

PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
#6
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2019/12/20 09:43:01 (permalink)
0
Always check the erratas.
 
The CH and probably the CK has a problem with the uart.
It can run fine and it may not even be noticed until you send some fast control codes that do not need printing and execute faster.
 
bit TRMT from UxSTA becomes unstable with back to back operations.
bit UTXBE from UxSTAH works as in the erratta.
;- - - - - - - - - - - - - - - -
    ;wait uart
    btss    U1STAH,#UTXBE
    bra     $-2
    mov.b   #_LF,ch
    mov     ch,U1TXREG
    mov     #_CR,ch
    bra     cout
    ;- - - - - - - - - - - - - - - -


MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#7
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2019/12/20 09:45:18 (permalink)
0
It is specific cases like sending many characters to the uart without printing.
 

MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#8
du00000001
Just Some Member
  • Total Posts : 3795
  • Reward points : 0
  • Joined: 2016/05/03 13:52:42
  • Location: Germany
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2019/12/20 15:22:02 (permalink)
0
Considering that a number of peripherals involves synchronous counters, might be these are not (yet) fit for the highest clock rates.
My question would be whether you're better of with a higher input (peripheral) clock and "local" prescalers or with a lower peripheral clock. We'll see...

PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
#9
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2019/12/20 16:25:49 (permalink)
1 (1)
I've used i2c at 100KHz and 400KHz, it does go up to 1000KHz.
i2c works fine, smbus freq. is 100KHz, the bug applies to smbus.
 
 
 
 
 
 
 
 

MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#10
picy2620
Super Member
  • Total Posts : 136
  • Reward points : 0
  • Joined: 2009/11/13 08:12:47
  • Location: Germany
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2020/01/05 02:36:00 (permalink)
0
Gort2015
I've used i2c at 100KHz and 400KHz, it does go up to 1000KHz.
i2c works fine, smbus freq. is 100KHz, the bug applies to smbus.



@Gort2015: Where do you have this information from?
If this is true, why is MCHP saying it´s not working at all?
 
#11
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2020/01/05 07:36:43 (permalink)
1 (1)
The i2c information and register configs are in the datasheets.
Any restrictions will be in MCHP.
 
i.e:
fcy = 100MHz, i2c = 1MHz, clock rate = 41
 
Just a simple calculation and there will be a list of common freqs. in the docs.
post edited by Gort2015 - 2020/01/05 08:34:37

MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#12
picy2620
Super Member
  • Total Posts : 136
  • Reward points : 0
  • Joined: 2009/11/13 08:12:47
  • Location: Germany
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2020/01/05 08:57:11 (permalink)
0
Gort2015
the bug applies to smbus.
 

I am interrested in this part of your answer. 
I know how to calculate the speed of i2c. This thread is about the new errata.
#13
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2020/01/05 13:58:52 (permalink)
1 (1)
Yes and that info is in the errata docs.
 
I thought you were asking about 1MHz i2c?
post edited by Gort2015 - 2020/01/05 14:01:36

MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#14
picy2620
Super Member
  • Total Posts : 136
  • Reward points : 0
  • Joined: 2009/11/13 08:12:47
  • Location: Germany
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2020/01/06 02:35:46 (permalink)
0
I asked following question in the very first Post #1: (regarding the new errata number 29(twenty nine))
Does anyone expirienced issue with the i2c module? I use it since serveral months without any problems.
#15
T Yorky
Super (Thick) Member
  • Total Posts : 560
  • Reward points : 0
  • Joined: 2012/08/28 02:07:35
  • Location: UK
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2020/01/06 10:16:50 (permalink)
4 (1)
I have not used the PIC33CK. No experience with it. However, if the Errata says the peripheral should not be used then I would assume they have discovered a major F up. That is 'No Workaround'.
The predicament you are in is... if you use it, you have no guarantee it will work faultlessly when you release your product. I can not imagine any engineering director being told that and having a smile on their face.
 
It is a shame as the PIC33 is a good product. But the whole purpose of expanding the range is to minimise work. If the data sheet said it didn't have a I2C port, I doubt you would have chosen the chip.
#16
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2020/01/06 14:02:45 (permalink)
1 (1)
Comparing the new errata to the one that I have from 2018, nothing new has been added to the i2c section.
 
T Yorky, errh, over speculation.
The Errata does not say that this i2c module should not be used, the op appears to be using it successfully the same as I do.
post edited by Gort2015 - 2020/01/06 14:04:24

MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#17
ric
Super Member
  • Total Posts : 27704
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: offline
Re: new i2c errata in dsPIC33CK256 2020/01/06 14:07:54 (permalink)
0
Gort2015
Comparing the new errata to the one that I have from 2018, nothing new has been added to the i2c section.

Are you looking at http://ww1.microchip.com/downloads/en/DeviceDoc/dsPIC33CK256MP508-Family-Silicon-Errata-and-Data-Sheet-Clarification-DS80000796F.pdf ?
The "DOCUMENT REVISION HISTORY" specifically mentions that errata #29 was added in December 2019.
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#18
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2020/01/06 14:14:00 (permalink)
1 (1)
I will double check.

MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#19
Gort2015
Klaatu Barada Nikto
  • Total Posts : 3956
  • Reward points : 0
  • Joined: 2015/04/30 10:49:57
  • Location: 0
  • Status: online
Re: new i2c errata in dsPIC33CK256 2020/01/06 14:25:51 (permalink)
1 (1)
Done
 
Opened them side by side.
No change from the CH 2018 (DS80000798A) errata compared to the latest 2019.
 
CH and CK are near identical with obvious differences.
 
 
 

MPLab X playing up, bug in your code? Nevermind, Star Trek:Discovery will be with us soon.
https://www.youtube.com/watch?v=Iu1qa8N2ID0
+ ST:Continues, "What Ships are Made for", Q's back.
#20
Page: 123 > Showing page 1 of 3
Jump to:
© 2020 APG vNext Commercial Version 4.5