深海游弋的鱼 – 第 89 页 – 智障儿童欢乐多

Ti CC1310 SDK版本兼容

在开发Ti CC1310应用的时候遇到了SDK版本兼容问题。早期的应用都是从SDK 1.60版本的例子中修改得来的，最近在升级到SDK 2.x版本的时候遇到了编译不通过的问题。主要是某些变量名的定义改变了。

但是，翻遍了代码也没找打一个SDK版本宏。

于是只能通过ti/devices/cc13x0/driverlib/driverlib_release.h文件里面的DRIVERLIB_RELEASE_BUILD的版本号来进行区分，根据数字的不同来使用不同的代码，例子如下：

#include <ti/devices/cc13x0/driverlib/driverlib_release.h>

/*SDK 1_60_00_21*/
#if (DRIVERLIB_RELEASE_BUILD <= 50218)
const DisplaySharp_HWAttrs displaySharpHWattrs = {
    .spiIndex    = CC1310_LAUNCHXL_SPI0,
    .csPin       = CC1310_LAUNCHXL_LCD_CS,
    .extcominPin = CC1310_LAUNCHXL_LCD_EXTCOMIN,
    .powerPin    = CC1310_LAUNCHXL_LCD_POWER,
    .enablePin   = CC1310_LAUNCHXL_LCD_ENABLE,
    .pixelWidth  = BOARD_DISPLAY_SHARP_SIZE,
    .pixelHeight = BOARD_DISPLAY_SHARP_SIZE,
    .displayBuf  = sharpDisplayBuf,
};
#else /*SDK 2_10_02_10*/
const DisplaySharp_HWAttrsV1 displaySharpHWattrs = {
    .spiIndex    = CC1310_LAUNCHXL_SPI0,
    .csPin       = CC1310_LAUNCHXL_LCD_CS,
    .powerPin    = CC1310_LAUNCHXL_LCD_POWER,
    .enablePin   = CC1310_LAUNCHXL_LCD_ENABLE,
    .pixelWidth  = BOARD_DISPLAY_SHARP_SIZE,
    .pixelHeight = BOARD_DISPLAY_SHARP_SIZE,
    .displayBuf  = sharpDisplayBuf,
};
#endif

#include <ti/devices/cc13x0/driverlib/driverlib_release.h>

/*SDK 1_60_00_21*/

#if (DRIVERLIB_RELEASE_BUILD <= 50218)

const DisplaySharp_HWAttrs displaySharpHWattrs = {

.spiIndex = CC1310_LAUNCHXL_SPI0,

.csPin = CC1310_LAUNCHXL_LCD_CS,

.extcominPin = CC1310_LAUNCHXL_LCD_EXTCOMIN,

.powerPin = CC1310_LAUNCHXL_LCD_POWER,

.enablePin = CC1310_LAUNCHXL_LCD_ENABLE,

.pixelWidth = BOARD_DISPLAY_SHARP_SIZE,

.pixelHeight = BOARD_DISPLAY_SHARP_SIZE,

.displayBuf = sharpDisplayBuf,

};

#else /*SDK 2_10_02_10*/

const DisplaySharp_HWAttrsV1 displaySharpHWattrs = {

.spiIndex = CC1310_LAUNCHXL_SPI0,

.csPin = CC1310_LAUNCHXL_LCD_CS,

.powerPin = CC1310_LAUNCHXL_LCD_POWER,

.enablePin = CC1310_LAUNCHXL_LCD_ENABLE,

.pixelWidth = BOARD_DISPLAY_SHARP_SIZE,

.pixelHeight = BOARD_DISPLAY_SHARP_SIZE,

.displayBuf = sharpDisplayBuf,

};

#endif

/*
 *  =============================== RF Driver ===============================
 */
#include <ti/drivers/rf/RF.h>

/*SDK 1_60_00_21*/
#if (DRIVERLIB_RELEASE_BUILD <= 50218)
const RFCC26XX_HWAttrs RFCC26XX_hwAttrs = {
    .hwiCpe0Priority = ~0,
    .hwiHwPriority   = ~0,
    .swiCpe0Priority =  0,
    .swiHwPriority   =  0,
};
#else /*SDK 2_10_02_10*/
const RFCC26XX_HWAttrsV2 RFCC26XX_hwAttrs = {
    .hwiPriority        = ~0,       /* Lowest HWI priority */
    .swiPriority        = 0,        /* Lowest SWI priority */
    .xoscHfAlwaysNeeded = true,     /* Keep XOSC dependency while in stanby */
    .globalCallback     = NULL,     /* No board specific callback */
    .globalEventMask    = 0         /* No events subscribed to */
};
#endif

* =============================== RF Driver ===============================

#include <ti/drivers/rf/RF.h>

/*SDK 1_60_00_21*/

#if (DRIVERLIB_RELEASE_BUILD <= 50218)

const RFCC26XX_HWAttrs RFCC26XX_hwAttrs = {

.hwiCpe0Priority = ~0,

.hwiHwPriority = ~0,

.swiCpe0Priority = 0,

.swiHwPriority = 0,

};

#else /*SDK 2_10_02_10*/

const RFCC26XX_HWAttrsV2 RFCC26XX_hwAttrs = {

.hwiPriority = ~0, /* Lowest HWI priority */

.swiPriority = 0, /* Lowest SWI priority */

.xoscHfAlwaysNeeded = true, /* Keep XOSC dependency while in stanby */

.globalCallback = NULL, /* No board specific callback */

.globalEventMask = 0 /* No events subscribed to */

};

#endif

其他的就是动态链接库的位置不同，导致链接的时候报告找不到链接库，需要重新设置一下，或者简单的移除一些找不到的库即可，例子中并没有用到全部的链接库。

Code Composer Studio 8.2运行时对象查看器Runtime Object View (ROV)

Code Composer Studio 8.2提供的Runtime Object View (ROV)是一个非常好用的功能，能动态监视系统的运行情况。

该功能需要使用TI-RTOS的应用才可以正常使用。

下面是官方的参考文档：
继续阅读Code Composer Studio 8.2运行时对象查看器Runtime Object View (ROV)

卸载华为系统自带的百度输入法

百度作为中国互联网的一颗毒瘤，实在是需要远离。可惜华为系统自带的输入法恰恰就是百度的输入法。

继续阅读卸载华为系统自带的百度输入法

GCC支持在代码中对头文件是否存在的判断(__has_include)

我们在实际编写代码的时候，经常需要判断当前编译环境是否存在我们需要的头文件，如果不存在，则使用其他头文件代替。

以前这个操作都是通过外部的configure文件生成Makefile的时候指定。

最近的GCC已经增加了__has_include这个内置函数判断头文件是否存在。

这个功能最早是Clang实现的，现在GCC终于补上了这个功能。

例子如下：

#ifdef __has_include
#  if __has_include(<optional>)
#    include <optional>
#    define have_optional 1
#  elif __has_include(<experimental/optional>)
#    include <experimental/optional>
#    define have_optional 1
#    define experimental_optional
#  else
#    define have_optional 0
#  endif
#endif

#ifdef __has_include

# if __has_include(<optional>)

# include <optional>

# define have_optional 1

# elif __has_include(<experimental/optional>)

# include <experimental/optional>

# define have_optional 1

# define experimental_optional

# else

# define have_optional 0

# endif

#endif

Code Composer Studio 8.2.0.00007 ,GCC 5支持这个内置函数。

参考链接

解决Ti CC1310上I2C驱动能力不足(稳定性)问题

在使用Ti CC1310的硬件I2C与外部设备进行通信的时候，无法长时间稳定运行，尤其是平时的测试开发板，使用杜邦线连接的情况下。

同等情况下的SPI总线，一般不会发生此类问题，因此怀疑是GPIO管脚的驱动能力不足导致的。

我的工程是通过简单修改Ti CC1310 SDK自带的Code Composer Studio的例子工程而创建的，因此存在已经进行过默认配置的CC1310_LAUNCHXL.c，CC1310_LAUNCHXL.h这两个文件。用Code Composer Studio完全重新创建的工程，缺乏必要的默认配置。因此，我们还是建议根据Ti CC1310 SDK自带的例子进行修改，而不是完全从头创建工程。

我们研究I2C初始化GPIO管脚的代码在simplelink_cc13x0_sdk_2_30_00_20/source/ti/drivers/i2c/I2CCC26XX.c，相关的代码如下：

/*
 *  ======== I2CCC26XX_initIO ========
 *  This functions initializes the I2C IOs.
 *
 *  @pre    Function assumes that the I2C handle is pointing to a hardware
 *          module which has already been opened.
 */
static int I2CCC26XX_initIO(I2C_Handle handle, void *pinCfg) {
    I2CCC26XX_Object            *object;
    I2CCC26XX_HWAttrsV1 const  *hwAttrs;
    I2CCC26XX_I2CPinCfg         i2cPins;
    PIN_Config                  i2cPinTable[3];
    uint32_t i=0;

    /* Get the pointer to the object and hwAttrs */
    object = handle->object;
    hwAttrs = handle->hwAttrs;

    /* If the pinCfg pointer is NULL, use hwAttrs pins */
    if (pinCfg == NULL) {
        i2cPins.pinSDA = hwAttrs->sdaPin;
        i2cPins.pinSCL = hwAttrs->sclPin;
    } else {
        i2cPins.pinSDA = ((I2CCC26XX_I2CPinCfg *)pinCfg)->pinSDA;
        i2cPins.pinSCL = ((I2CCC26XX_I2CPinCfg *)pinCfg)->pinSCL;
    }

    /* Handle error */
    if(i2cPins.pinSDA == PIN_UNASSIGNED || i2cPins.pinSCL == PIN_UNASSIGNED) {
        return I2C_STATUS_ERROR;
    }
    /* Configure I2C pins SDA and SCL*/
    i2cPinTable[i++] = i2cPins.pinSDA | PIN_INPUT_EN | PIN_PULLUP | PIN_OPENDRAIN;
    i2cPinTable[i++] = i2cPins.pinSCL | PIN_INPUT_EN | PIN_PULLUP | PIN_OPENDRAIN;
    i2cPinTable[i++] = PIN_TERMINATE;
    /* Allocate pins*/
    object->hPin = PIN_open(&object->pinState, i2cPinTable);

    if (!object->hPin) {
        return I2C_STATUS_ERROR;
    }

    /* Set IO muxing for the UART pins */
    PINCC26XX_setMux(object->hPin, i2cPins.pinSDA, IOC_PORT_MCU_I2C_MSSDA);
    PINCC26XX_setMux(object->hPin, i2cPins.pinSCL, IOC_PORT_MCU_I2C_MSSCL);
    return I2C_STATUS_SUCCESS;
}

* ======== I2CCC26XX_initIO ========

* This functions initializes the I2C IOs.

* @pre Function assumes that the I2C handle is pointing to a hardware

* module which has already been opened.

static int I2CCC26XX_initIO(I2C_Handle handle, void *pinCfg) {

I2CCC26XX_Object *object;

I2CCC26XX_HWAttrsV1 const *hwAttrs;

I2CCC26XX_I2CPinCfg i2cPins;

PIN_Config i2cPinTable[3];

uint32_t i=0;

/* Get the pointer to the object and hwAttrs */

object = handle->object;

hwAttrs = handle->hwAttrs;

/* If the pinCfg pointer is NULL, use hwAttrs pins */

if (pinCfg == NULL) {

i2cPins.pinSDA = hwAttrs->sdaPin;

i2cPins.pinSCL = hwAttrs->sclPin;

} else {

i2cPins.pinSDA = ((I2CCC26XX_I2CPinCfg *)pinCfg)->pinSDA;

i2cPins.pinSCL = ((I2CCC26XX_I2CPinCfg *)pinCfg)->pinSCL;

}

/* Handle error */

if(i2cPins.pinSDA == PIN_UNASSIGNED || i2cPins.pinSCL == PIN_UNASSIGNED) {

return I2C_STATUS_ERROR;

}

/* Configure I2C pins SDA and SCL*/

i2cPinTable[i++] = i2cPins.pinSDA | PIN_INPUT_EN | PIN_PULLUP | PIN_OPENDRAIN;

i2cPinTable[i++] = i2cPins.pinSCL | PIN_INPUT_EN | PIN_PULLUP | PIN_OPENDRAIN;

i2cPinTable[i++] = PIN_TERMINATE;

/* Allocate pins*/

object->hPin = PIN_open(&object->pinState, i2cPinTable);

if (!object->hPin) {

return I2C_STATUS_ERROR;

}

/* Set IO muxing for the UART pins */

PINCC26XX_setMux(object->hPin, i2cPins.pinSDA, IOC_PORT_MCU_I2C_MSSDA);

PINCC26XX_setMux(object->hPin, i2cPins.pinSCL, IOC_PORT_MCU_I2C_MSSCL);

return I2C_STATUS_SUCCESS;

}

从上面的代码中，我们发现GPIO管脚的驱动能力没有设置，根据CC13x0, CC26x0 SimpleLink ™ Wireless MCU Technical Reference Manual中的介绍，我们发现，如果不设置，默认情况下是PIN_DRVSTR_MIN（< (*) Lowest drive strength）。这个驱动模式下，最省电，但是当有干扰存在的情况下，最容易导致出现错误。

查找Ti CC1310提供的I2C驱动程序，没有找到可以设置管脚驱动能力的接口。

网上有人通过直接修改Ti CC1310提供的I2C驱动程序，也就是simplelink_cc13x0_sdk_2_30_00_20/source/ti/drivers/i2c/I2CCC26XX.c里的初始化代码（见上面的代码段）增加驱动能力属性来实现这个功能。

但是这种修改方式不推荐，修改的侵入太强。

从GPIO的操作函数中，我们找到如下函数：

/** @brief Returns pin configuration
 *
 *  @param pinId    Pin ID
 *  @return  Current pin configuration as a device-independent #PIN_Config value
 *  @note    The pin ID is embedded in return value.
 *  @note    There is usually a device-specific version of this function that
 *           returns device-specific options
 *  @par Usage
 *       @code
 *       // Get config of pin 14 to be able to revert later
 *       myPinConfig = PIN_getConfig(PIN_ID(14));
 *       // ...
 *       // Lots of pin reconfigurations
 *       // ...
 *       // Restore previous configuration
 *       PIN_setConfig(hPins, PIN_BM_ALL, myPinConfig);
 *       @endcode
 */
extern PIN_Config PIN_getConfig(PIN_Id pinId);


/** @brief Sets complete pin configuration
 *
 *  @param handle  Handle provided by previous call to PIN_open()
 *  @param updateMask  Bitmask specifying which fields in cfg that should take
 *                 effect, the rest keep their current value.
 *  @param pinCfg  #PIN_Config entry with pin ID and pin configuration
 *  @return #PIN_SUCCESS if successful, else error code
 *  @par Usage
 *       @code
 *       // Set drive strength on pin 15
 *       PIN_setConfig(hPins, PIN_BM_DRVSTR, PIN_ID(15)|PIN_DRVSTR_MAX);
 *       @endcode
 */
extern PIN_Status PIN_setConfig(PIN_Handle handle, PIN_Config updateMask, PIN_Config pinCfg);

/** @brief Returns pin configuration

* @param pinId Pin ID

* @return Current pin configuration as a device-independent #PIN_Config value

* @note The pin ID is embedded in return value.

* @note There is usually a device-specific version of this function that

* returns device-specific options

* @par Usage

* @code

* // Get config of pin 14 to be able to revert later

* myPinConfig = PIN_getConfig(PIN_ID(14));

* // ...

* // Lots of pin reconfigurations

* // ...

* // Restore previous configuration

* PIN_setConfig(hPins, PIN_BM_ALL, myPinConfig);

* @endcode

extern PIN_Config PIN_getConfig(PIN_Id pinId);

/** @brief Sets complete pin configuration

* @param handle Handle provided by previous call to PIN_open()

* @param updateMask Bitmask specifying which fields in cfg that should take

* effect, the rest keep their current value.

* @param pinCfg #PIN_Config entry with pin ID and pin configuration

* @return #PIN_SUCCESS if successful, else error code

* @par Usage

* @code

* // Set drive strength on pin 15

* PIN_setConfig(hPins, PIN_BM_DRVSTR, PIN_ID(15)|PIN_DRVSTR_MAX);

* @endcode

extern PIN_Status PIN_setConfig(PIN_Handle handle, PIN_Config updateMask, PIN_Config pinCfg);

我们尝试从上层找到I2C驱动使用的GPIO管脚，然后调整其驱动能力。

/* I2C */
#define CC1310_LAUNCHXL_I2C0_SCL0            (IOID_5) 
#define CC1310_LAUNCHXL_I2C0_SDA0            (IOID_6)

/* I2C */

#define CC1310_LAUNCHXL_I2C0_SCL0 (IOID_5)

#define CC1310_LAUNCHXL_I2C0_SDA0 (IOID_6)

/*
 *  =============================== I2C ===============================
*/
#include <ti/drivers/I2C.h>
#include <ti/drivers/i2c/I2CCC26XX.h>

I2CCC26XX_Object i2cCC26xxObjects[CC1310_LAUNCHXL_I2CCOUNT];

const I2CCC26XX_HWAttrsV1 i2cCC26xxHWAttrs[CC1310_LAUNCHXL_I2CCOUNT] = {
    {
        .baseAddr    = I2C0_BASE,
        .powerMngrId = PowerCC26XX_PERIPH_I2C0,
        .intNum      = INT_I2C_IRQ,
        .intPriority = ~0,
        .swiPriority = 0,
        .sdaPin      = CC1310_LAUNCHXL_I2C0_SDA0,
        .sclPin      = CC1310_LAUNCHXL_I2C0_SCL0,
    }
};

const I2C_Config I2C_config[CC1310_LAUNCHXL_I2CCOUNT] = {
    {
        .fxnTablePtr = &I2CCC26XX_fxnTable,
        .object      = &i2cCC26xxObjects[CC1310_LAUNCHXL_I2C0],
        .hwAttrs     = &i2cCC26xxHWAttrs[CC1310_LAUNCHXL_I2C0]
    }
};

const uint_least8_t I2C_count = CC1310_LAUNCHXL_I2CCOUNT;

* =============================== I2C ===============================

#include <ti/drivers/I2C.h>

#include <ti/drivers/i2c/I2CCC26XX.h>

I2CCC26XX_Object i2cCC26xxObjects[CC1310_LAUNCHXL_I2CCOUNT];

const I2CCC26XX_HWAttrsV1 i2cCC26xxHWAttrs[CC1310_LAUNCHXL_I2CCOUNT] = {

{

.baseAddr = I2C0_BASE,

.powerMngrId = PowerCC26XX_PERIPH_I2C0,

.intNum = INT_I2C_IRQ,

.intPriority = ~0,

.swiPriority = 0,

.sdaPin = CC1310_LAUNCHXL_I2C0_SDA0,

.sclPin = CC1310_LAUNCHXL_I2C0_SCL0,

}

};

const I2C_Config I2C_config[CC1310_LAUNCHXL_I2CCOUNT] = {

{

.fxnTablePtr = &I2CCC26XX_fxnTable,

.object = &i2cCC26xxObjects[CC1310_LAUNCHXL_I2C0],

.hwAttrs = &i2cCC26xxHWAttrs[CC1310_LAUNCHXL_I2C0]

}

};

const uint_least8_t I2C_count = CC1310_LAUNCHXL_I2CCOUNT;

从上面我们看到I2C句柄的.object指针指向了I2CCC26XX_Object类型的结构体，这个结构体在simplelink_cc13x0_sdk_2_30_00_20/source/ti/drivers/i2c/I2CCC26XX.c里的static int I2CCC26XX_initIO(I2C_Handle handle, void *pinCfg)函数中被初始化，这个结构体记录了详细的GPIO操作句柄。

因此我们可以使用如下的代码对GPIO管脚的驱动能力进行调整：

#include <ti/drivers/I2C.h>
#include <ti/drivers/i2c/I2CCC26XX.h>
#include "CC1310_LAUNCHXL.h"

static I2C_Handle initI2c(void) {
    I2C_Params      i2cParams;
    /* Create I2C for usage */
    I2C_Params_init(&i2cParams);
    i2cParams.bitRate = I2C_400kHz;
    i2cParams.transferMode = I2C_MODE_BLOCKING;

    I2C_Handle i2c = I2C_open(Board_I2C_TMP, &i2cParams);
    if (NULL == i2c) {
        return NULL;
    }

    /* Change I2C Pin Drive Strength*/
    /*CC1310_LAUNCHXL.c I2CCC26XX_Object i2cCC26xxObjects[CC1310_LAUNCHXL_I2CCOUNT];*/
    I2CCC26XX_Object* i2cObj = i2c->object;
    if (NULL != i2cObj) {
        PIN_Config pinCfg = PIN_getConfig(PIN_ID(CC1310_LAUNCHXL_I2C0_SDA0));
        PIN_Status status = PIN_setConfig(i2cObj->hPin, PIN_BM_ALL, pinCfg | PIN_DRVSTR_MAX);
        if (PIN_SUCCESS != status){
            I2C_close(i2c);
            return NULL;
        }
        pinCfg = PIN_getConfig(PIN_ID(CC1310_LAUNCHXL_I2C0_SCL0));
        status = PIN_setConfig(i2cObj->hPin, PIN_BM_ALL, pinCfg | PIN_DRVSTR_MAX);
        if (PIN_SUCCESS != status){
            I2C_close(handle->i2c);
            return NULL;
        }
    }
    return i2c;
}

#include <ti/drivers/I2C.h>

#include <ti/drivers/i2c/I2CCC26XX.h>

#include "CC1310_LAUNCHXL.h"

static I2C_Handle initI2c(void) {

I2C_Params i2cParams;

/* Create I2C for usage */

I2C_Params_init(&i2cParams);

i2cParams.bitRate = I2C_400kHz;

i2cParams.transferMode = I2C_MODE_BLOCKING;

I2C_Handle i2c = I2C_open(Board_I2C_TMP, &i2cParams);

if (NULL == i2c) {

return NULL;

}

/* Change I2C Pin Drive Strength*/

/*CC1310_LAUNCHXL.c I2CCC26XX_Object i2cCC26xxObjects[CC1310_LAUNCHXL_I2CCOUNT];*/

I2CCC26XX_Object* i2cObj = i2c->object;

if (NULL != i2cObj) {

PIN_Config pinCfg = PIN_getConfig(PIN_ID(CC1310_LAUNCHXL_I2C0_SDA0));

PIN_Status status = PIN_setConfig(i2cObj->hPin, PIN_BM_ALL, pinCfg | PIN_DRVSTR_MAX);

if (PIN_SUCCESS != status){

I2C_close(i2c);

return NULL;

}

pinCfg = PIN_getConfig(PIN_ID(CC1310_LAUNCHXL_I2C0_SCL0));

status = PIN_setConfig(i2cObj->hPin, PIN_BM_ALL, pinCfg | PIN_DRVSTR_MAX);

if (PIN_SUCCESS != status){

I2C_close(handle->i2c);

return NULL;

}

return i2c;

}

参考链接

macOS Mojave(10.14)安装AX88179(USB 3.0 有线网卡)驱动程序

自己的mac book pro在升级到macOS Mojave(10.14)之后，无法识别USB 3.0有线网卡。

使用如下命令，查询网卡的设备类型：

$ system_profiler SPUSBDataType

1	$ system_profiler SPUSBDataType

然后下载驱动安装才可以。

官方下载地址：
AX88179 Drivers Download

本站下载地址：
AX88179_178A_macintosh_Driver_Installer_v2.13.0

sql-按条件统计非重复值，count(distinct case when)使用

背景

项目中，遇到一个统计需求，从某张表中按照条件分别统计。刚开始想到用union all的写法，太臃肿，后来使用count(distinct case when)解决此问题

count

数据统计中，count出现最频繁

最简单的用法

select count(*) from table where ....

select count(distinct xx) from table where ...

但最简单的用法也有其深刻的地方，比如这里其实有3种写法，count(1)、count(*)、count(字段)，它们有什么区别呢？

count(1) 和 count(*)

count(1)和count(*)差别不大，使用count(*)时，sql会帮你自动优化，指定到最快的字段。所以推荐使用count(*)

count(*) 和 count(字段)

count(*)会统计所有行数，count(字段)不会统计null值

count(case when)

条件统计，即对某个table分条件统计，比如表test_db，有一个字段user_id(可能重复), gender(man、women)，需要统计man和women的人数

可以使用where分别统计

select count(distinct user_id) as man_cnt from test_db where gender = 'man'

select count(distinct user_id) as women_cnt from test_db where gender = 'women'

也可以使用按条件统计

select count(distinct case gender = 'man' then user_id end) as man_cnt

, count(distinct case gender = 'women' then user_id end) as woman_cnt

from test_db

Raspberry Pi Zero W解决调试信息不足的问题（以libzmq-dev为例)

最近在参照树莓派实时系统下脚本语言的选择(应当使用Lua而不是Python) 调用调试lua-zmq的时候，发现使用PAIR模式进行线程之间通信，长时间运行后会出现死锁的情况。

当我们需要跟踪问题的时候，使用apt-get安装的版本缺乏必要的调试信息。

我们可以手工安装调试信息包，如下：

$ sudo apt install libzmq-dbg

# 系统默认的lua 5.1的符号信息使用如下命令安装
$ sudo apt-get install liblua5.1-0-dbg

# libreadline提供了多个版本（5,6,7），根据需要下载对应的版本
$ sudo apt-get install libreadline6-dbg

# sudo apt-get install search libtinfo* 根据返回的结果安装
$ sudo apt-get install libtinfo5-dbg

$ sudo apt install libzmq-dbg

# 系统默认的lua 5.1的符号信息使用如下命令安装

$ sudo apt-get install liblua5.1-0-dbg

# libreadline提供了多个版本（5,6,7），根据需要下载对应的版本

$ sudo apt-get install libreadline6-dbg

# sudo apt-get install search libtinfo* 根据返回的结果安装

$ sudo apt-get install libtinfo5-dbg

我们也可以从源代码重新编译一份，如下：

# 打开源代码的源
$ sudo sed -i "s/^#deb-src/deb-src/g" /etc/apt/sources.list

# 安装必要的编译工具
$ sudo apt-get install build-essential devscripts lintian

$ cd ~

# 下载源代码，此处不可sudo,否则后续操作会出现权限问题
$ apt-get source libzmq-dev

$ cd zeromq*/

# 安装依赖项
$ sudo apt-get install libpgm-dev

$ sudo apt-get install uuid-dev

$ debuild -us -uc -b

$ cd ..

$ sudo dpkg -i libzmq-dev*.deb

$ sudo dpkg -i libzmq-dbg*.deb

$ sudo ldconfig

# 打开源代码的源

$ sudo sed -i "s/^#deb-src/deb-src/g" /etc/apt/sources.list

# 安装必要的编译工具

$ sudo apt-get install build-essential devscripts lintian

$ cd ~

# 下载源代码，此处不可sudo,否则后续操作会出现权限问题

$ apt-get source libzmq-dev

$ cd zeromq*/

# 安装依赖项

$ sudo apt-get install libpgm-dev

$ sudo apt-get install uuid-dev

$ debuild -us -uc -b

$ cd ..

$ sudo dpkg -i libzmq-dev*.deb

$ sudo dpkg -i libzmq-dbg*.deb

$ sudo ldconfig

以上是针对Debian安装包来进行的处理，然而对于luarocks安装的插件来说，默认luarocks是不能编译调试版本的，此时就需要我们手工编译了。我们以lua-zmq为例子，参考如下：

$ sudo apt-get -y install cmake

$ git clone git://github.com/Neopallium/lua-zmq.git

$ git checkout v1.1

$ cd lua-zmq ; mkdir build ; cd build

$ cmake -DCMAKE_BUILD_TYPE=Debug ..

$ make

$ sudo make install

$ sudo ldconfig

$ sudo apt-get -y install cmake

$ git clone git://github.com/Neopallium/lua-zmq.git

$ git checkout v1.1

$ cd lua-zmq ; mkdir build ; cd build

$ cmake -DCMAKE_BUILD_TYPE=Debug ..

$ make

$ sudo make install

$ sudo ldconfig

sql中!=与的区别

背景

sql中表示不等于关系时，有两种写法!=、<>，抱着刨根问底的精神，看看这两个符号到底有什么不同

标准答案

https://stackoverflow.com/questions/18015422/what-is-difference-between-and-in-sql-server

搬运过来

这两个符号没有任何区别，你使用哪个都一样。

Microsoft的文档中，这两个符号的意义相同，都是 Not Equal To

https://docs.microsoft.com/en-us/sql/t-sql/language-elements/not-equal-to-transact-sql-exclamation?view=sql-server-2017

但，<>是ANSI 99 SQL标准中的定义，!=不是。所以，不是所有的DB引擎都支持!=。

最终推荐使用<>。

STM32开发环境

OpenSTM32开发环境

install_sw4stm32_macos_64bits-v2.6.run.tar
install_sw4stm32_linux_64bits-v2.6.run.tar
install_sw4stm32_win_64bits-v2.6.exe

辅助工具

官方下载地址 ST-LINK-SERVER
本站下载一份拷贝 ST-LINK-SERVER 1.0.6

ST的MEMOS开发参考

en.x-cube-mems1
en.stm32cubemx

继续阅读STM32开发环境

一	二	三	四	五	六	日
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31