Good morning,
I am transitioning from the DA14531 USB Dev Kit to a custom prototype board. I was able to correctly configure the Dev Kit for programming per the serial wire debug guide. The custom prototype is now recognized by the Keil IDE and can enter debug mode.
However, when attempting to run the code there is an issue with CPU being halted which I believe is related to the reset line. Log below:
* JLink Info: Memory map 'after startup completion point' is active* JLink Info: CPU could not be halted***JLink Error: Cannot read register 15 (R15) while CPU is running***JLink Error: Cannot read register 16 (XPSR) while CPU is running***JLink Error: Cannot read register 0 (R0) while CPU is running***JLink Error: Cannot read register 1 (R1) while CPU is running***JLink Error: Cannot read register 2 (R2) while CPU is running***JLink Error: Cannot read register 3 (R3) while CPU is running***JLink Error: Cannot read register 4 (R4) while CPU is running***JLink Error: Cannot read register 5 (R5) while CPU is running***JLink Error: Cannot read register 6 (R6) while CPU is running***JLink Error: Cannot read register 7 (R7) while CPU is running***JLink Error: Cannot read register 8 (R8) while CPU is running***JLink Error: Cannot read register 9 (R9) while CPU is running***JLink Error: Cannot read register 10 (R10) while CPU is running***JLink Error: Cannot read register 11 (R11) while CPU is running***JLink Error: Cannot read register 12 (R12) while CPU is running***JLink Error: Cannot read register 13 (R13) while CPU is running***JLink Error: Cannot read register 14 (R14) while CPU is running***JLink Error: Cannot read register 15 (R15) while CPU is running***JLink Error: Cannot read register 16 (XPSR) while CPU is running***JLink Error: Cannot read register 17 (MSP) while CPU is running***JLink Error: Cannot read register 18 (PSP) while CPU is running***JLink Error: Cannot read register 20 (CFBP) while CPU is running
My questions are:
1. Is this error likely due to the reset line being disconnected?
2. How do I connect BOTH the SWDIO pin AND Reset from my custom PCB to the USB dev kit given that the SWDIO connection (per serial wire debug guide) uses the connection labeled as RES on the actual silk layer of the USB dev kit?
*I currently have P0_0 multiplexed with UART_TX and Reset by using a resistor to for the connection. Only UART_TX was connected on the custom PCB.
Hi Nate,Thank you for the reply.On your Schematic I do not see any SPI Flash or I2C EEPROM to store the FW.Are you going to load the FW directly into SRAM every time via Host MCU?For supported SPI Flash part numbers please refer here: AN-B-088: DA1453x Flash Selector GuidePlease also refer on AN-B-075: DA14530/531 Hardware GuidelinesFrom my understanding you are trying to implement Buck Configuration:On your Schematic:On VBAT_High I do not see the Battery connection.Please also check your Crystal Part number based on AN-B-075:Best Regards,OV_Renesas
Apologies for any confusion as I am new to circuit design and am not familiar with standard practices or conventions.
My understanding was that I could use the DA14531's internal 32kB OTP memory for firmware storage.
For the buck configuration, my schematic probably isn't following conventions but does have a connection from VBAT_High to the power source shown on the battery protection circuit:
The crystal selected was the XRCGB32M000F1H19R0 as the XRCGB32M000F1H00R0 is no longer manufactured and this was the closest comparable I could find at the best price. The only difference I see is the ESR of 50 Ohms for the former vs 60 Ohms for the latter.
Should these specifications be sufficient to run the Blinky sample code discussed previously (suggesting that there is an issue in assembly) or would there be other possible hardware errors?
Thank you again!
Hi Nate,Thank you for the reply.
Nate said:My understanding was that I could use the DA14531's internal 32kB OTP memory for firmware storage.
Yes, if your firmware is small you can store it in the OTP.Please refer here: 10. Boot from OTPand here: 17. OTP Programming — DA145XX Tutorial SDK Getting startedYou will find the necessary changes in order to store your FW on the OTP and boot from there.While you are in development stage, please do not flash the OTP (One Time Programmable) since you are not going to be able to change this. You should only download your FW into the SRAM in order to test it.
Nate said:For the buck configuration, my schematic probably isn't following conventions but does have a connection from VBAT_High to the power source shown on the battery protection circuit:
Could you please run some tests on your custom board.Check the Voltage level on VBAT_High and VBAT_low when you have downloaded your FW into the SRAM. If possible probe an oscilloscope on the XTAL Pins and check the behavior during boot time. Please also refer here as a reference: DA1453x Hardware Design Examples — DA14531 Hardware Design ExamplesBest regards,OV_Renesas
Thank you for the resources! Apologies for the delay in response as I have been moving houses.
I must be missing something as I haven't been able to locate the actual files from the DA1453x Hardware Design Examples. I have referenced AN-B-075 frequently in my process along with AN-B-027 to copy the ZOR antenna design for this initial prototype. I also referenced the DA14531 USB Development kit schematic. However, I can't seem to locate the actual design files from the link provided although I recall seeing them previously.
The voltage level for VBAT_High is 3.25 and VBAT_Low is 1.281.
Unfortunately, I haven't designed test points for the XTAL Pins so I'm unable to do so at this time.
One point of concern to me is that I see the power LED faintly illuminating when the ground pin is disconnected with only 3.3V & SWDIO connected. This behavior is only observed when the device is connected to SmartSnippets Toolbox. Is that to be expected or does that suggest a bridged solder joint on one of the pads?
EDIT: Was able to locate hardware design examples on the Renesas DA14531 page. The main difference I see being the use of SPI flash.
Hi Nate,Thank you for the reply.1) Please make sure you follow: 19. Serial Wire Debug Probe — DA145XX Tutorial SDK Getting startedPlease double check that R3 and R11 have been removed.2) Please then refer here: 3.3. RAM — UM-B-083 on how to download your FW image (ideally please use the ble_app_barebone default FW) directly into RAM.If you are not able to see your device advertising, we would need to see the behavior of the XTAL during boot.Best Regards,OV_Renesas