Which are the available dongles required for the MAX86140EVSYS?

The USB to Bluetooth dongle should be included in the evaluation kit. There is a typo in the datasheet for the MAX86140EVSYS.

What Bluetooth dongle is compatible with the MAX86140EVSYS?

Bluetooth Dongles CY5677 or CY5670 are compatible for use with the EVKIT. The dongle is included in the EVSYS.

How to upgrade MAXSensorBLE F/W using the MRD100HDK

Overview Multiple evaluation kits and reference designs implement the MAXSensorBLE_EVKIT board that contains both a Nordic nRF52 and Maxim MAX32620 microcontroller device. This document describes how to program the boards requiring a MAXREFDES100HDK (MRD100HDK) programming board. Section 4.2 describes programming for version 2.0+, using the MAXDAP-Type-C programming board. The Eval Kits highlighted in green are the target devices potentially requiring programming via a MRD100HDK board. Eval Kit/Ref Dsgn Programming Board Referenced Included in Kit? Notes MAXREFDES104 MAXDAP-Type-C X F/W upgrade instructions in DS MAX86140EVSYS MRD100HDK MAX86160EVSYS MRD100HDK MAX86171EVSYS MRD100HDK MAX86173EVSYS MAXDAP-Type-C X F/W upgrade instructions in DS MAX86174EVSYS MAXDAP-Type-C X F/W upgrade instructions in DS MAX86176EVKIT MAXDAP-Type-C X F/W upgrade instructions in DS MAX86177EVKIT MAXDAP-Type-C X F/W upgrade instructions in DS MAX86178EVKIT MRD100HDK X F/W upgrade for nRF52 instructions in DS. Does not include MAX32620 F/W upgrade instructions. MAX86180EVSYS MAXDAP-Type-C X F/W upgrade instructions in DS MAXM86146EVSYS MRD100HDK MAXM86161EVSYS MRD100HDK X No instructions in EVSYS DS given. Notes: 1) The MAXREFDES100HDK# is currently not available for purchase. 2) If the MRD100HDK is unavailable, the MAXDAP-Type-C programming board can be used. Required Tools The following are required: Windows 7 or 10 MAXSensorBLE_EVKIT Board Programmer Board: MAXREFDES100HDK# USB male A to micro male B cable Firmware files (e.g., XXX_mcu_flashtools_yyyymmdd.7z file format) MAXREFDES100HDK# The MAXREFDES100HDK# is the programmer. It plugs into the MCU board right-side up to program the MAX32620, and it plugs in upside down to program the nRF52. The following pictures show the connection when programming the MCUs. Plug the USB micro B into the ‘HDK’ input (not the ‘DEV’ input). Figure 1: Using the MAXREFDES100HDK# to program the nRF52 Figure 2: Using the MAXREFDES100HDK# to program the MAX32620 Programming the nRF52 Unzip the firmware file to a directory on your PC and use Windows Explorer to enter the newly created directory If necessary, edit and save “erase+flash_nrf52.bat” with the new firmware filename that you want to program. Modify *.hex in erase+flash_nrf52.bat openocdbin0.10\openocd -f nrf52_isyst_cmsisdap.cfg -c "program *.hex verify exit" The nRF52's *.hex file includes: softdevice, bootloader, application and settings *.hex files merged into one Do not upload the application *.zip file using the MAXREFDES100HDK#; this file is meant for over-the-air device firmware update (OTA DFU) Double click erase+flash_nrf52.bat An erase will be followed by a program; you will be prompted to “press any key” twice Watch the console output for any signs of failure Power cycle the hardware This may require holding the power switch for 25 seconds This can be done after both MCUs are programmed You can then close Nordic nRF Connect and the OSxx UI will function properly Programming the MAX32620 Upgrading from v1.2 and earlier to v2.0+ Important: v2.0+ firmware is meant for use with a bootloader. The bootloader can only do Device Firmware Updates (DFU) on MAX32620 rev C2. This procedure installs both the bootloader and v2.0+ application firmware. Although these can be installed on MAX32620 rev A4, any attempt to do DFU will fail and erase the application firmware. A full reprogram will then be required using this procedure. Note: The procedure described here will not work if the bootloader is already installed (which implies that v2.0+ application firmware is also installed). Erase failure messages will occur if this procedure is attempted, but the existing bootloader and application will not be affected. See next section (Upgrading from v2.0+). Unzip the firmware file to a directory on your PC and use Windows Explorer to enter the newly created directory If necessary, edit and save “erase+flash_nim.bat” with the new firmware filename that you want to program. Modify *.elf in erase+flash_nim.bat for Nimitz openocdbinMaxim0.9\openocd -f max32620_swd_cmsisdap.cfg -c "program *.elf verify exit" The line for the bootloader (* .hex ) should not need to be modified Do not upload the application *.bin file using the MAXREFDES100HDK#; this file is meant for drag-and-drop device firmware update Double click erase+flash_nim.bat An erase will be followed by two programs (one for the bootloader and one for the application); you will be prompted to “press any key” three times Watch the console output for any signs of failure Power cycle the hardware This may require holding the power switch for 25 seconds This can be done after both MCUs are programmed Upgrading from v2.0+ Upgrading Firmware In case the MAXSENSORBLE_EVKIT_B board firmware needs to be upgraded, follow the procedure to properly flash the firmware: 1) Connect the MAXSENSORBLE_EVKIT_B board to the MAX-DAP-TYPE-C programmer board as shown in Figure 3. Whether the MAXSENSORBLE_ EVKIT_B board is connected to the MAXxxxxx_ OSB_EVKIT_x board or not, does not matter. The orientation of Type-C connection between the MAXDAP-TYPE-C programming board to the MAXSENSORBLE_EVKIT_B board does matter during flashing, which can be checked by making the Maxim logo on the programmer board stay on the same side with the Power Button of MAXSENSORBLE_EVKIT_B board. Connect the USB Micro to USB-A cable to your PC and then the MAXSENSORBLE_EVKIT_B board has red and yellow status indicator LEDs on. 2) Unzip the firmware file (e.g., MAXxxxxx_mcu_flashtools.7z). In the unzipped folder (see Figure 4 for an example), double click the file “erase+flash_ nrf52.bat.” Note: Do not simply copy the .bat file to any other folder, as the .bat file requires support from the files in this folder. 3) A command prompt should pop up when the “.bat” file is opened. Follow instructions provided in the command prompt to finish flashing the firmware. If the command prompt shows “Verified Okay,” the firmware has been successfully flashed on the MAXSENSORBLE_EVKIT_B board (see Figure 5 for an example). If you get any error, check all USB orientations and redo step 2 and step 3. 4) Once finished, unplug the MAXDAP-TYPE-C programming board from the MAXSENSORBLE_ EVKIT_B board. 5) Power off the MAXSENSORBLE_EVKIT_X board by holding down the Power Button for 12+ seconds and all the LEDs will be off. If MAXxxxxx_OSB_EVKIT_x board is not connected to the MAXSENSORBLE_ EVKIT_B, connect those two boards. 6) Now the MAXSENSORBLE_EVKIT_B board is ready. Power on the Sys by holding the Power Button for less than 1 second. Note: Holding longer for 1 second brings MAXSENSORBLE_EVKIT_B board into bootloader mode. Figure 3. Connections to Flash Firmware on MAXSENSORBLE_EVKIT_B Board Figure 4. Flash the new FW by double-clicking erase+flash_nrf52.bat Figure 5. Command Prompt Display when firmware has successfully been flashed

Error Message "Unable to load DLL 'PSnrACDC.dll': The specified module could not be found." while launching software

It has been identified that some of the bio sensor evaluation kits and MAXREFDES solutions software GUIs show the following error when the application is starting: This has been linked to the 32-bit version of the Visual C++ Redistribute Packages for Visual Studio 2013, which needs to be installed for the Software GUI to work. Download and install the x86 (32-bit) version of the Visual C++ Redistributable Packages for Visual Studio 2013. https://www.microsoft.com/en-us/download/details.aspx?id=40784

Why is MAX86140EVSYS GUI PPG Plot Data Information not showing PSNR, PSNR Avg, AC, DC?

The GUI will only display PSNR, PSNR Avg, AC, DC values when using sample rates divisible by 25.

How does the timestamp is formatted and generated on the MAXSENSORBLE_EVKIT board for the some of the PPG sensor's Evaluation Kits?

For all the evaluation kits ( MAXM86161EVKIT/SYS, MAXM86146EVKIT/SYS, MAX86176EVSYS, MAX86171EVSYS, MAX86140/1EVSYS) that contain the MAXSENSORBLE_EVKIT board, the timestamp format and how timestamps are generated is explained in the following summary: Format The timestamps are in milliseconds (ms) from the epoch ( converter ). Generation FW logic: SW sends wall clock time SW sends start command (enables RTC and sensors) Delay before ADC starts (i.e., MAX86141 DAC cal = ~180ms, other sensors = ~20ms) FIFO data is read periodically Every ~1s the RTC value is saved (RTC is read on FIFO interrupt) SW sends stop command The final RTC value is sent with the last FIFO sample(s) SW sends wall clock stop time (unless the device loses power before SW can send it) Parser logic: If a start and stop wall clock timestamp are available: The RTC tick period is: (start - stop - delay)/ (final RTC value) The default delay is 180ms for MAX8614x, 20ms for other sensors, but is adjustable via a parser parameter Otherwise: The RTC tick period is (RTCscale +1)/32.768kHz Default RTCscale = 31 The number of samples between two successive RTC values (which is saved every ~1s) gives the sample period for that group of samples The group of samples before the first RTC value uses (start – delay)/(number of samples before first RTC value). Hence if the delay is way off the mark, the sample period for this group will also be. It’s best to ignore the sample period for this group of samples If there isn’t a wall clock stop time (due to power loss), then the last group of samples will not have a sample period Each sample’s timestamp is the previous sample’s timestamp + its group sample period The first sample’s time stamp is the wall clock timestamp + its group sample period

What battery is recommended for use with the MAX86140EVSYS?

Any 3.7V battery would be suitable for the EVKIT. The LP-401230 would be one such suitable battery.

After installing the software by following the procedure in the evkit datasheet, I can see the COM port . However, there is no response after pressing "connect," and the MAX86140EVSYS cannot be connected. Why is that?

After installation, apart from selecting the correct COM port, BLE device must also be selected in order to connect to the evkit.

In the MAX86140EVSYS, do you use a standard heart rate service defined by the SIG or it is a custom service with custom characteristics? and which Bluetooth version is implemented?

The EVSYS uses a custom service with custom characteristics on Bluetooth 4.2.

Why I can not run the MAX86140EVSYS on my Windows 7 Operating system?

If you are getting an error as shown in the pictures below, you do not have the supported .NET framework to run the application. Notice on the download window it is indicated that a .NET framework version 4.5 or higher is required. You should be able to download the .NET framework for Windows operating systems from this link https://www.microsoft.com/net/download/framework Key Words: Fatal Error: "Sorry, application has to close! Please contact the developers with the following information."