⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
fritsch
Offline
Last seen: 1 year 10 months ago
Joined: 2017-10-18 14:17
DA14580

Hi,
I analyzed the software of a vitaltracker (supplied with DA14580) with a Segger JLink in SmartSnippet Studio. I can read the contents of the SPI-Flash Memory and the OTP Memory.
I found that the OPT Header describes the Adress of JTAG as "Disabled". How can i connect the Target when with JTAG "Disabled"? Can anyone explain me that?
Thanks for your investigation.

best regards
Friedhelm

Device: 
PM_Dialog
Offline
Last seen: 9 months 2 days ago
Staff
Joined: 2018-02-08 11:03
Hi fritsch,

Hi fritsch,

When programming the “JTAG disable” bit in the OTP header you can no longer use the Serial Wire Debugger port.

Thanks, PM_Dialog

fritsch
Offline
Last seen: 1 year 10 months ago
Joined: 2017-10-18 14:17
Hi

Hi
At the first time of my analyse i thougt it was a random contents in the memories.
In the OTP-Header is the JTAG Disable Flag "Disabled" with grey background underlined, so that the flag cannot be changed. OK thats the programmers choice.
But how can I get connection with the JTAG/JLink Debugger by Segger OZONE and JLink GDB Server. The SmartSnippetStudio tells me the right Target-Constellation , Contents of the OTPHeader was dumped and on adress JTAG Flag is AA AA AA AA reading. This cannot be possible when i take your reply for absolutly.
A part of the dump of the OTP Header is following:

47F00 Application Flag 1 0x00000000:Emty OTP 00 00 00 00
47F04 Application Flag 2 0x00000000:Emty OTP 00 00 00 00
47F08 RF_Trim Bits [31:16) =RF_TRIM1 00 15 68 8F
47F0C CRC crc16 of the calibration 00 00 32 FD
47F10 Reserved free for future 00 00 00 00
47F14 Reserved 00 00 00 00
47F18 Reserved 00 00 00 00
47F1C Reserved 00 00 00 00
47F20 Reserved 00 00 00 00
47F24 Reserved 00 00 00 00
47F28 Reserved 00 00 00 00
47F2C Reserved 00 00 00 00
47F30 Reserved 00 00 00 00
47F34 Reserved 00 00 00 00
47F38 Reserved 00 00 00 00
47F3C Reserved 00 00 00 00
47F40 Reserved 00 00 00 00
47F44 Custom Fields Custom Fields 00 00 00 00
47F48 Custom Fields Custom Fields 00 00 00 00
47F4C Custom Fields Custom Fields 00 00 00 00
47F50 Custom Fields Custom Fields 00 00 00 00
47F54 Custom Fields Custom Fields 00 00 00 00
47F58 Custom Fields Custom Fields 00 00 00 00
47F5C Custom Fields Custom Fields 00 00 00 00
47F60 Custom Fields Custom Fields 00 00 00 00
47F64 Time Stamp Byte 3,Byte 2,Byte1,Byte0 0A F8 5A 5E
47F68 Tester Bits[7:2]=Tester_ID, 00 01 00 00
47F6C Position Byte3: LOT, Byte2: Wafer Byte1: Y coord, Byte0: X coord 00 00 00 00
47F70 Package used 0x00=WLCSP34, 0xAA=QFN40, 0x55=QFN48,0x99 KGD QFN40
47F74 32kHz Source Selec 0x00 XTAL 32kHz, 0xAA: RC 32kHz RC
47F78 Calibration Flag Bit[31:16]: 0A5A5, Bit5: Trim_VCO_Cal, Bit4: A5 A5 00 2D
47F7C LNA Trim Values LNA Trim Values 07 42 A1 D1
47F80 RFIO Capacitance Trim RFIO Capacitance Trim Value 00 00 00 00
47F84 BandGap Trim Values BandGap Trim Values 00 00 2A 62
47F88 RC 16 Trim Values RC 16 Trim Values 00 00 00 09
47F8C XTAL 16MHz Trim XTAL 16MHz Trim Values 00 00 00 00
47F90 VCO Trim Values VCO Trim Values 00 00 00 02
47F94 Customer Code Signatur Hash Signature of Code 00 00 00 00
47F98 Customer Code Signatur Hash Signature of Code 00 00 00 00
47F9C Customer Code Signatur Hash Signature of Code 00 00 00 00
47FA0 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FA4 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FA8 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FAC Customer Code Signatur Hash Signature of Code 00 00 00 00
47FB0 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FB4 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FB8 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FBC Customer Code Signatur Hash Signature of Code 00 00 00 00
47FC0 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FC4 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FC8 Customer Code Signatur Hash Signature of Code 00 00 00 00
47FCC Customer Code Signatur Hash Signature of Code 00 00 00 00
47FD0 Signatur Algorihm 0x00 None,0xAA: MD5, 0x55: SHA-1, 0xFF: CRC32 None
47FD4 Device unique ID Device number (written as a string of bytes, i.e. 17 9D2A 1E
47FD8 Device unique ID Device number (written as a string of bytes, i.e. FE 60 00 00
47FDC Custom Fields Custom Fields 00 00 00 00
47FE0 Custom Fields Custom Fields 00 00 00 00
47FE4 Custom Fields Custom Fields 00 00 00 00
47FE8 Custom Fields Custom Fields 00 00 00 00
47FEC Custom Fields Custom Fields 00 00 00 00
47FF0 Custom Fields Custom Fields 00 00 00 00
47FF4 Remapping Flag 0x00 SRAM remapped to 0, 0xAA OTP remapped to 0 SRAM
47FF8 DMA Length Number of 32-Bit words 0x2000 words 00 00 00 00
47FFC JTAG Enable Flag 0x00 Enable, 0xAA Disable AA AA AA AA
I m wondering.
best regards
fritsch

PM_Dialog
Offline
Last seen: 9 months 2 days ago
Staff
Joined: 2018-02-08 11:03
Hi fritsch,

Hi fritsch,

The JTAG could be disabled into the OTP, but if the application that is mirrored from the OTP enables the JTAG bit, then you could read the OTP. Be aware that when you attach the Smart Snippets into the OTP head and the JTAG bit is enabled from the application, you will read that the JTAG OPT field is disabled.

Thanks, PM_Dialog