LPC11u24 deepsleep interface disconnect about mbed-os HOT 8 CLOSED

I agree with this, not only does it affect development boards without an interface chip, but it affects any production boards using the mbed SDK as well.

from mbed-os.

Hello Erik,

Is this issue solved? If yes, please close this issue. I can see that is macro protected now.

    // ensure debug is disconnected
    #if DEVICE_SEMIHOST
    mbed_interface_disconnect();
    #endif

from mbed-os.

Actually, no :P. That fixes it on devices without semihost (such as the seeeduino arch), but it imo should be completely removed. For reasons see above :). And personally I would put it in powerdown instead. Also PDAWAKECFG should only wake with is currently enabled (easy to make), instead of everything.

But since in the meantime I started doing other stuff and with only Neil's reaction on it I didn't feel like changing the original mbeds behavior.

from mbed-os.

Aside from LocalFileSystem (which isn't going to be around forever since the mbed interface is deprecated now), what benefit does semihosting offer? All I see are drawbacks. For example, the mbed-rtos library can't put the chip to sleep in the idle thread because it might disconnect from semihosting. So what's the point of an idle thread then? I'm of the opinion that semihosting needs to bite the dust entirely.

from mbed-os.

Heh it understands I referenced this. Pull request in to change this, then I close it ;).

Btw I agree with Neil. LocalFileSystem is a very neat thing to have, but in general the semihosting interface is not the greatest thing since sliced bread. Although it can't put it to sleep in idle thread? Never tried it, but regular sleep works fine. Although also the others I have tried all end up in a debugging state when the interface chip is also powered, so including newer mbeds. (You notice that since its powerdown consumption is a few milli-amps instead of micro-amps).

from mbed-os.

Pull request was cancelled. The bug is still there, so hopefully mbed staff fixes this in the future. With some toying around I made my lpc11u24 semi debug-aware, so maybe something like that would meet the requirements.

from mbed-os.

Old one, but what I just considered: Did anyone ever checked if the disconnect command to the mbed interface does even have any influence whatsoever on the state of the target (the LPC11u24)? I ask because I recently had some discussions with an ARM colleague of yours (mbed staff), Yunfei Niu, and he wasn't able to really get the LPC1768 out of the debug mode it is standard in. In addition personally I haven't been capable of getting any target out of debug mode without power cycling: Just resetting the microcontroller also never did the job.

from mbed-os.

ARM Internal Ref: IOTMORF-328

from mbed-os.