element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Experimenting with Gesture Sensors
  • Challenges & Projects
  • Design Challenges
  • Experimenting with Gesture Sensors
  • More
  • Cancel
Experimenting with Gesture Sensors
Forum Establishing serial communication over UART instead of USB in MAX25405 EVKIT
  • Challenge Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Experimenting with Gesture Sensors to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 89 replies
  • Subscribers 41 subscribers
  • Views 10299 views
  • Users 0 members are here
  • MAX25405
  • gesture sensors
  • maxim integrated
  • uart
  • max32620fthr
Related

Establishing serial communication over UART instead of USB in MAX25405 EVKIT

rsjawale24
rsjawale24 over 2 years ago

The MAX25405EVKIT comes with a MAX32620FTHR board which is preprogrammed with custom binary file for the gesture recognition. The application note at Maxim Gesture Sensor EVKit Serial API (maximintegrated.com)

mentions "The serial interface can be implemented over the Universal Serial Bus (USB) virtual serial port or over a Universal Asynchronous Receiver-Transmitter (UART). The EV kit is shipped configured to use the USB serial port to work with the EV kit PC Graphical user Interface (GUI). If a UART serial interface is desired, custom firmware in binary format is available."

Upon researching more, I found the firmware_framework code that contains the code for gesture recognition compiled using mbed compiler.

The readme file says that a file called interface.h and interface.c define the communication protocol. When I open the interface.c file, I can see a comment in the code that says Option to implement serial API over UART instead of USB but there is only a MACRO set as #define macro_name 0 

I tried to change the 0 to 1 and compile the code, however, it does not compile successfully. The USBDevice library shows some error while compiling. 

Did anyone try to change the serial API over UART instead of USB? Was it successful?  

EDIT: I have successfully compiled the code for UART. However, I'll do some experiments and write introductory blogs before I re-program the MAX32620FTHR board with my firmware. 

  • Sign in to reply
  • Cancel

Top Replies

  • misaz
    misaz over 2 years ago in reply to misaz +4
    Today I found root cause of the issue. Issue is caused by invalid assembly code generated by modern ARM compiler. With older GCC compiler it works because it handle undefined behaviour used in code differently…
  • misaz
    misaz over 2 years ago +3
    I am curious how did you successfully compiled non-changed code? I started working with latest mbed-os but I was unable to compile it (missing toolchain) no matter of USE_UART_INTERFACE setting. Later…
  • BigG
    BigG over 2 years ago in reply to rsjawale24 +3
    I've create a very basic stripped down library based on the firmware framework using the latest MbedOS 6.16. github.com/.../Max25x05_MbedOS6 All it is doing is getting the raw pixel data. It is doing…
  • rsjawale24
    rsjawale24 over 2 years ago in reply to misaz

    I think I know where I made a mistake. When I compiled the framework code, I was getting an error in the compiler

    Error: Non-void function does not return a value [-Werror,-Wreturn-type] in "cmd.cpp", Line: 283, Col: 1

    I went to the cmd.cpp file and added a return 0; at the end.

    After which the code compiled without any errors.

    But this return 0; statement will always return a 0 on the execution on the function in cmd.cpp file. 

    And this may be the reason why I'm not receiving anything over UART.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rsjawale24
    rsjawale24 over 2 years ago in reply to BigG

    Thanks! I'm a beginner at mbed. I have only used 8051 in Keil uvision and Arduino till date. I haven't used any advanced MCUs so I have a very little idea on using mbed command line interface as suggested by the readme file.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • BigG
    BigG over 2 years ago in reply to rsjawale24
    rsjawale24 said:
    I'm a beginner at mbed

    Don't worry, I found the documentation on the MbedOS website to be very helpful and you should pick it up fairly quickly. Nevertheless, if you get stuck or if there's something you do not understand just ask and I'm happy to help.

     I have never had to use the command line before now, as I prefer to rely on Mbed Studio. This is the first time I've used CLI to handle a GCC compile for Mbed.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • rsjawale24
    rsjawale24 over 2 years ago in reply to BigG

    Thanks! I'll surely message you if I need any help. 

    I compiled the firmware using the code provided by Maxim and using the same version of mbed os as misaz. 

    It succeeded but with 24 warnings!! 

    This is when UART is set to 0 (disabled) in the interface.h file.

    I uploaded the binary for USB and it worked with the Maxim GUI. So now I have the original binary for USB interface. Let me know if you need it, I can email it over to you. 

    image

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • BigG
    BigG over 2 years ago in reply to rsjawale24

    Excellent. I sent you a private message with my email address. Thanks very much.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • BigG
    BigG over 2 years ago

    I was experimenting with the different options on the MAX32620FTHR board to print serial messages. I created some simple code to test behaviour using the latest MbedOS 6.16.

    I made life easier and also used a wrapper library, which you would need to import into your project: os.mbed.com/.../

    Here is the example code:

    /* mbedOS 6.16
     * Board: MAX32620FTHR
     * Copyright (c) C Gerrish
     * SPDX-License-Identifier: Apache-2.0
     */
    
    #include "mbed.h"
    #include "BufferedSerial.h"
    #include "SerialStream.h"
    #include "USBSerial.h"
    
    // Blinking rate in milliseconds
    #define BLINKING_RATE       1000ms
    
    #define UART_BAUD_RATE      115200
    
    BufferedSerial fthrUART(P3_1,P3_0, UART_BAUD_RATE);
    // This SerialStream is a wrapper for Stream.h to give you printf
    SerialStream<BufferedSerial> RXTX(fthrUART);
    
    // true here blocks until USB serial monitor opens
    // in Arduino you would use while(!Serial) for same effect
    USBSerial USB(true, 0x0b6a, 0x4360, 0x0001);
    
    int main()
    {
        // Initialise the digital pin LED1 as an output
        DigitalOut led(LED1);
    
        int cntr = 0;
    
        while (true) {
            led = !led;
            ThisThread::sleep_for(BLINKING_RATE);
            USB.printf("hello USB world %d\r\n", cntr);
            RXTX.printf("hello RXTX world %d\r\n", cntr);
            printf("hello DEBUG world %d\r\n", cntr);
            cntr++;
        }
    }
    

    The mbed_app.json file:

    {
        "target_overrides": {
            "*": {
                "platform.stdio-baud-rate": 115200,
                "platform.stdio-buffered-serial": 1
            }
        }
    }
    

    And here is a short video:

    You don't have permission to edit metadata of this video.
    Edit media
    x
    image
    Upload Preview
    image

    [Post EDIT]

    Looking at the original MAX25x05 gesture library again to see how the serial part could be adapted to OS6.16 I would say that you could use...

    the UnbufferedSerial API for when USE_UART_INTERFACE = 1 as this only provide putc etc.

    I've just realised that the above statement is not correct.

    In OS6.xx, it is not that simple to use putc anymore. In fact, I think the only way I could find is though the SerialStream wrapper. Not worth the effort, IMHO. If I had read the UnbufferedSerial API documentation more carefully then I would see that it only provides a write function. Sorry about that.

    and you could use BufferedSerial API for when USE_UART_INTERFACE = 0 as this provide buffered writes etc.

    Hope that helps.

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Cancel
  • rsjawale24
    rsjawale24 over 2 years ago in reply to BigG

    Hi thanks for this. The only problem with this is that I will have to re-write the entire code for the gesture sensor. What I'm aiming for is just to get the gesture results over UART instead of the USB connection. As per the application note from Maxim, this should be possible. 

    I'm trying to read the values from the MAX32620 board using Arduino. Here's my code. I'm not sure if this is correct.

    int ges_res = 0;  //variable to store gesture result
    
    void setup() {
      // put your setup code here, to run once:
    Serial.begin(115200);         //initialise serial comm. at 115200 baud
    
    }
    
    void loop() {
      // put your main code here, to run repeatedly:
    Serial.write("ver");         //send a command to the MAX32620FTHR firmware as it expects a command from user
    delay(1000);                //delay to slow down the interval at the command is being sent to the FTHR board
    ges_res = Serial.read();   //read the ges_res from MAX32620 board
    Serial.println(ges_res);        //print the result on the serial monitor
    }
     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • BigG
    BigG over 2 years ago in reply to BigG

    I was thinking about how we could minimise changes in the code, so here is one option that simplifies things.

    This code will either print to the debug/console UART pins (as defined in pinNames.h) or to UART pins of choice.

    #include "mbed.h"
    
    #define USE_UART_INTERFACE 1
    
    #if USE_UART_INTERFACE
        #define printf(f_, ...) fprintf((f_), __VA_ARGS__);
    #else
        #define printf(f_, ...) printf( __VA_ARGS__);
    #endif
    
    BufferedSerial otherUART(P3_1,P3_0,MBED_CONF_PLATFORM_STDIO_BAUD_RATE);
    FILE* myTX = fdopen(&otherUART, "r+");
    
    // main() runs in its own thread in the OS
    int main()
    {
        printf(myTX,"Hello New World\r\n");
    
        while (true) {
    
        }
    }
    
    

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Cancel
  • rsjawale24
    rsjawale24 over 2 years ago in reply to BigG

    Today I tried to read the UART from the MAX32620 into a FT232 USB to UART interface, it seems that the MAX32620 is not sending anything over UART. This is for the framework code provided by Maxim

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • BigG
    BigG over 2 years ago in reply to rsjawale24

    Are you still using your version of MbedOS?

    Just to say that I have managed to get the firmware working with the latest MbedOS 6.16 and have tested it using a Windows laptop with the Maxim GUI software. It all works. I'll post some guidance if you need it. Basically this is cleaner as you do not need to download the separate USBdevice or the MAX32620 libraries. All I had to do was amend a couple of lines in interface.cpp.

    So, basically I ignored the UART option as there really is no point using this option when the shield is attached to the MAX32620FTHR board, because you cannot readily get access to the GPIO's unless putting it on a breadboard or soldering wires.

    But, if I wanted to use UART in the latest MbedOS 6.16 I would then have to use with BufferedSerial or UnbufferedSerial API and then I would need to amend the code in CMD.cpp as, unlike USBSerial, these API's don't provide printf or getc functions.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
<>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube