Hi Zoltán,

thanks for the help I really appreciate it. I have changed the constructor definition and basically, the main problem was that I forgot to brackets after hm_10.setup(); I would like to implement your further suggestions as well, but first I would like to study it a little bit. To understand better your proposal, would it be still possible to use the serial functions inside the class? I mean e.g. serial.printf("bla bla"); My second question would be, why it is better to move this from cpp file to the header file?

HM_10(PinName tx, PinName rx, int bitrate = HM_10_BAUD) : Serial(tx, rx, bitrate), _ATCmd(this, "\r\n") {}

And one more thing, I have improved the library further a little bit, the constructor looks like now:

HM_10::HM_10(PinName tx, PinName rx, PinName state, PinName en) : _serial(tx, rx), _ATCmd(&_serial, "\r\n"), _state(state), _enable(en), _stateINT(state)
{   
    _enable = 0;
    _stateINT.fall(callback(this, &HM_10::statusChangeHandler));
    _stateINT.rise(callback(this, &HM_10::statusChangeHandler));
    //_serial.attach(this, &HM_10::RX_interrupt, Serial::RxIrq);
    _rx_in = 0;
}

My question is, is it the right way to define handlers if the state pin status changes, and/or attach an interrupt handler if data is received?

Thanks your help in advance!

• Since HM_10 is actually an extended Serial, HM_10's constructor, destructor or methods are free to call any (public or protected) Serial function. But be cautious with printf. There are actually defined two such functions. One inherited from the Serial class and another (global) one defined in the mbed library and associated with the default serial port (the one available as mbed virtual serial port on the connected PC). In HM_10 function definitions use symple printf(..) (or this->printf(...) to call the inherited function. To call the global one, defined outside the HM_10/Serial class, prepend the scope operator, like ::printf(..). This will instruct the compiler to call the global printf function. If you decide go with composition (by keeping a Serial member and removing inherintance) you'll be equally able to call Serial functions (like _serial.printf(...), etc). Choose whatever is easier and more comfortable for you.
• When you have a function or constructor/destructor with a very short or empty body you can make it inline by putting it's definition into the header file (or by declaring it as inline and keeping it in the cpp file ). The compiler will then substitute the function body for the function call, thus eliminating the overhead. The inline code does occupy space, but if the function is small, this can actually take less space than the code generated to do an ordinary function call (pushing arguments on the stack and doing the CALL).
• In my opinion, if you plan to connect status pins then it's logical to utilize them to handle the related intrrupts, actually as you did. I think you are on the right way. Good luck.

Thanks for your helpful feedback. I have continued to work on the HM_10.ccp and header file, the constructor how it is created almost working correctly, one think is not okay, and I have searched a lot but I cannot find the answer/solution, so the constructor looks like:

HM_10::HM_10(PinName tx, PinName rx, PinName state, PinName en) : _serial(tx, rx), _ATCmd(&_serial, "\r\n"), _state(state), _enable(en), _stateINT(state)
{   
    _enable = 0;
    _stateINT.fall(callback(this, &HM_10::statusChangeHandler));
    _stateINT.rise(callback(this, &HM_10::statusChangeHandler));
    _serial.attach(this, &HM_10::RX_interrupt, Serial::RxIrq);
    _rx_in = 0;
}

In that case I have warning: Warning: Function "mbed::SerialBase::attach(T *, void (T::*)(), mbed::SerialBase::IrqType) [with T=HM_10]" (declared at line 117 of "/extras/mbed/drivers/SerialBase.h") was declared "deprecated" in "HM_10.cpp", Line: 12, Col: 14

So I have changed it like the "rise" and "fall":

    _serial.attach(callback(this, &HM_10::RX_interrupt, Serial::RxIrq));

But in that case I get an error: Error: No instance of overloaded function "callback" matches the argument list in "HM_10.cpp", Line: 12, Col: 21

If I ignor the warning in case of the first version (without callback) and flash the device it is crashing after an Rx interrupt happens. What could be wrong? Just a note the "rise" and "fall" interrupts are working correctly, only the serial rx interrupt has problem.

Thanks your help in advance!

• If you dont like the warning try

    _serial.attach(callback(this, &HM_10::RX_interrupt), Serial::RxIrq);

• Mutex methods shall not be called from interrupt service routines. In the current version of Mbed OS, if you attempt to use a mutex from within an ISR, it will treat that as a fatal system error. Read here for more details. For example, if you try

void HM_10::RX_interrupt()
{
    char c = _serial.getc();
    //..
}

then it will result in a fatal system error because Serial::getc(), which is inherited from Stream, locks the Mutex (by calling the lock() function).