cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC 6 MCU

trstc_4056926
New Contributor II

I am trying to use the CY8CKIT-062 - BLE to have UART on pins 8.0 and pins 8.1.  So I took the simple UART printf  example code and change the TX pin to be 8.1 in the TopDesign.cysch and rebuilt it.   Once I rebuilt and programmed the part pin 8.1 never toggles or changes.  Does anyone know if this is a known bug?

Thanks

0 Likes
Reply
1 Solution
Vison_Zhang
Moderator
Moderator

For different board revision, silicon ES version is different i think.  For production, you won't get the ES silicon.

Did you solder R100 on your board when you monitor signal on P8[1]?  This resister is not load by default.

Capture.JPG

View solution in original post

0 Likes
Reply
7 Replies
Vison_Zhang
Moderator
Moderator

I think maybe the PDL version you used is not compatible with the 062-BLE board. If the board revision is 11, please change to use PDL 3.0.1 or PDL 3.0.4.

Capture.JPG

1.jpg

0 Likes
Reply
trstc_4056926
New Contributor II

Is this because of a silicon change between boards? If so how do we know which to use in production?

0 Likes
Reply
trstc_4056926
New Contributor II

Changing the PDL version did not fix the problem. 

0 Likes
Reply
trstc_4056926
New Contributor II

I have tried a rev13 board with 3.0.1 and it does not work. Rev11 board with 3.0.1 does not work either.

0 Likes
Reply
trstc_4056926
New Contributor II

I tried turning 8.1 into a GPIO and drive high and it does not work either.

Is there something with the cap sense pins that need to be reconfigured.

0 Likes
Reply
Vison_Zhang
Moderator
Moderator

For different board revision, silicon ES version is different i think.  For production, you won't get the ES silicon.

Did you solder R100 on your board when you monitor signal on P8[1]?  This resister is not load by default.

Capture.JPG

View solution in original post

0 Likes
Reply
trstc_4056926
New Contributor II

Thanks,

I was not use to "No Load" as meaning not populated and since the resistor had a value I assumed it was populated.  I asked another engineer and he said he had found the same problems and assumed he fried the driver on the chip. 

Thanks again!

0 Likes
Reply
Top labels