Hi dialog,
We have bought 1000pieces around 14583 from the retailer channel. Now we have issue to download the software into the produced board.
We can connect the board with the UART and running debugging to be fine. Also the board can connected with the Jtag and running the debugging, the issue is that : when we start to download the software it reports "spi memory erasing failed. " we can read the spi sometimes also the VCC_FLASH is connected to 3.3V, how to deal with this issue. Since we can not erasing the flash, it makes us can not download the software
Device:
Very urgent issue. Please contact us back if it possible, my phone is +46739516656
Hi liuluan002,
Are you using Smart Snippets with the JTAG interface and what version? Please make sure is the latest. Also make sure that you have selected the proper pins in the Smart Snippets Board Setup configuration (2_0, 2_3, 2_4, 2_9 - 2_0, 2_3, 2_4, 2_9). Also are the SPI are used for anything else ? Are they connected to anywhere else on the PCB ? Can you please attach the error log from Smart Snippets ?
Thanks MT_dialog
Hi dialog，
After we remove the outside the Lis3dh, it can download. How to fix this without changing the schematics? Our lis3dh use p23 SDI, p21 SDO, P20 SCK, P28CS, P24 INT1, P29 INT2
嗨liulian002,
I suppose that the reason for this should be an active SPI lis3dh, since the default state of the 583 pins are pulldown your sensor is activated as soon as the 580 is activated (CS of the lis3dh is pulled low), and it might send data on the pins while the flash programmer is trying to download data. Try to keep the chip select of the lis3dh deactivated and download the flash programmer through smart snippets. You can change the flash programmer and keep the CS of the p28 high in order to keep your sensor disabled. Also please check the 583 datasheet page 12 section 3.6.7.
Thanks MT_dialog
I have tried with the PULLUP with the 1k resistor to the 3.3V for the CS PIN of LIS3DH, which still did not work. I guess is it problem with the INT1 P24, INT2 P29?
LIS3DH. P23 to SDI, P21 to SDO, P24 to INT1, P20 to SCK, P29 to INT2,P28 to CS
你的生产工具可以使用吗14583? When I checking the GUI interface, seem it does not contain the 14583 as an option.
Hi liuluan002,
There should be activity on the lines when the flash programmer tries to read/burn/erase the flash and i suppose that this is the reason that you are not able to program the 583 with the SPI sensor on it. About the production line tool, yes it can be used in order to program the 583. The option is DA14580 and make sure that the SPI-connections are changed to the 583-SPI connections.
Thanks MT_dialog
Is it possible that we use the P13 and P12 in the DA14583 chipset?
Hi liuluan002,
It depends with what you want to do with these pins, please note that that those pins interfere with the 16MHz oscillator causing BLE link loss, etc, those pins should only be used for static or low speed signals (i.e. a push button) and not for high speed signals. Please check the application note AN-B-009.
Thanks MT_dialog
Hi MT_dialog.
I have someting to quest you.
I was about to writing hex file in flash memory.
我的开发envi. is DA14581, Flash memory(Dialog recommanded), and UARTtoUSB cable.
I connected RX, TX and GND in between DA14581 and UARTtoUSB cable.
I used the SPI Flash Programmer of SmartSnippets v3.8.
Connect -> OK
Erase -> ERROR
I had tested repeatedly. please help me.
I will attach a capture file.
I'm waiting for your answer.
Thanks jglee
Hi MT_dialog.
Must I use FTDI(UARTtoUSB) necessary?
I read SmartSnippets manual.
But, I am using CP2102(silicon lab. UARTtoUSB).
The booter of SmartSnippets tool worked well with CP2102.
Thanks jglee.
Hi jglee,
Please try to use the latest Smart Snippets 3.9, also please make sure that the proper connections are made to the SPI memory and that the SPI memory is supplied, also please make sure that the correct SPI pins are selected from the Smart Snippets tool. Regarding the CP2102 we haven't tested a module like this, but since its working with the UART booter i dont think that it will cause you ant trouble. Just tested on a proboard with an external FTDI chip, didn't have any troubles.
Thanks MT_dialog