OK, I'm hoping someone can help me resolve this, because its driving me nuts!!
Short story is I've had some problems with some hardware I designed using a PSoC4 BLE chip, and the problem stems from the start up delay from when the chip first gets a clean 3.3V supply and when things start to kick off in software. There seems to be a 500msec delay between these two events, which is causing issues with my hardware operation.
To try to get to the bottom of why this is, I tried paring the code right back. Still seeing the delay
Then I wrote a very simple pin-toggling program to eliminate everything else - still seeing the delay.
I then programmed one of the Cypress BLE modules with my code to eliminate my hardware as being the issue - still seeing the delay!
I've attached my code here, in the hope someone can look at it and go "oh, you're doing this wrong - that's why you've got the 500msec delay at start up". I've also included a screen dump from my scope showing the 3.3V rail starting up (yellow trace) and my pin toggle kicking into action (blue trace) showing the 500msec delay I'm referring to.
The weird thing is I have some other code that drives some additional hardware, and this isn't showing the issue with the software I developed for that. However, if I load up the simple pin toggle code, it starts showing the 500msec delay, so there is something weird going on in my software set up that I can't seem to get to the bottom of.
I've tried updating PSoC Creator to the latest version, and updating the firmware on my development kit, but this hasn't improved the situation at all :-(
Anyone got any ideas?