Hi,
I have implemented a program based on the DSPS example. It runs on the DevKit Basic board when it is loaded from Connection Manager or loaded into SPI Flash with Smart Snippits.
My problem is, on my custom board, wich has a PAN1740 module and W25X20CL ( just like the DevKit ), the program will run, advertise, and connect, when loaded by Connection Manager, but when loading the program to flash with Smart Snippits it does not run. Using "Burn & Verify" button loads and verifies. Pressing the reset button on my board, causes activity on the CS\, MOSI, MISO, and SCK pins of the flash chip. It seems the program is loading from flash, but there is no sign of advertising on a BLE Central host.
The UART pins have been re-defined to resolve the conflict with the SPI port pins:
#define UART1_TX_PORT GPIO_PORT_0
#define UART1_TX_PIN GPIO_PIN_1
#define UART1_RX_PORT GPIO_PORT_0
#define UART1_RX_PIN GPIO_PIN_2
#define UART1_RTS_PORT GPIO_PORT_0
#define UART1_RTS_PIN GPIO_PIN_4
#define UART1_CTS_PORT GPIO_PORT_0
#define UART1_CTS_PIN GPIO_PIN_7
What am I missing?
Hoping for help and wishing a Happy New Year,
Corky
Mon, 2015-12-28 19:52
#1
Boot from SPI Flash
Keywords:
Device:
Upon boot up, the boot ROM in DA14580 will scan pre-defined UART, SPI and I2C ports for valid firmware image downloading, If you can see SPI_CLK signal on P0.0 pin more than 1ms, it implies a valid image downloading process. If not, it may be due to not enabling the SPI header put before the image while programming the SPI Flash. If this is not the cause, maybe you can insert a small function to output a character string at the head of main function to determine the downloaded image can be executed firstly. Need more info to fix your issue step by step.
The same HEX file burned to Flash on the DevKit Basic, works as expected. The flash content on my board verifies, ans appears to load on boot, but it appears that it does not run correctly. I will try a simple program to echo characters to the UART.
It may have something to do with the connection to the J-Link, but it works fine now. The issue can be marked as resolved.
Happy, healthy New Year to All!