You are here

RXBERR IRQ | Cypress Semiconductor


Summary: 3 Replies, Latest post by csai on 06 Aug 2009 10:29 AM PDT
Verified Answers: 0
Last post
Log in to post new comments.
allene2's picture
2 posts


I'm currently working on a Analog Devices Blackfin interfacing with a CYRF6936. I've written the driver to mimic the WirelessUSB LP Driver 1.4 for Cypress PSoCs as closely as possible, but it's unstable. After several seconds of transmitting and receiving, the RXBERR IRQ is asserted, and I can't get it to de-assert. Reading the TX and RX IRQ_STATUS registers doesn't seem to clear it, so my interrupt keeps on firing continuously. The datasheet says "this flag is cleared when RX GO is set and a SOP is received," but this is happening during a period of transmission, and the other end isn't going to be transmitting anything because it's waiting for a packet.

How do I get RXBERR IRQ to de-assert so my ISR stops firing?

klausgr's picture
1 post

try not enabling this interrupt to be present on IRQ pin, rather just examine by reading status register if/when necessary

Stub for 16562373's picture
13 posts

Receive Buffer Error Interrupt Status. This IRQ is triggered in one of two ways: (1) When the receive buffer is empty and there

is an attempt to read data (2) When the receive buffer is full and more data is received; this flag is cleared when RX GO is set

and a SOP is received. These are the only ways by which this register gets set. This is a read only register. You will not be able to write to this register. Once you read it gets cleared



csai's picture
Cypress Employee
32 posts


You are right .This are the only two ways where you can expect an interrupt and get the RXBERR IRQ bit set.



Log in to post new comments.