Thats cool.. I didn’t know that… I’m quite sure that uS delays are implemented as busy wait.

Alan

That chip has an RTOS running in it with a 1ms tick. If you are trying to time things at the 100micro or 1micro level you are going to be in trouble with the bluetooth. The Bluetooth threads are very timing critical to keep things going.

Alan

Ooops, there is wiced_rtos_delay_microseconds, so only left the nanoseconds part of the question. Thanks

Thanks Alan,
Any idea for the smaller delays: 10MICRO and 100NANO?
The only problem with wiced_rtos_delay_milliseconds I see so far is I cant find any information about the RTOS threads that are automatically started what serve they and what priority have, so not to mess the bluetooth communication with such delay if they will run on the same thread. Even if I make a dedicated thread, need to find what priority to put there (lower than BT) … but will try … this WICED/20719 is quite a challenge 🙁
Regards

Oh… I thought that you were talking about PSoC 4s (or 6’s).

For 20719 if you do something like this you can use wiced_rtos_delay_millisconds

I don’t see anywhere CyDelay or Cy_SysLib_Delay in the API for the CYW20719 – this is the only reason I’m looking for something like this?
The only place in WICED Studio 6.2.1 I could see them is for 43xxx platform, not for CYW20719 or any other of the included platforms.
Thanks

I don’t know… everything I could imagine would be more complicated… you could use SysTick or if you are running an RTOS like FreeRTOS your could use vTaskDelay.

What is wrong with CyDelay (for an application like this?) … obviously it is a busy wait which isn’t ideal. I suppose that if I did it again it would be done with FreeRTOS. In fact you can see that I wrote several articles about using Segger where I did vTaskDelay

I suspect that you have not added all of the .c files to your project.

If that EINK display driver is in the library… then yes I think that is best. But I dont know which one you are talking about.

I have been wondering if this is still the best starting point to interface PSOC 4 to SPI e-ink display in your opinion?
/Alex

The real problem is that there is a flaw in the design of the HAL… I have itchy fingers to fix it… but don’t really have time… that is what kept me from really dealing with the problem.

Maybe to keep track of the changes on the u8g2 source code you can add it’s repo as a git submodule on the custom component repository.

Carlos

Yes. I was/am planning on moving the code that makes the hardware access layer work into that file instead of having it in main. But I can’t decide the best way to implement it. As soon as I figure it out Ill do that.

Really I want to make it all a component… but Im don’t want to permanently freeze his source code into the component as it continues to change… so I am not sure.

Email me (engineer@iotexpert.com) your real address and Ill send you development kit for pointing out my error.

Alan