Help from the Atmel guys?

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Is it possible to communicate with the folks that designed the Xmega?  Has Trondheim been obliterated?  Is it now only a blank spot on Google maps, like area 51?

 

The USB silicon seems to do something desirable about disabling DFLL when we are suspended and not receiving SOF.  That works well.  It also tries to enable DFLL when we are resumed and again receiving SOF.  Sometimes this works and sometimes doesn't, with disastrous results to our clock frequency.  None of this appears in the manual, as far as I can see.  I might be able to kludge Atmel's boo boo, but it would be nice to communicate to someone with more knowledge of the silicon.   

 

 

Last Edited: Thu. Mar 15, 2018 - 07:09 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

You would need to raise a support case through the Microchip site

 

See: https://www.avrfreaks.net/forum/microchipatmel-support-page

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks, I think I'm in now.  I see my old cases.   For a while, I was thinking it may be easier to switch to another brand of Microcontroller.

 

P.S.  Microchip won't accept special characters in passwords.  I don't know if they will accept zero.  That is a rather new concept to us westerners.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have you looked at the ASF code? It's an onion of many, many layers but when you get to the core it can offer some useful hints on how to handle stuff like DFLL. Just create a dummy USB project and check how it manages DFLL.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just looking at the ASF has got to cause severe brain injury.

 

However if it gets SOF to work as well as I think it should be able to, I may risk my sanity and look at it.

 

If the clock frequency is still good after waking the PC from sleep, while using SOF, I'll take a peek.

 

The real goal is to have SOF fix the frequency after attaching to the USB bus that is way off before attaching to the USB bus. 

 

Can ASF do either of these? 

 

 

Last Edited: Sat. Mar 17, 2018 - 12:41 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The ASF code does seem to recover when the PC comes out of sleep, yes.

 

You can actually detect when the PC goes to sleep. You are supposed to according to the USB spec, and go into low power state. Basically if you stop getting SOF markers for several milliseconds then you know the PC is napping, and on XMEGA you can use a timer to measure that with the SOF event triggering a timer reset.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I did a quick look at the ASF examples.  I'm not sure any of them use SOF to adjust the 32MHz RC osc..   I will investigate some more later.  There is another little project I want to work on now.