It seems odd to me that with the Kinetis processors, PE and the CAN module can set individual receive masks for each mailbox, but looking into the FLEXCAN module in MQX, there is no interface for individual mailbox masks.
One more note about MPC8308 port.
I saw that SDRAM was separated into large cacheble and non-cachable areas with additional MMU.
I understood that the reason is troubles with TSEC and DMA ring descriptors and buffers in cachable memory.
THE SOLUTION IS to enable bus snooping (in ATTR register for receiver...) as Linux driver does!
Hi,
I faced and solved some problems between task priorities and task template list, and I think It would be interesting to add the related info to the docs. See :
My current wishes are:
+ DMA support for UARTs (see https://community.freescale.com/message/115446#115446
+ out-of-the-box USB composite device support (see USB composite device)
A few words about new MPC8308 MQX port.
In init_bsp.c module in decrementer initialization branch hasn't been set value to:
kernel_data->TIMER_HW_REFERENCE = timer_preload;
so strange sheduling occurs, but in GPT branch was set.
Also some funny usage of:
_time_set_hwtick_function(_e300_decrementer_get_hwticks, (pointer)timer_preload);
but "timer_preload" is a variable not a function. Also found in MPC51525 port.
Found a bug in kflexcan.c that causes it to not function when using CAN0.
**************************************************************************
*
* $FileName: kflexcan.c$
* $Version : 3.6.3.0$
* $Date : Nov-5-2010$
*
* Comments:
*
* Revision History:
* Date Version Changes
* --------- ------- -------
* June 10/04 2.50 Initial version
*
*END************************************************************************/
Line 343 of is:
while((CAN1_MCR & CAN_MCR_FRZACK_MASK) == 0) {}
Should be:
while((can_reg_ptr->MCR & CAN_MCR_FRZACK_MASK) == 0) {}
Organize better.
Or maybe not obvious to me ...
Be able to look at posts filtered by processor, CW version MQX version.
Remove "flakeyness" in MQX & CW. i've used uC/OS II, HCS12 & CW - pretty solid.
Moving to Coldfire, so planning on using CW & MQX, but .... too much confusion!
KISS
Please.
Is this where we should put requests for updates?
We use PTJ7 as a GPIO (MCF52259) which requires modification of gpio_init.c. is it possible to have this as a standard option in user_config.h so we dont have to modifiy bsp?
I have done the following modification at the bottom of _bsp_enet_io_init()
...
// mcf5225_ptr->GPIO.PTJPAR = 0xFF;
// Added this to allow us to use the 'un-used' pin
#ifdef USE_PTJ7_AS_GPIO
#warning PTJ7 will be left as GPIO when ENET IO is loaded / configured / reset
mcf5225_ptr->GPIO.PTJPAR = 0x7F;
#else
mcf5225_ptr->GPIO.PTJPAR = 0xFF;
#endif
...
HI every body.
I have just started with Freescale MQX. I ´d like to know if there are some key suggestions about the use(or visibility) of MQX variables that lead to a no execive use of onchip memory resources and or help to prevent further task´s stack overlap.
Thanks for your ideas
I have a suggestion to tell you and your company.
The MQX RTOS of Freescale is a really powerful Software. The efficiency of MQX RTOS is really good. But freescale didn't provide a file about architecture of MQX RTOS. And Freescale Did not provide a seminar in detail. There are only MQX RTOS UG and other API RM. But they didn't write all the defination of functions and micros in detail. Just like setjmp(b) and longjmp(b,n) that are in my problems.
Would Freescale semiconductor provide a web seminar about introduction of MQX RTOS in detail? Or Freescale semiconductor may provide a file to introduce the architecture of the MQX RTOS? I think that we don't need a small introduction in five minutes. We really need a fully introduction about the software in detail. I consider that this is a only way to solve any weird problems, just like my problem.
And This is a only way to introduce the powerful MCU to all engineer.
Freescale also have already provided a fully seminar for CMX USB lite Stack in detail.
I think that Freescale also do a same seminar or e-class for customers.
Thank you for your Help.
Sincerely Yours
fish_yu
Just a little feedback.
I think having a boot loader example with MQX is key. The example should have a simple way of getting data from say a comm port or just from the MRAM table then varifiying the flash for a valid operatig system before booting to that MQX image.
I think this would be a better example than HVAC, or, to include this with the HVAC demo so you can do it via the HTTP interface would be great!
I cannot think of a project that would deploy something like MQX without being able to remotely upload new software.
We are currently writing a remote boot loader that works via GPRS.
I totally support the Bootloader demo!
Please include it in the next release
Hi,
Currently I am working on MCF5213 controller ,For my application I am serching for best RTOS which fulfilles my requirement,
So I serach MQX RTOS which is freeware with Silab controller,But I have a confusion in my mind wheather MQx is fully supporting MCF 5213 controller which includes UART,SPI,I2C,GPIO,Rapid GPIO and other ports, So can any one suggest me wheather I can go with MQX for MCF5213