cc1310 + TI 15.4 二进制文件 导致 串口无法正常使用

user5153918 说：

第一个版本 烧录运行中 串口无法正常打印和接收。

两个版本在串口相关基础代码和使用代码无任何区别。

说明串口部分没问题，第一个版本有问题，是代码的问题，检查下逻辑是否有问题

单步运行看看是否执行了你所调用的函数
// -----------------------------------------------------------------------------
//! \brief      This callback is invoked on Read completion of readSize/receive
//!             timeout
//!
//! \param[in]  handle - handle to the UART port
//! \param[in]  ptr    - pointer to buffer to read data into
//! \param[in]  size   - size of the data
//!
//! \return     void
// -----------------------------------------------------------------------------
static void NPITLUART_readCallBack(UART_Handle handle, void *ptr, size_t size)

两个版本Release出来的文件内容完全一样  区别在于collector.c 中函数Uart_ReadCallback  在处理串口已读字符时调用了一个外部处理函数。

执行中会在

/* Allocate message buffer space */
macStackInitParams_t *pMsg = (macStackInitParams_t *)OsalPort_msgAllocate(
sizeof(macStackInitParams_t));

中报错，进入  Main_assertHandler。

但是单步可以过去。。。。。。。。。。过去后在执行  也会报错。

错误现场如下：

TI大神！

          ti15.4协议栈协调器 启动阶段，执行到  ApiMac_init时，分配地址空检报错，

uint8_t * OsalPort_msgAllocate(uint16_t len )
{
    uint8_t *pMsg = NULL;
    OsalPort_MsgHdr* pHdr;

    if ( len == 0 )
        return ( NULL );

    pHdr = (OsalPort_MsgHdr*) OsalPort_malloc( len + sizeof( OsalPort_MsgHdr ) );

    if ( pHdr )
    {
        pHdr->next = NULL;
        pHdr->len = len;
        pHdr->dest_id = OsalPort_TASK_NO_TASK;

        pMsg = (uint8_t *)((uint8_t *)pHdr + sizeof( OsalPort_MsgHdr ));
    }

    return pMsg;
}

估计是空间分配不够了，请问TI大神，这个空检配置在哪里调整呢？

空间受RAM限制，具体报什么错？修改了哪些程序


/*********************************************************************
 * @fn      OsalPort_msgAllocate
 *
 * @brief
 *
 *    This function is called by a task to allocate a message buffer
 *    into which the task will encode the particular message it wishes
 *    to send.  This common buffer scheme is used to strictly limit the
 *    creation of message buffers within the system due to RAM size
 *    limitations on the microprocessor.   Note that all message buffers
 *    are a fixed size (at least initially).  The parameter len is kept
 *    in case a message pool with varying fixed message sizes is later
 *    created (for example, a pool of message buffers of size LARGE,
 *    MEDIUM and SMALL could be maintained and allocated based on request
 *    from the tasks).
 *
 *
 * @param   uint8_t len  - wanted buffer length
 *
 *
 * @return  pointer to allocated buffer or NULL if allocation failed.
 */
uint8_t * OsalPort_msgAllocate(uint16_t len )