Maxim MAX32650-EVKIT

Table of contents

image

 

{tabbedtable} Tab LabelTab Content
About

The MAX32650-EVKIT# from Maxim Integrated is an evaluation kit (EV kit) for MAX32650. This EV kit provides a platform for evaluating the capabilities of the MAX32650 ultra-low power memory scalable microcontroller designed specifically for high performance battery powered applications. It can also evaluate MAX32651/MAX32652 IC's. Typically used at industrial sensors, IoT, sports watches, fitness monitors, wearable medical patches and portable medical devices.

image

Features

  • 3.5in 320 x 240 Color TFT Display
  • 64MB HyperRAM
  • 64MB XIP Flash
  • 1MB XIP RAM
  • USB 2.0 Micro B Interface
  • USB 2.0 Micro B to Serial UARTs
  • Selection with Jumpers Between UART0 and UART2
  • Micro SD Card Interface
  • Select GPIOs Accessed through 0.1in Header
  • Access to the Four Analog Input Through 0.1in Header
  • Arm® or SWD JTAG 20-Pin Header
  • On-Board PMIC to Source Power for the MAX32650
  • Board Power Provided by Either USB Port
  • Individual Power Measurement on All IC Rails Through Jumpers
  • On-Board 1.8V and 3.3V Regulators for Peripherals
  • Two General-Purpose LEDs and Two General-Purpose Pushbutton Switches

 

Kit contents

  • MAX32650 EV kit containing a MAX32650 with a preprogrammed demo
  • JTAG debugger with ribbon cable
  • One standard A-to-B USB cable
  • Two standard A to Micro B USB cables
  • Quick start Guide

Applications

  • Industrial Sensors, IoT
  • Sports Watches, Fitness Monitors
  • Wearable Medical Patches, Portable Medical Devices

 

Additional Information

Important Dates

Enrollment Begin: Oct 18 2019

Enrollment Ends: Nov 29 2019

RoadTesters Selected: Jan 3 2020

Product Shipped: Jan 3 2020

RoadTesting Begins: Jan 10 2020

Reminder/Update Email: Feb 10 2020

Submit Reviews By:Mar 10 2020

*The element14 RoadTest Staff will send this reminder/update email.

**If a RoadTester is unable to meet the deadline, please notify the RoadTest Program Lead, , as soon as possible before the deadline.

RoadTesters

Terms and Conditions

RoadTest: Terms and Conditions RX65N Envision Kit

 

These are the terms and conditions which govern the Maxim MAX32650-EVKIT contest. This Contest requires participants to submit an application indicating their previous experience with this type of equipment/component, information on what they would do to test the equipment/component, and the applicant’s desire to post a thorough review of their experience with images, photos, or other supplemental materials. Participants will be required to meet the Conditions for Participation.  The winners of this RoadTest will receive the item(s) listed below. RoadTest Reviews are due no later than 60 days after the receipt of the item(s). No other prizes are offered.

The Principal terms of the Competition:

The following words and phrases are used in these terms and conditions and have the meanings given to them below.

(RoadTest or Contest)

Key dates:

Applications Close: midnight (GMT) on Nov 29 2019

Announcement of Winner (estimated): Dec 3 2019

Prize: Maxim MAX32650-EVKIT

Additional Prizes: none

Competition Site: https://www.element14.com/community/groups/roadtest?ICID=menubar_resources_roadtest

Site or element14 Community: www.element14.com/community

Judges: members of the element14 community team chosen at the Organiser’s discretion.

Judging Criteria, All of the following which will have equal weighting:

· Demonstrated competence with the technologies including links or descriptions of past projects

· Qualifications as indicated by current job role and/or schooling/vocational training;

· A thorough description of how the prize would be tested;

· Likelihood that the Applicant will blog about the prize and provide a review on element14.com;

· Originality;

· Innovation.

Organiser: Premier Farnell plc (registered in England and Wales under company number 876412) whose registered office is at Farnell House, Forge Lane, Leeds, UK

Conditions for Qualification: in addition to meeting the requirements of these terms, all persons applying to take part in the Contest (each one an Applicant) must:

· Provide a RoadTest application describing what he/she would do if awarded the Prize including similar previous projects, product experience and qualifications

Terms: these terms and conditions which govern the Competition and to which the Organiser reserves the right to make changes from time to time and the latest version of these Terms from time to time will be posted to the Site.

  1. Eligibility
  2. Applications:
  3. Selecting Winners:
  4. Liability:
  5. General:

1.1 Save as set out in these Terms, the Contest is open to any natural or legal person, firm or company or group of natural persons or unincorporated body.

1.2 All Applicants must be aged at least 18 at the time of their application.

1.3 Applicants must not enter the RoadTest if doing so or taking part may:

1.3.1 cause the Organiser and/or themselves to be in breach of any agreement (including but not limited to any contract of employment) to which they are a party or in breach of any law, regulation or rule having the force of law to which the Organiser or the Applicant may be subject or any policy of the Organiser or the Sponsor;

1.3.2 Require the Organiser to obtain any licence, authorisation or permission to deal with the Applicant; or

1.3.3 Be in breach of any policy or practice of their employer. Some employers prohibit or restrict their employees from taking part in competitions such as these or receiving prizes under them and the Organiser respects those policies and practices.

The Organiser reserves the right to disqualify any Application made in breach of these Terms and to reject any Application which it reasonably believes may be or become in breach. The Organiser reserves the right to require evidence in such form as the Organiser may reasonably require of any Applicant’s compliance with any of these Terms and to disqualify any Applicant or Participant who cannot provide such evidence reasonably promptly.

1.4 Multiple applications are not permitted.

1.5 Applications may not be submitted by an agent whether acting on behalf of an undisclosed principal or otherwise.

1.6 The Contest is NOT open to:

1.6.1 Any person or entity who is a resident or national of any country which is subject to sanctions, embargoes or national trade restrictions of the United States of America, the European Union or the United Kingdom;

1.6.2 Any employee, director, member, shareholder (as appropriate) or any of their direct families (parents, siblings, spouse, partner, children) (“Direct Families”) of the Organiser and Sponsors; or

2.1 Each Applicant must fully complete and submit a RoadTest Application by the Application Close.

2.2 By submitting a Registration Form, each Applicant:

2.2.1 Authorises the Organiser to use his or her personal data (as defined in the Data Protection Act 1998) for the purposes of running and promoting the RoadTest;

2.2.2 Authorises the Organizer to copy, reproduce and publish their application should they be accepted as a Participant;

2.2.3 Will be deemed to have read, accepted and agree to be bound by these Terms. Applicants are advised to print and keep safe these Terms;

2.2.4 Authorises the Organiser to copy, reproduce and use the Application and/or Review for the purposes of the RoadTest and as otherwise contemplated by these Terms. The Organiser will not be responsible for any inaccuracy, error or omission contained in any reproduction or use of the Project Blogs.

2.2.5 Licenses the Organiser to use the intellectual property in the Project (IP) for the purposes of this Contest. As between the Applicant and the Organiser the IP remains owned by the Applicant.

2.2.6 Grants the Organiser the right to use his or her likeness, photographs, logos, trademarks, audio or video recordings without restriction for the purposes of Contest or the promotion of it or the Site;

2.2.7 Agrees to participate positively in all publicity surrounding the Contest;

2.2.8 Agrees to be responsible for all expenses and costs incurred by him or her in preparing for, entering and participating in the Contest (save for any expenses expressly agreed by the Organiser to be borne by it in these Terms);

2.2.9 Confirms that he or she owns all IP used in his or her application or Project or Blogs and indemnifies the Organiser from any claim by a third party that use of any material provided by an Applicant to the Organiser infringes the intellectual property rights of any third party;

2.2.10 Agrees not to act in any way or fail to act in any way or be associated with any cause or group which would have a negative impact on the reputation of the Organiser and/or the RoadTest.

2.3 All applications submitted to this RoadTest must meet the following criteria:

2.3.1 Applicants must be the author, creator and owner of the proposed review idea. Applicants must not submit someone else’s idea;

2.3.2 The proposed application must be reasonably achievable by the within the time constraints of the Contest;

2.3.3 Applications must not include or propose any of the following, the inclusion of which shall render any proposed application ineligible:

(a) Applications which relate to socially taboo topics, such as illicit drug use or sexual gratification;

(b) Applications that are or could reasonably be considered to be illegal, immoral, discriminatory or offensive as determined by the Organiser;

(c) Applications in relation to them which if accepted would infringe or breach any of the policies or terms of access or use of the Site.

2.4 No Application may contain any of the hazardous substances identified by Article 4 of Directive 2002/95/EC of the European Parliament on the Restrictions on the Use of Substances in Electronic and Electrical Equipment ("the Directive") or the use of such hazardous substances in the in any such Project must not exceed the maximum concentration values set out in the Directive.

3.1 Winners will be selected by the Organiser on the basis of the quality of his or her application and its adherence to these Terms.

3.2 The total number of Winners selected will be at least the minimum number set out above but the actual number is at the sole discretion of the Organizer and/or the Sponsor, if applicable.

3.3 The Organiser will use all reasonable efforts to announce the Winners via an update to the RoadTest page by the date listed above.

3.4 Winners agree to take part in all publicity which the Organiser or the Sponsor wishes to use to promote the RoadTest, the Products featured or other Contests with which the Organiser may be connected from time to time.

3.5 Details of the Winners may also be published in the media.

3.6 Winners are responsible for all applicable taxes, duties or other charges payable in relation to any prize.

3.7

4.1 The Organiser hereby excludes all and any Liability arising out of the Contest or the acceptance, use, quality, condition, suitability or performance of any Prize, even where that Liability may arise from the Organiser’s negligence.

4.2 Nothing in these Terms will affect any Liability of the Organiser for death or personal injury arising from its negligence, for breach of Part II of the Consumer Protection Act 1987 (in the event that any entrant is entitled to claim rights under the Consumer Protection Act 1987) or for any matter in relation to which it would be illegal for the Organiser to exclude or to attempt to exclude its Liability.

4.3 Subject to 4.2, neither the Organiser, any parent company nor any subsidiary of the Organiser or such parent company or any of their directors, officers and employees (together referred to in these terms and the ‘Associates’) makes any guarantee, warranty or representation of any kind, express or implied, with respect to this Competition or the Prizes potentially available under it. Neither the Organiser nor any of its Associates shall be responsible for any Liability that may arise out of or in connection with person’s participation in this Competition, the claiming, redemption or value of any prizes under it, the use or enjoyment of such prizes or any events or circumstances arising out of or in connection with any of them. Any implied warranties of condition, merchantability or suitability or fitness for purpose of any of them are hereby expressly excluded. Wherever used in these Terms, ‘Liability’ shall mean any and all costs, expenses, claims, damages, actions, proceedings, demands, losses and other liabilities (including legal fees and costs on a full indemnity basis) arising directly or indirectly out of or in connection with the matter concerned.

5.1 The RoadTest is organised and sponsored by the Organiser. The Organiser reserves the right to delegate all or any of its powers, rights and obligations arising in relation to the RoadTest to any Associate and certain such rights and powers are assumed by the Organiser on behalf of itself and each Associate. Reference to “Organiser” shall be deemed to include reference to each Associate.

5.2 The RoadTest may be terminated at any time if there are, in the sole opinion of the Organiser, an insufficient number of entries, or if the Applications are not of an appropriate standard for a competition of this nature. The Organiser has the right to cancel or suspend the RoadTest at any time due to circumstances outside its reasonable control.

5.3 The Organiser shall have the sole discretion to disqualify (without correspondence or right of appeal) any Applicant it considers to be adversely affecting the process or the operation of the RoadTest or to be in breach of these Terms or to be acting in a disruptive manner or with intent to annoy, abuse, threaten or harass any other Applicant or Participant.

5.4 The Organiser has the right to amend or add to these Terms from time to time. Revised Terms and Conditions will be posted on the Contest Site and it is a condition of entry to the RoadTest that Applicants agree to comply with these Terms and, if appropriate, such Terms as amended from time to time.

5.5 Headings are for convenience only and do not affect the interpretation or construction of these Terms and Conditions.

5.6 These Terms and the operation of the Contest shall be governed by and construed in accordance with English Law and any claim or matter arising under these Terms shall be subject to the exclusive jurisdiction of the English courts.

Comment List
Anonymous
  • So now should I disassemble the Olimex debugger and try to find any physical problem (if any)

     

    Hi Mahmood,

     

    There's a chance it is Windows driver related, if the Olimex device USB interface is using the same identification (VID/PID) as recognised by some other driver on your PC (e.g. due to some other hardware on your PC, or due to where the drivers are being loaded from).

    As I understand, that libusb error you're seeing, isn't a driver, rather libusb connects to a driver (libusb just presents a generic API to the application software, it is one more layer, so that the developers can write their app the same way for Windows and Linux etc).

    It could even be a permissions issue (just a guess though! - I don't understand Windows too well). You could right-click on it and check what driver got installed and what driver version, in case it looks different to others.

    Anyway, isn't the Segger debugger as good (or maybe even better) than the Olimex one? If it is a fault with the Olimex one, maybe it's a waste of time troubleshooting it since it isn't core to RoadTest?

  • If you can use the SEGGER j-link to program the board then personally I'd carry on and complete the roadtest of the MAX32650 using that setup. Otherwise time will slip past and the raodtest deadline will be looming ! The Maxim board is probably what everyone wants to read about anyway.

     

    I'd just note the failing of the Olimex unit in your roadtest report. Perhaps in slower time it is something Maxim can resolve if more people report their unit failed, maybe they will send you a new one but it will take a while I guess and we're halfway through the allocated time now.

     

    All that said, if you have time, pull the Olimex apart...the E14 community likes looking inside things image

  • Olimex debugger is not working so far. Possible there is some hardware issue in it.

    So currently I am using SEGGER j-link debugger and its working perfectly in both JTAG and SWD modes. This means all the JTAG/SWD pins and connections with MAX32650 mcu are in working condition.

     

    So now should I disassemble the Olimex debugger and try to find any physical problem (if any) or wait for the MAXIM support team response?

    Am I the only one with REV3 or anyone else has also received the REV3?

  • You are very welcome.

     

    Sorry for the confusion; the first case is correct and it did display max32xxx.cpu. Further on that line it displayed by board's own unique number (which I decided not to share online) and I replaced that four-byte hexadecimal value with XX. From that four-byte value it seems to be able to know it is an ARM device and the part is 0xba00. I suspect that last part equates to the MAX32650 being idenfied by openocd.

  • Thanks Sir for sharing the log.

    Is it

    Info : JTAG tap: max32xxx.cpu tap/device found: 0xXX (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) 

    or

    Info : JTAG tap: max32650.cpu tap/device found: 0xXX (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) 

  • Hope this helps, and good luck:

    Open On-Chip Debugger 0.10.0+dev-snapshot (2018-12-21-12:38)
    Licensed under GNU GPL v2
    For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
    srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
    adapter_nsrst_delay: 200
    Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
    adapter speed: 2000 kHz
    Started by GNU ARM Eclipse
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 4444 for telnet connections
    Info : clock speed 2000 kHz
    Info : JTAG tap: max32xxx.cpu tap/device found: 0xXX (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    Info : max32xxx.cpu: hardware has 6 breakpoints, 4 watchpoints
    Info : Listening on port 3333 for gdb connections
    Info : accepting 'gdb' connection on tcp/3333
    undefined debug reason 7 - target needs reset
    Info : JTAG tap: max32xxx.cpu tap/device found: 0xXX (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x00000184 msp: 0x2000b680
    Info : JTAG tap: max32xxx.cpu tap/device found: 0xXX (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x00000184 msp: 0x2000b680
    Info : JTAG tap: max32xxx.cpu tap/device found: 0xXX (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x00000184 msp: 0x2000b680
    Info : JTAG tap: max32xxx.cpu tap/device found: 0xXX (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x00000184 msp: 0x2000b680
    ===== arm v7m registers
    (0) r0 (/32): 0x00000000
    (1) r1 (/32): 0x00000000
    (2) r2 (/32): 0x00000000
    (3) r3 (/32): 0x00000000
    (4) r4 (/32): 0x00000000
    (5) r5 (/32): 0x00000000
    (6) r6 (/32): 0x00000000
    (7) r7 (/32): 0x00000000
    (8) r8 (/32): 0x00000000
    (9) r9 (/32): 0x00000000
    (10) r10 (/32): 0x00000000
    (11) r11 (/32): 0x00000000
    (12) r12 (/32): 0x00000000
    (13) sp (/32): 0x2000B680
    (14) lr (/32): 0xFFFFFFFF
    (15) pc (/32): 0x00000184
    (16) xPSR (/32): 0x01000000
    (17) msp (/32): 0x2000B680
    (18) psp (/32): 0x00000000
    (19) primask (/1): 0x00
    (20) basepri (/8): 0x00
    (21) faultmask (/1): 0x00
    (22) control (/2): 0x00
    (23) d0 (/64): 0x0000000000000000
    (24) d1 (/64): 0x0000000000000000
    (25) d2 (/64): 0x0000000000000000
    (26) d3 (/64): 0x0000000000000000
    (27) d4 (/64): 0x0000000000000000
    (28) d5 (/64): 0x0000000000000000
    (29) d6 (/64): 0x0000000000000000
    (30) d7 (/64): 0x0000000000000000
    (31) d8 (/64): 0x0000000000000000
    (32) d9 (/64): 0x0000000000000000
    (33) d10 (/64): 0x0000000000000000
    (34) d11 (/64): 0x0000000000000000
    (35) d12 (/64): 0x0000000000000000
    (36) d13 (/64): 0x0000000000000000
    (37) d14 (/64): 0x0000000000000000
    (38) d15 (/64): 0x0000000000000000
    (39) fpscr (/32): 0x00000000
    ===== Cortex-M DWT registers

     

    [My part number for my device is where 0xXX]

  • I have re-installed it several times, also tested it on newly installed window 10 x64 and everywhere I am getting the same errors.

    If its possible can you share the all the lines in openocd log?

    All the drivers are perfectly fine. Its able to communicate with the debugger but unable to detect the mcu and write the flash. Whereas segger debugger is working perfectly fine image

  • Hi ,

     

    Mine seems to work OK with the Olimex unit and I'm running Windows 10 x64. I can run the code or debug step by step....although I'm no expert.

     

    When I enter debug mode I get some of the code you listed below appear in red in my console output, with line 10 being the same and then mine deviates off:

    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 4444 for telnet connections
    Info : clock speed 2000 kHz

     

    Did you run the ArmCortexToolchain.exe from Maxim to install Eclipse and all the drivers?  Under device manager I can see this, and your printout seems to have an issue at libusb:

    image

     

    If you have installed that perhaps an uninstall and re-install might help, or a re-boot if only just installed?

  • Is anyone able to use OLIMEX debugger with window 10 x64?

    And also can anyone compare the openocd log?

    Any idea how to solve the issue? Currently I am testing with J-link debugger.

     

    Open On-Chip Debugger 0.10.0+dev-snapshot (2018-12-21-12:38)
    Licensed under GNU GPL v2
    For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
    srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
    adapter_nsrst_delay: 200
    Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
    adapter speed: 2000 kHz
    Started by GNU ARM Eclipse
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 4444 for telnet connections
    Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
    Info : clock speed 2000 kHz
    Info : JTAG tap: max32xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    Info : max32xxx.cpu: hardware has 6 breakpoints, 4 watchpoints
    Info : Listening on port 3333 for gdb connections
    Info : accepting 'gdb' connection on tcp/3333
    undefined debug reason 7 - target needs reset
    Info : JTAG tap: max32xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x00000184 msp: 0x2000b680
    Info : JTAG tap: max32xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x00000184 msp: 0x2000b680
    Error: Invalid ACK (0) in DAP response
    Error: Failed to write memory at 0x20005d20
    Error: JTAG-DP STICKY ERROR
    Warn : target was in unknown state when halt was requested
    Error: JTAG-DP STICKY ERROR
    Error: JTAG-DP STICKY ERROR
    Error: error waiting for target flash write algorithm
    Error: JTAG-DP STICKY ERROR
    Error: Failed to write memory at 0x40029024
    Error: JTAG-DP STICKY ERROR
    Error: Failed to write memory at 0x40029008
    Error: error writing to flash at address 0x10000000 at offset 0x00000000
    Error: JTAG-DP STICKY ERROR
    Polling target max32xxx.cpu failed, trying to reexamine
    Info : max32xxx.cpu: hardware has 6 breakpoints, 4 watchpoints
    Info : JTAG tap: max32xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x00000184 msp: 0x2000b680
    Info : dropped 'gdb' connection

  • I believe that when the debugger is attached, it holds the microcontroller in Reset until you start a debug session, by asserting the ~reset pin.