PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
See: https://sourceforge.net/projects/mecrisp/files/Cypress/
With this FORTH-pagage it is possible to test all C-applications interactively without debugger. The Kernel have integrated an interpreter and compiler.
The Compiler is extendabel in FORTH itself. The porting for the PSoC 6 is also planned.
If you would like to know more about FORTH, you will find the classic Starting-FORTH and Thinking-FORTH by Leo Brodie:
http://thinking-forth.sourceforge.net/
The Definition of ANS FORTH you can find here: http://lars.nocrew.org/dpans/dpans.htm
If you want to know more about Mecrisp-Stellaris you are right here:
https://www.forth-ev.de/filemgmt_data/files/4d2015-arm.pdf
Have fun
Klaus
Show LessI'm just trying to port the examples to PsocCreator 4.,2 and CYBLE-224110-00.
building bootloader is fine, but bootloadable will not link.
ERROR: address 0x241a0 of ...\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.text' is not within region `rom'
ERROR: ...\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.eh_frame' will not fit in region `rom'
ERROR: address 0x241a0 of ..\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.text' is not within region `rom'
ERROR: address 0x241a0 of ...\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.text' is not within region `rom'
ERROR: section .cyloadablemeta loaded at [0001ffc0,0001ffff] overlaps section .cybootloader loaded at [00000000,0001ffff]
ERROR: region `rom' overflowed by 0 bytes
collect2.exe: error: ld returned 1 exit status
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
Bootloader size is (38.4%), so I don't think I've overflowed.
I can't seem to find a memory map for the device, but don't see why the linker would make this mistake.
Workspace is attached. Thanks.
Show LessDear Community Team,
Please find attached project with SCB block for external EEPROM use internal slave I2C block.
The issue we are facing is that when we build this file with SCB block component version 1.2 project gets built correctly. But when we update that component to version 4.0 (latest) . The same program shows 13 critical error and does not get built.
Please suggest us necessary corrections/changes so that we can use latest version 4.0 of SCB block.
Best Regards,
Pavan.
Show LessMr. E. Pratt,
Thanks for taking the time to answer my question. I haven't had the time to try adding the uart_sleep and wake commands yet. What I did was change the code to use the SW UART, and that is working. I am now having problems with current draw through the SPI bus during PSOC deep sleep mode. If I disconnect the SPI MOSI and SClK, from PSOC to the slave, then the excess current goes away. So, I think I might try using the sleep and awake commands for the SPI to see if that helps.
Jeff
Sent from my iPad
Show LessI have an application where I want to use a single CYBLE-222014-01 to pair to two peripherals (also using CYBLE-222014-01) at the same time. BLE allows a central device to be paired with several peripherals but cant seem to get these modules to do so. It pairs with one but will not pair with second. Any help will be appreciated.
Show LessHi All,
I have run this example program called PSOC 4200M WDT LONG DEEP SLEEP from the following link:
http://www.cypress.com/blog/technical/psoc-4200m-wdt-long-deep-sleep
In this program, WDT0 and WDT1 are cascaded. I would like to know if the maximum delay that can be achieved is 32768 / 3600 =~ 9 hours.
Shouldn't this delay be the same as a 32-bit counter [WDT2], which goes for more than 19 hours?
Thanks,
Andrew Collins
Show LessHi,
I am implementing a simple USB command response interface for the PsoC 4 board I designed. I have it working but only through a nasty workaround.
In the CyUSB,NET document it states that ReadInput() will indefinitely hang until a input report is received. I immediately noted that it
does not hang but simply reports a packet of all zeroes. To make it work I had to add a Thread sleep of 16 or greater ms after the WriteOutput() function
sends a command. My device has a generic HID interface with 8 byte packets. This fix is problematic because of varying times for the device
to send it's response. Sometimes, I have to wait 32, 48 or even 64ms to receive a valid response.
Why does ReadInput() not block as stated ? Also, is there another function I can call to guarantee the response packet has been received before I post
a ReadInput() ? I noticed there is a WaitForXfer function in the EndPoint class hierarchy. But nothing like that for CyHIDDevice.
Regards,
Chuck
Show LessThe information below is for those who would like to enable and disable a BLE Service and/or an associated Characteristic (value), and possible Characteristic Configuration (e.g. for Notify), using the Cypress BLE API functions CyBle_GattsEnableAttribute() and CyBle_GattsDisableAttribute():
The defined constants below are as generated by Cypress in BLE_custom.h for a Custom Service having a Custom Characteristic (value) and a Custom Characteristic Configuration, with no Custom Descriptor:
#define CYBLE_CUSTOM_SERVICE_SERVICE_HANDLE (0x000Cu) /* Handle of Custom Service service */
#define CYBLE_CUSTOM_SERVICE_CUSTOM_CHARACTERISTIC_CHAR_HANDLE (0x000Eu) /* Handle of Custom Characteristic characteristic */
#define CYBLE_CUSTOM_SERVICE_CUSTOM_CHARACTERISTIC_CUSTOM_CHARACTERISTIC_CONFIGURATION_DESC_HANDLE (0x000Fu) /* Handle of Custom Characteristic Configuration descriptor */
A Service is enabled/disabled by utilizing the Service Handle (e.g. CYBLE_CUSTOM_SERVICE_SERVICE_HANDLE) with the functions CyBle_GattsEnableAttribute() and CyBle_GattsDisableAttribute().
However, to enable/disable only a Characteristic (of a Service), the required "Characteristic Declaration Handle" is produced by subtracting 1 from the "Characteristic Value Handle" (e.g. CYBLE_CUSTOM_SERVICE_CUSTOM_CHARACTERISTIC_CHAR_HANDLE) and any Characteristic Configuration (e.g. handle of CYBLE_CUSTOM_SERVICE_CUSTOM_CHARACTERISTIC_CUSTOM_CHARACTERISTIC_CONFIGURATION_DESC_HANDLE) associated with that Characteristic Value will also be enabled/disabled when calling CyBle_GattsEnableAttribute() and CyBle_GattsDisableAttribute() with the "Characteristic Declaration Handle".
Therefore, for the defined constants generated by Cypress above, the entire Service (and Characteristics) is enabled/disabled by calling CyBle_GattsEnableAttribute()/CyBle_GattsDisableAttribute() with the handle CYBLE_CUSTOM_SERVICE_SERVICE_HANDLE.
The Service Characteristic (value) and associated Characteristic Configuration is enabled/disabled by calling CyBle_GattsEnableAttribute()/CyBle_GattsDisableAttribute() with a handle value of CYBLE_CUSTOM_SERVICE_CUSTOM_CHARACTERISTIC_CHAR_HANDLE - 1 (e.g. 0x000Eu - 1 = 0x000Du) which is not defined anywhere by Cypress.
Show LessHi All:
About the Linker Script File for gcc,I have some question to ask:
1:
what the "NOLOAD" and the "alignment" is used for and how can I set the size of the custom section?
2: If the a variable of type const must be place in the section of " .rodata" or not? Can I place a variable of type const in the section of the custom by myself?
Hello,
I don't know what is the problem, something linked with the security policy, because when i disable strict pairing it work :
I tried to debug it with CySmart but pairing works with the key..
Do you have any idea ? I didn't see something related with that in the update list ...
Thanks.
Regards,
Show Less