List of known bugs/issues

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

List of known bugs/issues

1,155 Views
CorderBollie
Contributor II

Hello.

Chasing known bugs and issues is an unpleasant sensation.

Is there a list of known bugs and issues for the actual version of MQX including RTCS?

Tags (3)
0 Kudos
3 Replies

646 Views
soledad
NXP Employee
NXP Employee

Hi CorderBollie,

You can find the known issues and limitations in the MQX Release notes chapter 5.


Have a great day,
Sol

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

646 Views
gfinlay56
Contributor II

It would be much desired to have a sanitized MQX BSP and PSP device driver bug fix report (e.g. Bugzilla or JIRA or equivalent) which identifies fixed issues which Freescale customers for MQX should be aware. The release notes are just not a comprehensive coverage of all code changes and driver fixes. If in doubt, we try to compare the code between different versions of MQX as the ultimate source for potential bug fixes or improvements, but this is time consuming.

I suspect that there are a lot of device driver bug fixes labelled "ENGR00xxxxxx" or "MQX-nnnn" between MQX 3.8 and MQX 4.1 for Kinetis which are not included in the release notes, but are nonetheless very important for us since we need to continue using MQX 3.8 (until such time as the updated AR4100 Atheros stack from Qualcomm as well as the OTG version of the USB stack are released with MQX 4.1 or higher). We would like to understand what issues have been fixed so that we don't waste unnecessary time tracking down MQX bugs that have already been fixed in later versions.

A couple of good examples:

1. We wasted a lot of time trying to find out why our UART TX FIFO wasn't draining properly until we saw this email thread on the

    Freescale community forum which identified a known issue with the Kinetis MQX serial UART driver:

     https://community.freescale.com/message/478244#478244

     The serl_pol_kuart.c serial driver for Kinetis contained a problem with _kuart_polled_ioctl() for the

     IO_IOCTL_SERIAL_WAIT_FOR_TC command. In this case, there were missing parentheses to explicitly override

     the default operator precedence to make sure the bit mask "&" is done before the "!".

     Old code in MQX 3.8:

          while( !sci_ptr->S1 & UART_S1_TC_MASK )

             { };

     New code in MQX 4.1:

          while( ! ( sci_ptr->S1 & UART_S1_TC_MASK ) )

             { };

2. In MQX 4.1, the lwgpio driver contains a couple of fixes to the lwgpio driver from MQX 3.8.  There is nothing in the release notes identifying what issue this fixes!

   Old code in MQX 3.8 for lwgpio_set_value() (I suspect this is an issue with "write one to clear" register bits):

       if (out_value == LWGPIO_VALUE_LOW) {

           handle->gpio_ptr->PDOR &= ~handle->pinmask;

       }

       else if (out_value == LWGPIO_VALUE_HIGH) {

           handle->gpio_ptr->PDOR |= handle->pinmask;

       }

   New code in MQX 4.1 for lwgpio_set_value():

       if (out_value == LWGPIO_VALUE_LOW) {

           handle->gpio_ptr->PCOR = handle->pinmask;

       }

       else if (out_value == LWGPIO_VALUE_HIGH) {

           handle->gpio_ptr->PSOR = handle->pinmask;

       }

   Old code in MQX 3.8 for  lwgpio_int_init():

        handle->flags |= LWGPIO_INT_MODE(0x08 | mode & 0x07); /* see PCR_IRQC register field definition */

   New code in MQX 4.1 for  lwgpio_int_init()

        handle->flags |= LWGPIO_INT_MODE(0x08 | (mode & 0x07)); /* see PCR_IRQC register field definition */

Is there any possibility of getting a more comprehensive list of MQX BSP or PSP device driver fixes (including items not found in release notes)?

Regards,

Gord Finlay

0 Kudos

646 Views
CorderBollie
Contributor II

OK this relates to issues but what about bugs?

To be more precise, is there some kind of bug tracking system that can be used by the community to keep informed about bugs in new MQX releases?

If I look into the threads here it is often the case that someone chases bugs in MQX, asks questions and gets the answer that it is a 'known issue'. However these issues are not in the MQX release notes.

0 Kudos