Comments on: Lesson 4 – PSoC 6 Introduction: CapSense

By: Alan Hawse

Alan Hawse — Fri, 05 Oct 2018 16:48:51 +0000

In reply to JWeaver.

Thanks… good catch. Ill fix it.
Alan

By: JWeaver

JWeaver — Wed, 03 Oct 2018 13:28:43 +0000

FYI for those trying to duplicate what Alan is doing, if you run the UART task as shown above, you’ll notice that two case statements are missing for “s” and “S” to start and stop the PWM. Just add them (from Lesson 3) for completeness if you wish.

By: Alan Hawse

Alan Hawse — Fri, 02 Feb 2018 21:17:02 +0000

In reply to Charles. I made an edit to show where. Thanks for the comment

By: Charles

Charles — Fri, 02 Feb 2018 18:15:48 +0000

For the section “Add a new PWM Task and Modify the UART Task”, the section is not explicit in saying where you are supposed to put the subsequent code.

By: Alan Hawse

Alan Hawse — Mon, 13 Nov 2017 19:02:31 +0000

In reply to Tom Oke.

1- Yes you are right… if it had stayed at 10240 (which for some reason is the PSoC Creator default it wouldn’t work. I notice above that I “say” to make it (48*1024) which I just picked out of the air.

2- Yes you are right. If you look in the workspace on git hub I have the CapSense project priorities all set at 3… which means that when I made that workspace I didn’t copy/paste as I showed in the demo.

Personally I think having their priority all set to (3) is the best way.

Thank you for the clarifications and I am glad you enjoyed the event.

By: Tom Oke

Tom Oke — Thu, 09 Nov 2017 21:00:42 +0000

I found a few things I had to correct (unless I missed something).

1. If the configTOTAL_HEAP_SIZE was left as the 10240, the Capsense task would fail to start and return a -1 code, indicative of not enough memory.
2. With the heap set higher (I took your 48*1024) from the webinar, the capsense would start, but since the task creation priorities were 3 for the PWM and Capsense but only 1 for the UART task, it would not start (at least to the printf) until I changed the taskYIELD to a vTaskDelay(1), or changed the UART priority to the 3 as well to let the pre-emptive scheduler work things out.

Otherwise the webinar was great, informative and entertaining. Thanks very much.