9 posts / 0 new
Last post
imalamoud
Offline
Last seen:2 months 3 weeks ago
加入:2014-11-16 21:34
DA14580没有t start the boot sequence.

Hello,

We have created a design board in accordance with with AN-B-023 (page 9 , fig 3, interfacing with external memory). The board contains Flash memory, FTDI UART and DA14580 obtained through Digikey.

We replicated connections from AN-B-023 and took DA14580 connections schematic from the Basic kit. The prototype created with the Basic kit and FTDI cable worked fine.

However I can not start the on-board DA14580 on out board.

Both 16M and 32K crystals work but the boot sequence does not start upon reset. I see virtually constant 1.8V output on the DA's TX after reset.

Can you please let me know possible troubleshooting ways?

Do chips supplied from bulk vendors come with a bootloader or they need to be prepped somehow?

Regards,
Ilia

JE_Dialog
Offline
Last seen:3 weeks 4 days ago
Staff
加入:2013-12-05 14:02
Hi Imalamoud,

Hi Imalamoud,

Could you put your schmatics onto a site where we can download and take a look ?

Also, if you probe around the circuit, could you indicate what voltage you see on which pins ? first , we need to check the schematic and voltages on the right pins etc.

What application are you trying to run in the 14580 and how did you generate that /download that into FLASH ? you mention it worked fine in the BASIC kit.

For bootload : devices are supplied completely blank : if you have no secondary bootloader in OTP, the device will automatically scan the different interfaces (up to 5 times) to detect boot source. There is no programmed secondary bootloader by default in the DA14580, that would need to be programmed. However, the device can perfectly boot from FLASH w/o a secondary bootloader, it just takes longer. The DA14583 (flash on board) has a bootloader built into it.

BR JE_Dialog

imalamoud
Offline
Last seen:2 months 3 weeks ago
加入:2014-11-16 21:34
Hello,

Hello,

Thank you for fast reply

Please take a look at the diagram here.

https://www.dropbox.com/s/fq99vtwbfe3kb0u/dongle.pdf?dl=0

I shall run SPS server there but I am not there yet. The boot sequence does not start at all. It does not try to detect UART on the port 0.

I have impression that port 0 is not driven at all.

Perhaps we are missing some pullups or etc. This is a 40-pin.

Thanks,
Ilia

MH_Dialog (not verified)
Hello Ilia,

HelloIlia,

you may probe VDCDC to see if it is 1.4V. If you didn't see GPIO toggling, there may some HW faliure.

BR, Morris

imalamoud
Offline
Last seen:2 months 3 weeks ago
加入:2014-11-16 21:34
Hello Morris,

Hello Morris,

Thank you for the reply. We shall try a different chip batch or a Murata module.

What is the purpose of 32KHz crystal?

Which features will be disabled if it is not connected?

Thanks,
Ilia

Joacimwe
Offline
Last seen:1 year 5 months ago
Guru
加入:2014-01-14 06:45
If you skip the external

If you skip the external 32KXtal and use the internal RC32K you will loose precision. This effectively means that you will not be able to have connection-intervals (including slave latency) that extend over 2 seconds. This also applies to internal timers that you set. If no BLE-related stuff is happening then you would not be able to have timers over ~2-4 seconds as well. Those are the biggest impacts that we have noticed.

imalamoud
Offline
Last seen:2 months 3 weeks ago
加入:2014-11-16 21:34
Thank you. How would it

Thank you. How would it affect DSPS application if at all?

imalamoud
Offline
Last seen:2 months 3 weeks ago
加入:2014-11-16 21:34
How would it affect DSPS

How would it affect DSPS application if at all?

JE_Dialog
Offline
Last seen:3 weeks 4 days ago
Staff
加入:2013-12-05 14:02
Hello Imalamoud, that would

Hello Imalamoud, that would really depend upon the length of extended sleep and how you configure / use DSPS : .. if you have long connection intervals, the XTAL32 is needed because of its accruacy - with an RC32 it will not be precise enough, and you will find that you will miss connections / exceed slave latency and lose connection... for any standard or propietary profile.

BR JE_Dialog