analogdevicesinc / max78xxx-refdes

MAX78000 and MAX78002 Reference Designs

Maxim AI Reference Designs

Start here:

->->-> MAXREFDES178 Wiki Page

->->-> Maxim AI Documentation

->->-> Getting Started with the MAXREFDES178 Cube Camera

max78xxx-refdes's Issues

Missing GPIO0_Handler causing cube camera to hang

The last SDK release consolidated each of the PushButton source files into the MiscDrivers library. Long story short, to make these changes compatible with all micros supported in the SDK, the GPIOx_IRQHandler's were removed from pb.c and instead weak definitions of the relevant GPIOx_IRQHandler's used by each of the push buttons was provided in each board.c file. Since the MAX32665/MAXREFDES178 does not have any push buttons connected to GPIO0 a weak definition of GPIO0_IRQHandler is not provided for GPIO0. However, it appears there are several other interrupt sources connected to GPIO0 that relied on the definition of GPIO0_IRQHandler in the old version of pb.c. Since the GPIO0_IRQHandler definition is no longer provided in the BSP this is causing the code to hang. To fix this, a GPIO0_IRQHandler should be defined somewhere in each of these projects to support these interrupt sources.

src/max32666_main.c:184:11: error: too few arguments to function 'MXC_DMA_Init'

In the latest SDK, MAX32665 requires an argument for MXC_DMA_init.
maxrefdes178_max32666 build fails.

/max32666_main.c and max32666_spi_dma.c need to be updated

LED Build Errors, Cube no longer turns on

Today I build ImageCapture on my computer with an updated tool chain and repo (develop). Making (make -r -j 4) the 32666 firmware generated no errors. When I build the 78000 video files, I received warning errors associated with defining the LEDs and some depreciated functions. Since these errors seemed mostly harmless and were part of the updated repo, I commented out line 114 "PROJ_CFLAGS+=-Werror" in the Makefile which treats all warnings as errors. I've seen this line commented out in previous releases of the repo and believed that since everything was updated, these errors were known and should not interfere with the program. I also received the same errors when building cats-dogs video. I repeated this process with the ImageCapture and cats-dogs audio files.

I sent the attached ImageCapture files to another user who I taught how to flash the firmware onto the cube. First we put the max32625pico_32630hsp.bin file onto the MAXDAP-TYPE-C which is advised here in the readme. This resulted in the correct GITSHA via link.

I watched him do this and we followed the tutorials and completed all of the steps correctly. First we flashed the video and audio and made sure to be in the correct debug settings. we had the MAXDAP facing the screen with the perpendicular Micro-USB port down as it shows here. We did this first and not the 32666 by following the instructions here. We received a mismatched checksum error but successfully flashed both.
We then flipped the MAXDAP-TYPE-C so that it was facing away from the screen and the perpendicular Micro-USB port was up as it shows here. When we flashed this, the cube went black, had no flashing lights, and never turned back on.

We did a fresh install of develop repo on his computer and had him build cats-dogs which resulted in the same build errors. He flashed cats-dogs 32666 and did not receive the checksum error, though his screen did not turn back on and the cube seemed to be entirely unresponsive.

Attached is my build of the ImageCapture that I sent along with my msys outputs from the builds. Additionally, I have the 32666 and (un)edited video build outputs from cats-dogs as well. I am confused since there were no errors in the 32666 build so I am not sure why the cube would not turn back on and simply have "No video/audio comm". Additionally, when I updated the repo, no files were changed. These were the same files I had been successfully using in the past, though now built with an updated tool chain? I'm confused what could have changed. Will we be able to get the cube to turn back on with an older version of the tool chain and/or the repo?

Sorry for linking the directions everywhere, just wanted to cover the basics. Thanks in advance!
refdes_issue_07.20.23.zip

Make error

Resetting the Video/Audio flash via jumper cables

Hi, both of my cube works, but due to a bug the code cannot run past a line.
I have made it once to reset the two max78000s and re-ran a code. However, similar thing happened again and I need to reset them.
I connected the max78000 with a jumper cable via pico adapter and put the erase.act file into it, however, regardless of battery/power, the erase.act will transfer and daplink will remount.
This process does not erase what is programmed, hence I cannot reprogram the cube from a buggy program. Would there anything I can do else?

Unable to build with the MAX32666 source code with the latest version 1.1.0-119 2022-08-07

Unable to build the MAX32666 source code provided for the Cats and Dogs example.

Here is the latest MaximSDK Updated versions:

Here is the error I get from MinGW and VS code:

msblGenOSX missing

Hi, I am trying to build this project for MAXREFDES178 in an Intel Mac environment.
However, without the file, msblGenOSX, it fails to build.
I guess this is the executable that generates the Maxim secure bootloader (.msbl) which can be flashed to the cube. Do you have a mac os version for this?

/bin/sh: /Users/USERNAME/refdes/maxrefdes178-CatsDogs/maxrefdes178_max32666/../../external/msblGenOSX: No such file or directory

openOCD error

I got an error from openOCD and the cube does not respond.
Below is the error.
Is there a way to solve this?

xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-03-25-19:34)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
DEPRECATED! use 'adapter srst delay' not 'adapter_nsrst_delay'
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: FW Version = 1.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 0 TDI = 0 TDO = 0 nTRST = 0 nRESET = 0
Info : CMSIS-DAP: Interface ready
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x2ba01477
Info : [max32xxx.cpu] Cortex-M4 r0p1 processor detected
Info : [max32xxx.cpu] target has 6 breakpoints, 4 watchpoints
Info : [max32xxx.cpu] external reset detected
Info : starting gdb server for max32xxx.cpu on 3333
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x01000003 pc: 0x000001f2 msp: 0xffffffd8
Warn : Flash driver of max32xxx.flash does not support free_driver_priv()
Warn : Flash driver of max32xxx.flash1 does not support free_driver_priv()
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-03-25-19:34)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
DEPRECATED! use 'adapter srst delay' not 'adapter_nsrst_delay'
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: FW Version = 1.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 0
Info : CMSIS-DAP: Interface ready
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x2ba01477
Info : [max32xxx.cpu] Cortex-M4 r0p1 processor detected
Info : [max32xxx.cpu] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for max32xxx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Warn : [max32xxx.cpu] Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x000001b4 msp: 0x20008400
** Programming Started **
Warn : Flash protection not supported on this device
Warn : Flash protection not supported on this device
Error: timeout waiting for algorithm, a target reset is recommended
Error: error -902 executing max32xxx flash write algorithm
Error: error writing to flash at address 0x10000000 at offset 0x00000000
** Programming Failed **
shutdown command invoked
Warn : Flash driver of max32xxx.flash does not support free_driver_priv()
Warn : Flash driver of max32xxx.flash1 does not support free_driver_priv()

UART connections

Hi,

I see that the block diagram of the cube shows that the audio and video boards are connected to each other via UART. Is there any minimalistic example for UART communication between the boards? Also, where can I find more about which UART pins are connected?

Thanks.