Re: Digest Number 4558

Group for Rabbit C-programmable microsThanks both.
I am comforted that it is probably not a problem of our making.
It is a shame about the brick wall that Digi have built. It is bound to lose them sales.  They have certainly lost our custom. We shall never use Rabbit modules again in new designs.
There are better ones around anyway. We have used the Netburner on some other products and, after around 500 units there have been no problems like this. The Netburner MOD5570 and MOD55415 are true 32 bit devices with flat addressing without messing with pages. 
Ken



  1a Re: RCM3000 hardware problems Tue Dec 29, 2015 9:03 am (PST) . Posted by: "seecwriter" seecwriter Ken,
  Years ago we had a similar problem where the module would boot up with incorrect baud rates. As Tom suggested, we modified our initialization code to set the clock divisors an not rely on the Bios to do it. That solved the problem for us.
  Steve

  Sent from my Galaxy Tab® S2-------- Original message --------From: "[email protected] [rabbit-semi]" <[email protected]> Date: 12/28/2015 8:18 AM (GMT-08:00) To: [email protected] Subject: [rabbit-semi] RCM3000 hardware problems 

   

  Has anyone seen a problem on the RCM3000 core 
  modules where they fail to initialise properly at power-up?
  We are seeing it on RCM3110 and RCM3200 at lower 
  temperatures, around 15 to 20 Celsius.
  The symptoms are that the timers A and B do not 
  produce the required frequency divisions. Baud rates are wrong.
  The symptoms are always cured by 
  taking  /reset_in low manually. That sort of eliminates our 
  code.
   
  Despite the fact that we are buying large 
  quantities of Rabbit modules from Digi they are being particularly un-helpful 
  about this problem. I am afraid that they appear much less helpful than the old 
  Rabbit people.
  They have given advice such as "connect an external 
  reset timer to /reset_in "!!. 
  After one department suggested that we 
  send a couple of troublesome modules back for them to investigate another 
  department refused to take them because "they are out of warranty".
   
  We have spent many hours testing and trying to 
  eliminate any source of the problem that might be in our application and can 
  find none. We are convinced that it is a design or manufacturing problem in the 
  product.
   
  Due to Digi's hard-line and unwillingness to 
  support their product we have decided to eliminate Rabbit modules or 
  any other Digi product from any short list of components for any new 
  projects.
   
  K.Shail
  Sparc Systems Ltd.
  UK
   
   
   
   
   
   
   
   

  Reply to sender . Reply to group . Reply via Web Post . All Messages (4) . Top ^ 1b Re: RCM3000 hardware problems Tue Dec 29, 2015 12:57 pm (PST) . Posted by: "Fournier, Peter" pfournier_astromed Ken, 

  I also ran into this. We had the wrong cap on the crystal and it did not start up at the right frequency but eventually locked in. Putting the correct cap on solved the problem. Since then I used an oscillator, now I don’t have to worry about purchasing buying a different manufacturers crystal that wants 22pf instead of 18pf. 

  -Pete F 

  From: [email protected] [mailto:[email protected]] 
  Sent: Tuesday, December 29, 2015 11:59 AM 
  To: [email protected] 
  Subject: RE: [rabbit-semi] RCM3000 hardware problems 




  Ken, 

  Years ago we had a similar problem where the module would boot up with incorrect baud rates. As Tom suggested, we modified our initialization code to set the clock divisors an not rely on the Bios to do it. That solved the problem for us. 

  Steve 


  Sent from my Galaxy Tab® S2 
  -------- Original message -------- 
  From: "[email protected] [rabbit-semi]<mailto:[email protected]%20[rabbit-semi]>" <[email protected]<mailto:[email protected]>> 
  Date: 12/28/2015 8:18 AM (GMT-08:00) 
  To: [email protected]<mailto:[email protected]> 
  Subject: [rabbit-semi] RCM3000 hardware problems 


  Has anyone seen a problem on the RCM3000 core modules where they fail to initialise properly at power-up? 
  We are seeing it on RCM3110 and RCM3200 at lower temperatures, around 15 to 20 Celsius. 
  The symptoms are that the timers A and B do not produce the required frequency divisions. Baud rates are wrong. 
  The symptoms are always cured by taking /reset_in low manually. That sort of eliminates our code. 

  Despite the fact that we are buying large quantities of Rabbit modules from Digi they are being particularly un-helpful about this problem. I am afraid that they appear much less helpful than the old Rabbit people. 
  They have given advice such as "connect an external reset timer to /reset_in "!!. 
  After one department suggested that we send a couple of troublesome modules back for them to investigate another department refused to take them because "they are out of warranty". 

  We have spent many hours testing and trying to eliminate any source of the problem that might be in our application and can find none. We are convinced that it is a design or manufacturing problem in the product. 

  Due to Digi's hard-line and unwillingness to support their product we have decided to eliminate Rabbit modules or any other Digi product from any short list of components for any new projects. 

  K.Shail 
  Sparc Systems Ltd. 
  UK 












  Reply to sender . Reply to group . Reply via Web Post . All Messages (4) . Top ^ Visit Your Group 
   • Privacy • Unsubscribe • Terms of Use