5 posts / 0 new
Last post
meriororen
Offline
Last seen:3 years 6 months ago
加入:2015-08-12 13:45
Development Mode without XTAL16M/XTAL32K

Hi,

I am using Murata ZY type which uses DA14580.

I am wondering if I can boot through development mode and let it download the firmware
via UART without any external oscillator connected to it?

is there any disanvantage?

Thanks

Device:
MT_dialog
Offline
Last seen:15 hours 56 min ago
Staff
加入:2015-06-08 11:34
嗨meriororen,

嗨meriororen,

Please check this posthttp://support.dialog-semiconductor.com/xtal-16mhz-and-32khz-must

The RC16M oscillator is inaccurate i suppose that without it you wouldn't be able to establish a proper connection.

Thanks MT_dialog

klim9531
Offline
Last seen:4 years 3 months ago
加入:2015-01-28 23:52
Hi MT_Dialog/meriororen,

Hi MT_Dialog/meriororen,

To meriororen: I am using the Type ZF also, it has a 32.768kHz crystal connected already, so it would *seem* to be necessary. The Murata chip DOES NOT HAVE pins for the 16MHz crystal, therefore a 16MHz crystal *must* be built in to the Murata. However, see my questions to MT_Dialog.

To MT_Dialog: I have a couple questions that maybe you can answer here, for the benefit of everyone else that might need this information.

The question is "when it comes time to design our own PCB using a DA14580, do we NEED TO HAVE A 32.768kHz CRYSTAL CONNECTED TO PINS XTAL32kP and XTAL32kM to establish a proper connection, via UART/SPI to another microcontroller?" The answer/link above are both horribly vague, even more so when we try to extend the answers to include the Murata Type ZF.

1.特别是DA14580(不是日本村田公司的佛罗里达州vor) The datasheet 'da14580_ds_v3-1' on page 142-3 shows diagrams for two different power supplies, lithium coin cell and alkaline battery. In both diagrams, it shows a 16MHz crystal. So we can deduce that, NO MATTER WHAT voltage of battery we use, we MUST have a 16MHz crystal on our PCB. Is this true? If so, might I suggest an application note entitled "Using the DA14580 in your PCB design" that tells us this, along with any other key bits of information.

2. Looking at the diagram for the coin cell on page 143 we see that it highlights the 32.768kHz crystal as 'optional'. So we deduce that if we use a supply voltage below 3.0V the 32.768kHz crystal is now optional. But by the answer/link above, we deduce that "If you wish to use UART to debug/download firmware on YOUR PCB, then you MUST HAVE A 32.768kHZ oscillator in YOUR CIRCUIT." Is this true? Again, an app note telling us this would really be a time saver during development.

So in summary, it would be great if you guys could put together an application note that lists the things we need to account for in our PCB design, the information seems to be 'buried in the weeds'. Thanks in advance for your response, mostly you guys do a good job answering the questions we ask, but sometimes the answer is not completely clear. --Klim

MHv_Dialog
Offline
Last seen:2 weeks 4 days ago
Staff
加入:2013-12-06 15:10
Hi,

Hi,

The Murata module indeed has the 16MHz crystal on-board. The 32kHz (or 32.768kHz) external crystal is not required unless you have a use scanario where you sleep for more than 4 seconds at the time. Not having the 32kHz crystal will add an average of 4.5uA to your current consumption while you are in a BT connected state. In all other states (advertising, idle) the power consumption will be the same whether or not you have an external crystal.

You do not need the 32kHz crystal for UART or SPI. It is possible to use the 32kHz clock for these peripheral interfaces, but it would provide very low baudrates, besides requiring an external crystal. The 32kHz is not used as a periperal clock for any of our sample applications and certainly not the boot loader.

klim9531
Offline
Last seen:4 years 3 months ago
加入:2015-01-28 23:52
Hi MHv_Dialog,

Hi MHv_Dialog,

I cannot thank you enough for the quick reply and the very specific answers to my questions!!

我发现在德velopment with the DA14580 is that, often, the answer that I am looking for is buried somewhere in all the documentation.

Its great to be able to get clear answers to questions without spending countless hours poring over datasheets and app notes, hoping that something will jump out at me.

It's somewhat frustrating to discover a problem similar to, or even exactly like, a problem that I am experiencing, where the problem resolution is not posted or made known.

Therefore, as I work through the problems that I encounter, I try to dutifully post my solutions to the forum, as you have done MHv_Dialog, in an equally clear and precise way.

+10 for your efforts, ---klim