Leon Lindenfelser
Forum Replies Created
-
AuthorPosts
-
Leon Lindenfelser
ModeratorHi Ryan,
Take a look at this link:
It’s as simple as it looks. As you already know, devices just need a different address to function properly.
The schematic can be found here:
https://www.multitech.com/documents/publications/hardware-guides/s000707.pdf
JP2 is under the LCD. You can access it from the bottom of the PCB. The square pin is pin 1.
I’d recommend you also look up and understand part PCA9517A. Again a pretty basic thing.
Good luck and have fun!
LeonModeratorThe mdot library sleep and deepsleep place the processor in stop mode. If you want to wake up to reset the watchdog every 20s, I recommend configuring the sleep function to wake every 20s to do that. Don’t add another LowPowerTimeout. I recently worked with someone who was testing out the possibility of using more than one timeout to wake and it can create problems in rare instances.
ModeratorHi Paul,
If your xDot is on the developer board, hold the reset button down and release it immediately after you drop the bin file.
Kind regards,
LeonModeratorIt needs to be high. NRESET is connected to the NRST pin of the STM32F411 processor. If it is held low, the processor will remain in the reset state.
ModeratorYou need to perform 1 and 2. After driving NRESET low for 1ms, the GPU pin can be left floating so that the internal pullup pulls it high or the GPU can drive it high.
ModeratorRight, ring indicator goes to the 40 pin connector pin 11 AND to pin PB1. So it can be read using pin names PB_1 or D8. See page 15 of the device guide.
https://www.multitech.com/documents/publications/device-guides/s000656.pdfModeratorHi,
The ring indicator pin from the radio goes to the 40 pin connector on pin 11. If you want to read it from the on board processor, you need to connect it to one of the GPIO pins on the 40 pin connector.
The 3 pin connector is for battery power/charge. It connects to a Texas Instruments BQ24074 linear battery charger.Leon
ModeratorSearch for SMTSO-M2-6ET.
ModeratorCorrect.
The interface chip or an SWD/JTAG interface is necessary if you wish to be able to perform in circuit firmware update. Another possible firmware update option would be to update via FOTA.ModeratorHi Toyo,
When plugging into the micro USB connector, you gain access to two serial ports. Pins 9 & 32 go through the USB-UART converter. Pins 1 & 40 go through the interface chip.
The USB pins on the 40 pin connector and not routed to anything on the UDK board. They are connected in parallel with the micro USB connector on the MTQ.
LeonModeratorPlease give this a try:
https://os.mbed.com/teams/MultiTech/code/Dragonfly_Filesystem_Example_mbed_5/ModeratorJust the radio firmware changed. Same flash part.
Moderatorhttps://www.multitech.com/brands/multiconnect-dragonfly
LAT3 Lists the region as US/Canada
MNA1 Lists the region as USModeratorYes, they are pin compatible.
ModeratorMTQ-MNA1-B01: I’m glad you pointed that out. The documentation must not have been properly updated.
MTQ-LSP3-B03: This is Sprint only.I’m going to see if I can get the file system example to build on a newer version of mbed.
ModeratorOn the following Dragonfly and Dragonfly Nano models, we are shipping with a flash part that support SFDP:
MTQ-MVW1-B01
MTQ-MNA1-B01
MTQ-LSP3-B03
MTQN-MNG1-B01
MTQN-MNG3-B01
Other Ddragonfly models will have a flash part, of the same density, that does not support SFDP. To verify the flash part is one that supports SFDP, you can see a rather large ‘G’ logo on the tiny part.ModeratorYou are right… it is connected to SPI3. These are the pin names. PA_4 did not receive an alias of SPI3_CS. You need to reference it as PA_4.
PA_4 is the SPI3 chip select.
PC_10 or SPI3_SCK
PC_11 or SPI3_MISO
PC_12 or SPI3_MOSIModeratorHi Ajay,
For the STM32, in isolation, setting all GPIO to “analog input no pull” will achieve lowest power consumption. However, you need to consider the attached components on your external I/O. Early on, we discovered some unexpected power draw unless certain pins were in a specific state. For instance, one component required pull down resistors on it’s SPI clock and MOSI pins in order for it to achieved its advertised lowest power in sleep mode. For cases like yours, where you have external components attached, we provide sleep versus deep sleep. In sleep mode we don’t set the external I/O to analog input no pull (in deep sleep we do). That allows the user to configure the external I/O, during sleep, as they see fit without interference from our library. If deep sleep is not getting to the expected low power level, you will need to sleep instead and configure the external I/O appropriately to achieve lowest possible current draw.
Kind regards,
LeonModeratorFebruary 13, 2020 at 9:00 am in reply to: Dragonfly nano becomes unresponsive after sleep mode #30275ModeratorHi Daniel,
I tried to duplicate the issue here with no luck. Please open a support ticket at https://support.multitech.com/support/login.html and put the above information in the case. That will make it easier for us to get everyone we need involved and figure out what’s going on.
Leon
February 12, 2020 at 5:32 pm in reply to: Dragonfly nano becomes unresponsive after sleep mode #30271ModeratorHi Daniel,
Please issue the following commands and let me know what the response is for each.
AT+CPSMS?
AT+UPSV?
AT+UMNOPROF?Kind regards,
LeonModeratorI don’t have a good reason for why the table is populated as it is other than the full complement of measurements was not taken for each voltage. Are there some specific power draw questions you have that I can help with?
ModeratorI’m checking on the power consumption table. All functionality is there across the voltage range. So it has nothing to do with limitations at certain voltages. That said, I’ll let you know what I find out.
I want to add some clarification about what the developer guide stated regarding 5v on the Dragonfly. There is a jumper on the board “TARGET VOLTAGE” that can be used to set the voltage supplied to MDOT or MTSMC types of devices to 3.3v or 5v. That jumper does not apply to the Dragonfly. Dragonflies will be powered by 5v unless you get a bit more creative and place a jumper from the 3.3v pin of the “TARGET VOLTAGE” connector to the appropriate pin of the 2 pin connector next to the Dragonfly connector.
ModeratorYes, the acceptable operating voltage is 3.2v-5.25v.
ModeratorUse the electrical characteristics information from the Dragonfly Nano device guide not the developer kit documentation. Sorry for the confusion.
Kind regards,
LeonModeratorHi Mark,
Make sure the wake pin is low then provide a rising edge to wake it. See errata section 2.1.12:
https://www.st.com/content/ccc/resource/technical/document/errata_sheet/a0/5e/99/68/b3/e2/41/57/DM00106202.pdf/files/DM00106202.pdf/jcr:content/translations/en.DM00106202.pdfKind regards,
LeonModeratorHi David,
Please measure the voltage you are providing to the mdot. VDD is pin 1. The voltage needs to be in the range of 3.3v-5v.
What voltage is your host board expecting? Is it a direct connection to the UART… no transceiver or level shifters?
Kind regards,
LeonModeratorHi David,
If the AT application is not loaded, that could be the issue.
The reset line has a weak pull up on it. So that should be fine.
Leon
ModeratorHi David,
Are you sending commands at 115200bps? Did you connect ground?
Leon
ModeratorYes. The Dragonfly has a 2MB flash part that you can use for whatever you want. We happen to load it with a flash file system.
mbed is running out of the flash memory in the STM32F411 processor.
mbed is tagged with a version number… git describe –match mbed-os*. It’s up to you to checkout the version of mbed before building your application.As for the leds, here is the manual for the UDK board(USB only version).
https://www.multitech.com/documents/publications/manuals/s000610.pdf
The UDK schematic starts on page 20. The STAT & COM leds flash when programming a target device.
See the pinout diagram for D0-D8 here:
https://os.mbed.com/platforms/MTS-Dragonfly/
These are controlled by GPIO from the STM32F411 processor. You can do what you want with them.
The link status LED is on pin 34 of the 40 pin connector and is driven directly by the cellular radio GPIO pin 1. You can also program that to the extent that the radio firmware allows.Kind regards,
Leon -
AuthorPosts