CYBLE416045 module unable to debug

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
TW_Chia
Level 3
Level 3
First like received 25 replies posted 10 sign-ins

Good day,

I have developed a board using the CYBLE416045-2.

I have also a CY8CPROTO-063-BLE prototyping board with CYBLE416045-2.

On PSoC 4.2, I created a project based on the BLE Find Me example code.

On the CY8CPROTO-063-BLE board. I was able to program it to run in Debug mode and the code is able to break at the start of the main function for CM4.

However, with the same project, there is an issue that the customized board is not able to run in the Debug mode.

The following message was shown in the Output window.

*************************

Programming device 'PSoC 63 CYBLE-416045-02 (CM4)' with file 'C:\Users\CTWMac\Documents\PSoC Creator\BLE01\BLE01.cydsn\CortexM4\ARM_GCC_541\Debug\BLE01.hex'.

Device ID Check

Erasing of Main Flash...

Programming of Flash Starting...

Protecting...

Verify Checksum...

Finished Programming

Device 'PSoC 63 CYBLE-416045-02 (CM4)' was successfully programmed at 08/15/2019 15:18:10.

Continuing target program

The target program has stopped at: file:  line: -1 function: ?? address: 0x1600400C

***********************

PSoc_Debug_Error.png

The schematic layout for the BLE portion of the customized is

BLE_Schematic.png

Can anyone please advice the possible issue that I may have?

Thank you.

0 Likes
1 Solution
TW_Chia
Level 3
Level 3
First like received 25 replies posted 10 sign-ins

Good day,

I just discover that I did not solder the 32.768kHz crystal.

After this external crystal is soldered, it can now work in the debug mode.

May I ask the reason how the crystal resulted in the issue that I encounter?

What can be done to disable the use of the 32.768kHz external crystal?

Thank you. 

View solution in original post

0 Likes
3 Replies
TW_Chia
Level 3
Level 3
First like received 25 replies posted 10 sign-ins

Good day,

I just discover that I did not solder the 32.768kHz crystal.

After this external crystal is soldered, it can now work in the debug mode.

May I ask the reason how the crystal resulted in the issue that I encounter?

What can be done to disable the use of the 32.768kHz external crystal?

Thank you. 

0 Likes

When the clock crystal is defined to drive the ILO your project will not start when the oscillator "hangs". This will be the case when the crystal is not soldered in.

Go to the low speed clock definitions and remove the WCO. You may alternatively use some APIs to start the WCO and configure it as the source for ILO.

Bob

Dear Bob,

Thank you for your reply.

0 Likes