Mdot pinout – associate and on/sleep

Home › Forums › mDot/xDot › Mdot pinout – associate and on/sleep

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • February 2, 2016 at 1:56 pm #11526
    Neil MacMullen
    Participant

    Similar to this query… http://www.multitech.net/developer/forums/topic/mdot-pin/

    I would like to better understand which pins are available for use by our software when embedding mdot in our own hardware design and using the libmdot library.

    This document http://www.multitech.com/manuals/s000612.pdf provides a pinout (page 10) which describes ‘Associate’ and ‘On/sleep’ but doesn’t describe whether these are free for use by application software.

    Note that we are NOT using the AT or other standard firmware – we are writing our own application that will link to libmdot. We would like to use these pins as GPIOs for our own purposes. My question is whether this is possible or whether libmdot already makes some assumptions about the use/state of these pins.

    thanks,
    Neil

    February 4, 2016 at 1:38 pm #11555
    Mike Fiore
    Blocked

    Neil,

    The mdot page on mbed has some documentation: https://developer.mbed.org/platforms/MTS-mDot-F411/

    Associate and On/sleep pins are used by the factory AT firmware and are free for use by your application. Keep in mind that if you want to put the device in deepsleep mode and wake up with an interrupt, pin D3/XBEE_CTS/XBEE_DIO7/PA_0 is the only pin that can be used.

    Cheers,
    Mike

    February 7, 2016 at 11:30 am #11616
    Neil MacMullen
    Participant

    Thanks Mike – much appreciated.

    March 1, 2016 at 4:41 pm #11820
    Yusuf Goren
    Participant

    Dear Neil, Mike,

    Here is what I understand from mBed page
    (1) Pins 21-23 is for RF antenna only.
    (2) Pins 24-31 is for programming purpose only (i.e. I cannot use them for bus/IO operations in development).
    (3) Pin 1 is reserved for VIN, Pin 5 for reset, Pin 10 for ground, and Pin 12 for wake-up interrupt while Pin 8 and 14 are not connected (hence all these are out in development).
    (4) Any pin not mentioned above can be used as digital/analog IO.

    Could you tell if these are correct? Am I missing/overstating anything?

    Thanks a lot,
    Yusuf

    March 1, 2016 at 4:47 pm #11821
    Mike Fiore
    Blocked

    Yusuf,

    1-3 are correct. For 4, all those pins can be use as digital ins and outs. Only the pins with a UDK2 pin name staring with A can be used as analog pins.

    Cheers,

    Mike

    March 1, 2016 at 4:49 pm #11822
    Yusuf Goren
    Participant

    Mike,

    Thanks a lot for the prompt reply, I got it now!

    Thanks,
    Yusuf

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.