This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RF430CL330H: Stack Error with iOS 16

Part Number: RF430CL330H

After Apple has updated to iOS 14, the Problem was fixed. Unfortunately with iOS 16 we have again the Issue that the RF430CL330 can not be opened for writing. When using an iPhone 8 or newer we are getting a Stack Error in our iOS App. With my iPhone 7 and iOS 15.7.2 (iPhone will not be updated to iOS 16) everything works fine. Do you have an Idea on this Issue?

Kind reagrds 

Michael

  • Hello Customer, thank you for your question and interest in our products.

    The forum support of this product has been reduced to first reference our existing documentation and collateral. TI does not have plans to stop production or place the device into a “Not Recommended for New Design” status, we genuinely feel most questions on these devices can be answered by reviewing existing collateral and previous questions asked. Please feel free to continue to use this device as you see fit for your applications. For support, please take a look to the “Similar Topics” section at the lower right of the thread page. In addition, please consult the existing collateral in the “Technical Documentation” section of the RF430CL330H product web page along with the Frequently Asked Question document. Alternatively, you can use the search engine of your choice to look for related E2E threads. With each of these resources we believe it will help with your question.

  • Dear Andreas,

    Thanks for your honest answer, For us it means to look for an other sollution and we would not recommend it for use in new designs. 

    kind regards

    Michael

  • Hello Michael,

    the RF430CL330H is a fixed function device with its firmware in ROM. So from IC perspective there is no update possible. The only advice I can give is to analyze the stack error for more detailed symptoms, such as if the error was caused from the SPI or I2C communication, from the data format or from NFC protocol. Then I would check if some modification in the operating mode is possible.

    Best regards,

    Andreas.