![]() THAT had me looking at PSoC in a better light. Inside of 40 minutes the Cypress Engineer had me create a usable BLE link and I understood what was going on under the hood. It did not go well, but it was more me this time, but the kits went back up on the shelf.(Side note, I was just getting started in only programming in C at teh time)Ībout four months ago the rep sent me an invitation to another seminar on PSoC4BLE, stay for the whole thing and you get to keep the Pioneer kit. He brought over a CY8KIT-030 and a CY8KIT-025 and said take these for a ride. I was talking to the local Cypress rep about how I might give Cypress another chance but I was not so sure the old gear would be worth the effort. Anytime I would hear another designer complain about how diffucult the PSoC is only fueled the "Do Not Bother" engine.Ībout a year and a half ago I was talking to another designer about the PSoC and he said again too much trouble. I said the hell with them all and sat down on my own to try to teach it to myself, but with no one to check what I was doing, I finally said screw it and went back to the way I was doing things. What little local support there was became non-existent and the internet was still in it's infantcy so no place like this. Went to the few introductory seminars to get it figured out, and once the folks that were running the show found that I only programmed in assembler one of them stopped just short of telling me not to bother comming back until I could program in C, which really pi$$ed me off. I looked at the user interface for PSoC designer and shook my head and said WTH. SO I went and bought an ExpressEval Kit(still have it) and a bunch of other PSoC mini boards and the lot and went at it. 'Bad Experiences" may have been a poor choice of words.īAck in the early 2000's it was suggested to me that I look at teh PSoC since I do a lot of Industrial Process Control work. This makes a contributor's life easier, just downloading and open the project, getting help from the IDE, easy checking of component versions and, and, and. Best practice is always to post your complete project, so that we all can have a look at all of your settings? To do so, useĬreator->File->Create Workspace Bundle (minimal) There is no button for keeping indentations of source-text, blame the forum software. PutArray() accepts any data-bytes(NULL as well) and relies on the given count-parameter telling how many bytes to transfer.īoth functions are "Blocking", which in this case means that the function will wait for room in the buffer and only returns after all bytes have been stored in the buffer. ![]() PutString() Transfers a null-terminated string into the buffer (without the NULL) and ![]() It fetches the next character from the buffer and puts it into the transmit-register of the UART. Is there a radio button to put source code in to keep indentation and formatting?įor UART_Putstring() and _PutArray() the interrupt is needed. * CyGlobalIntEnable */ /* Uncomment this line to enable global interrupts. * Place your initialization/startup code here (e.g. I thought is may have been the TX buffer, so I increased it to 32 bytes, but that did not fix it. Trying to output a 'message' string with the uart, but I only get the first six bytes and then it goes silent. AIROC™ Wi-Fi and Wi-Fi Bluetooth Combos. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |