MAX78000

This is a collection of tips, tricks and questions about the MAX7800 and MAX78000FTHR form Maxim.

The MAX78000

If you are new to the MAX78000 and the Maxim Micro IDE this shall give you some hints. For the Software a two-part article will be provided by Elektor to get you started. As this article is written here, we will collect a series of tips and tricks to even support you further. The first one we like to give is the Elektor GitHub repository, which contains the sample projects from our software article. Head over to GitHub and have a look.

No register view for the internal peripherals while debugging?

If you debug your project you will realize that the register and peripherals are not shown. The reason for this is the missing SVD file path inside the Eclipse projects. Currently this file is not included to any project, generated with a wizard or the supplied demo projects by Maxim. To solve this, you need to add the appropriate path to your project. Open the Build settings with the small cog wheel in the Eclipse IDE. You should be presented with a window as seen in Figure 1. Switch the tab to SVD path, as seen in Figure 2, and navigate to the path shown, assuming you used the default installation path.

Apply this path and within your next debug session you will be able to use the register viewer for the included peripherals.

Discussion (5 comments)

Detlef Osteroth 3 years ago

Hi,
I bought the Elector MAX78000FTHR Bundle (book and FTHR board.
After having installed the Maxim SDK and trying to run "Hello World " example I get the following error message when building the project:

Cannot run program "make": Launching failed

Error: Program "make" not found in PATH
PATH=[C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program......
and so on

I assume the installation of the SDK did not properly set the correct path to the necessary MAXIM toolchain but
1. I can not find in Eclipse the possibility to modify the search PATH to find the "make" program.
2. where do I find the "make" program?

Any help is welcome. I hope that I do not need to put aside this astonishing board because I can't get the toolchain working.

0 Comment(s)

SeanW 3 years ago

Whenever I try to run a project from within Eclipse I get a "problem occurred" dialog (see screen shot).

I am using Windows 10 on VirtualBox running on a Mac. I have passed through the USB device and can see the COM port and drive.

I've also tried the command line instructions from https://github.com/MaximIntegratedAI/MaximAI_Documentation/tree/master/MAX78000_Feather which has a similar output to the screen shot. A similar thing happens -- when I run the "openocd" command it doesn't show the "listening" line, it just exits immediately.

Not sure what I should be doing differently and would appreciate any pointers.

ucdev-running-2021-05-12-08-08-07.png (115kb)

fishbeetle 3 years ago

I found you sometimes need to reset the 78000 prior to attempting a download. That worked for me anyway. Great error message eh ;-)

SeanW 3 years ago

Thanks. I've been playing with resetting and USB filters to no avail.

When I run that "openocd -f interface/cmsis-dap.cfg -f target/max78000.cfg -s/c/MaximSDK/Tools/OpenOCD/scripts --debugcommand I see some flashing lights on the board and the debug output says that "dap init" failed with error code -4, which in the openocd source seems to mean "it failed".

Any idea how to generate a .hex file that I could copy to the DAP drive? Or is there a firmware update somewhere? When I do a "make" all I get is a .map and a .elf, which do nothing when copied to the drive.

I was able to go through the maintenance mode and wipe everything in case it was as a result of the problem the documentation mentions which didn't help other than now I have a device that does nothing.

1 Attachment(s) 1 Comment(s)

Peter Drescher 3 years ago

I think my board has a bug.
The DAPLINK is also not working.
If I try to copy a compiled bin file to the drive I get a FAIL.TXT.

Mathias Clauszen 3 years ago

in this case please contact the Elektor support and start a RMA process for it.

Best Regards

Mathias Claußen

1 Comment(s)

fishbeetle 3 years ago

Thanks for the tip, I can now see the variables. However I'm still also seeing a lot of red underlines in the main.c code pane, even though the code always compiles just fine. The most common is: "type int32_t could not be resolved". Any pointers as to how to clear these up?
Thanks a lot.

Mathias Clauszen 3 years ago

Hi,

this is a known issue with the current SDK provided by Maxim. Please have a look at https://pdfserv.maximintegrated.com/en/an/TUT6245.pdf and read the section "Troubleshooting Unresolved Symbols". Also if you feel this needs to be fixed by maxim head over to their GitHub page and fill an issue ( https://github.com/MaximIntegratedAI )

Best Regards

Mathias Claußen

fishbeetle 3 years ago

Afraid that document was not much help.
I think the real problem is this warning on the Properties -> "Preprocessor Include Paths, Macros etc" dialog:
Orphaned configuration. No base extension cfg exists for ilg.gnumcueclipse.managedbuild.cross.config.elf.debug.1674944962
Any idea how to fix that one?
Thanks again, Steve.

Mathias Clauszen 3 years ago

Hi,

sorry haven't looked into it. I can remember that for one project i tried to fix some includes but it didn't fully resolve the problem. Best is to open an issue at Maxim for this one.

Best Regards
Mathais Claußen

fishbeetle 3 years ago

FYI
I tried what you said and opened an issue with Maxim, they did not respond at all - sadly, pretty much as expected :-(

Mathias Clauszen 3 years ago

Hi fishbeetle,

the lack of support by a company like Maxim is not realy what should be expected in this case. Hope they will get the support in a better shape soon.

Best Regards
Mathias Claußen

1 Comment(s)

Peter Drescher 3 years ago

Ich habe mein Board erhalten und versuche gerade die ersten Schritte.
Das Micro meines Boards ist irgendwie total taub. Wenn man das vorinstallierte Demo startet muss man quasi in das Loch auf der Rückseite des Boards laut reinsprechen damit sich etwas tut.
Ist das normal ?