I am trying to create a Monostable of 300mS than is triggered every second. It was easy enough when I worked with a 16 bit counter because a PWM count...
I am trying to create a Monostable of 300mS than is triggered every second. It was easy enough when I worked with a 16 bit counter because a PWM counter (ms_Counter) with a period of 10000 (with a clock of 10KHz) and a Compare setting of 3000 was the perfect solution. Unfortunately I needed greater resolution for the period and since the component can only be configured for 16 bits, I went to a 24bit counter with a clock of 1MHz and a Period of 1000000 (OneSecCounter)which generated 1 Hz. I tried to get it to trigger (using the reload pin) a PWM counter with a period of 65000 and the Compare remained at 3000. I tried to get the TC of the 24 bit counter to reload the PWM counter as you can see in the attached drawing, but the monostable pulse occurred at a far longer period, perhaps the 65000 which would suggest that the reload does not work the way I think. I also tried the period at 4000 and the output was much faster than the desired 1 second.
According to the datasheet "For all devices, except PSoC 4000, PSoC 4100, PSoC 4200, it should only be used when the counter is not running.", so it seems that I can activate the Reload when it is running. I found the following in the data sheet a little confusing "In up and up/down counting modes, the counter is initialized with “0” (for PSoC 4000, PSoC 4100, PSoC 4200 devices).". Does that mean the reload should be active low? I tried both ways but it made no difference .
In the schematic you can see a divide by 2 D-FF to prove that the OneSecCounter is working. I also include the register settings
Does anyone have any idea what I can do generate the monostable pulse? Any help would be much appreciated!
because of supplier's stock shortages and too long lead time we are forced to replace the existing CY8C4247AZI-L423 MCU part number with CY8C4247A...
because of supplier's stock shortages and too long lead time we are forced to replace the existing CY8C4247AZI-L423 MCU part number with CY8C4247AZA-M483 which has an acceptable lead time. It is the only part number that is pin-compatible and has the minimum memory and peripheral requirements that we are looking for. We also check the build of existing PSOC Creator projects with new MCU selected. The compilation doesn't report any errors. We are also aware that the new MCU have fewer UDB blocks and PLLs, but it seems to be enough for our needs.
I would just like to double-check with you if there are any other details that we should take care of before purchasing the new MCU part number. Does anyone have any concerns about replacing the CY8C4247AZI-L423 MCU with a pin-compatible CY8C4247AZA-M483? Pin compatibility and memory size are mandatory.