Search site
Home

JTAG can not find device after OTP

2 weeks ago

JTAG can not find device after OTP

Posted byxu.bovey40 points 10 replies
0 upvotes

Hi all

1st. burn secondary_bootloader_531.bin with config otp header

app not run and jlink cannot find chip

2nd. config otp header as follow, then jlink cannot find chip

step1. i connect DA14531 by JTAG

step2. read OTP Header

step3. change Application Flag 1& 2 to YES

step3 burn

step4 repower da14531

step5. cannot find chip by jlink

i have update the bin, header and log.

the log file is 2nd

maybe i miss some thing, so need your help

thanks

SDK is 6.380.12.6

SDK6.0.14 Software Tools
Attachment Size
secondary_bootloader_531.zip 3.65 KB
header.zip 381 bytes
log1.zip 1.4 KB

2 weeks ago

PM_Dialog

Hi xu.bovey,

Thanks for your question online and for your interest in our BLE solutions. So, the secondary bootloader is burnt into the OTP image? Can you please indicate why you need to do this?

Have you done any modification in the secondary bootloader project? Additionally, is it a custom board, or you are using any of our DKs?

Thanks, PM_Dialog

2 weeks ago

xu.bovey 40 points

thanks for your replay.

1. the secondary bootloader is burnt into the OTP image? yes

2. Can you please indicate why you need to do this? rx image from mcu stm32

3. Have you done any modification in the secondary bootloader project? yes

6.380.12.6\utilities\secondary_bootloader

a. uart_booter.c line 166 add 2 line.

SetWord16(WATCHDOG_REG, 0xFF); // Reset WDOG

SetWord16(RESET_FREEZE_REG, FRZ_WDOG); // Start WDOG

b. bootloader.h line 24

/************** UART Booter section**************/ #define UART_SUPPORTED /************** Flash memory section **************/ #undef SPI_FLASH_SUPPORTED #undef I2C_EEPROM_SUPPORTED

c. user_periph_setup.h line 74

#define UART_TX_PIN GPIO_PIN_7

#define UART_RX_PIN GPIO_PIN_8

4. is it a custom board, or you are using any of our DKs? custom board

i had add the project files and sch picture

the project work well when i download in into ram

Attachment Size
secondary_bootloader.zip 3.36 MB
sch.png 79.25 KB

2 weeks ago

PM_Dialog

Hi xu.bovey,

Sorry for the questions, but what I can understand is that you want to program the DA14531 via P0_8 thought an STM32. Is my understanding correct?

Thanks, PM_Dialog

1 week ago

xu.bovey 40 points

Hi

yes, as the link saidhttp://lpccs-docs.dialog-semiconductor.com/SW_Example/SDK6/Booting_DA14…

1 week ago

PM_Dialog

Hi xu.bovey,

This example is using the SPI Flash to burn the secondary bootloader – please check section 2.2. Programming the BLE TINY Click with the secondary bootloader. You can use either the Flash Programmer tool or the SmartSnippets Toolbox to burn the SPI Flash.

Additionally, the secondary bootloader should be used as provided without any modifications.

Thanks, PM_Dialog

1 week ago

xu.bovey 40 points

hi pm

thanks.

yes, the example is using SPI.

in my application. i need send the firmware to DA14531 from STM32. i find the secondary_bootloader.bin, so my plan is burn it into OTP, so that DA14531 can receive firmware from STM32 through P0_7,P0_8, because there was no extern spi flash or eeprom.

please help me check that is there some mistake in my application?

我烧了OTP,参考文档:http://lpccs-docs.dialog-semiconductor.com/UM-B-083/tools/otpProgrammer…

1 week ago

xu.bovey 40 points

finally i find the question.

because the code:

if (GPIO_GetPinStatus(UART_GPIO_PORT, UART_RX_PIN))

i just connect TX to my serial port. so it didn't send out 0x02. when i connect tx and rx, i can receive DA14531 data.

thanks

1 week ago

xu.bovey 40 points

so the last problem is i can not conenct jtag after burn otp

1 week ago

PM_Dialog

Hi xu.bovey,

Did you disable the JTAG in the OTP Header?

Thanks, PM_Dialog

1 week ago

xu.bovey 40 points

Hi

no, the datasheet said it could disable, but i do not config the CS table .

board #1 use default config. board #2 only config "Application Flag 1& 2" to YES in main group.