{"id":6224,"date":"2020-06-01T12:52:01","date_gmt":"2020-06-01T19:52:01","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=6224"},"modified":"2020-06-01T12:55:22","modified_gmt":"2020-06-01T19:55:22","slug":"debugging-the-sipeed-maixduino-board-with-jtag-and-visualgdb","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/tutorials\/arduino\/maixduino\/","title":{"rendered":"Debugging the Sipeed Maixduino board over JTAG with VisualGDB"},"content":{"rendered":"

This tutorial shows how to create a basic Arduino-based application for the Sipeed Maixduino board and debug it with JTAG. We clone the “selfie” sample from the Maixduino platform, that takes pictures using the included camera and shows them on the LCD screen, program it into the FLASH memory using the COM port, and then show how to debug the board with JTAG.<\/p>\n

In order to debug the board over JTAG, make sure you solder the following pins of the on-board K210 module to a JTAG20 cable (you can skip this for now, as we will first show how to build and upload the program using the on-board COM port):<\/p>\n\n\n\n\n\n\n\n\n\n\n
Pin Name<\/td>\nPin Number<\/td>\nJTAG Signal<\/td>\nJTAG20 Pin<\/td>\n<\/tr>\n
IO0\/JTAG_TCK<\/td>\n1<\/td>\nTCK<\/td>\n9<\/td>\n<\/tr>\n
IO1\/JTAG_TDI<\/td>\n2<\/td>\nTDI<\/td>\n5<\/td>\n<\/tr>\n
IO2\/JTAG_TMS<\/td>\n3<\/td>\nTMS<\/td>\n7<\/td>\n<\/tr>\n
IO3\/JTAG_TDO<\/td>\n4<\/td>\nTDO<\/td>\n13<\/td>\n<\/tr>\n
RST<\/td>\n55<\/td>\nSRST<\/td>\n15<\/td>\n<\/tr>\n
3V3<\/td>\n(see power header on the board)<\/td>\nVDD<\/td>\n1<\/td>\n<\/tr>\n
GND<\/td>\n(see power header on the board)<\/td>\nGND<\/td>\n4<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Use the schematic below to double-check the wiring:\"\"<\/a>The final JTAG setup should look as shown below:\"\"<\/a>Now we will show how to create an Arduino-based VisualGDB project for Maixduino and upload it to the board. If you do not want to debug the board, you can skip the JTAG wiring setup and simply use the on-board COM port to upload the program to the FLASH memory.<\/p>\n

    \n
  1. Start Visual Studio and open the VisualGDB’s Arduino Project Wizard:\"\"<\/a><\/li>\n
  2. Enter the name and location for your project: \"\"<\/a><\/li>\n
  3. On the first page of the wizard select “Clone one of the sample sketches”: \"\"<\/a><\/li>\n
  4. On the next page of the wizard select the Sipeed Maixduino Board<\/strong>. If it does not appear, make sure you are using VisualGDB 5.5 or later and the Maixduino checkbox below the target list is checked: \"\"<\/a><\/li>\n
  5. If this is the first time you create a project for Maixduino, click “Install” to automatically download the necessary Arduino packages. Once all the packages are ready, you will be able to select the board and proceed to the next page. As we will first use the on-board COM port to program the FLASH memory, make sure you select the correct port before proceeding to the next page: \"\"<\/a><\/li>\n
  6. On the Project Sample page, pick the selfie<\/strong> sample and click “Next”:\"\"<\/a><\/li>\n
  7. Finally, you can set the debug settings for the project. If you don’t have the JTAG wiring setup yet, simply choose “built-in GDB simulator”. It won’t do any meaningful simulation for the K210 target, but will allow completing the wizard: \"\"<\/a> We will show the debug settings for JTAG-based debugging later in the tutorial.<\/li>\n
  8. Press “Finish” to create the sample project, then try building it with Ctrl-Shift-B. As of June 2020, the build will fail due to a missing implementation for Camera::setRotation(uint8_t)<\/strong>:\"\"<\/a><\/li>\n
  9. You can fix the build error by navigating to definition of Sipeed_OV2640<\/strong> and adding an empty implementation of setRotation()<\/strong> to it:\n
        virtual void setRotation(uint8_t rotation) { }<\/pre>\n
    \"\"<\/a>Note that as of June 2020, the Maixduino Arduino platform implementation does not properly generate dependency files, so changing any of the sources will rebuild the entire project.<\/li>\n
  10. Once the project is built, right-click on it in Solution Explorer and select “Program FLASH memory”:\"\"<\/a><\/li>\n
  11. VisualGDB will invoke the Maixduino FLASH script to automatically program the FLASH memory via the COM port. You can change the COM port number via the first page of VisualGDB Project Properties. Once the FLASH is programmed, the on-board LCD screen will show the live feed from the camera:\"\"<\/a><\/li>\n
  12. Before you go further, we recommend patching the <Documents>\\ArduinoData\\packages\\Maixduino\\hardware\\k210\\0.3.11\\platform.txt<\/strong> file as shown below (you can find out the exact path by opening any file from the Sipeed Maixduino Board<\/strong> folder in Solution Explorer and checking its\u00a0 full path in Visual Studio):\n
      \n
    1. Remove “-Os” from compiler.both.flags<\/strong> and add it to compiler.c.flags<\/strong> and compiler.cpp.flags<\/strong>.<\/li>\n
    2. Add “-Os” to compiler.c.flags<\/strong> and compiler.cpp.flags<\/strong>.<\/li>\n
    3. Add “-MMD” to compiler.c.flags<\/strong>, compiler.cpp.flags<\/strong> and compiler.S.flags<\/strong><\/li>\n<\/ol>\n
      This will enable dependency file generation, greatly reducing the build time, and will allow VisualGDB to disable optimization for debug builds if enabled via VisualGDB Project Properties: \"\"<\/a><\/li>\n
    4. Now we will show how to debug the Maixduino board with JTAG. Make sure you followed the JTAG wiring setup instructions from the beginning of the page, connect your JTAG debugger to the board and open VisualGDB Project Properties. Select the probe in the “Debug using” field an click “Test”: \"\"<\/a>If everything is connected correctly, the test will succeed:\"\"<\/a>We have tested the Maixduino board with both Olimex ARM-USB-OCD-H and Segger J-Link debuggers (both using OpenOCD).<\/li>\n
    5. Try adding a simple frame counter variable to loop()<\/strong>, set a breakpoint there and begin debugging. VisualGDB will load the program into the Maixduino RAM and will start debugging:\"\"<\/a>Note that the debugging experience using the K210 OpenOCD is less reliable compared to ARM (and other RISC-V) devices (see the end of this tutorial<\/a> for details). Although the regular breakpoints and stepping work, we have found the following debugging limitations during our tests:\n