Hi, I'm attempting to modify the basic firmware, and I'm progressing quite well however there are a couple of sneaky scenarios which require a lower level debugging capability. Can you please advise how you debug the firmware, on the device? I've modified the firmware to call 'AudioMoth_setupSWOForPrint' at the end of AudioMoth_initialise() and added a couple of debug statements such as printf("Debugging enabled"); Throughout the code, being executed. These changes, along with my other alterations were then successfully flashed to the AudioMoth device. I've then connected my J-Link debug probe https://www.segger.com/products/debug-probes/j-link/ , which appears to support the EFM32WG980F256 chip. https://www.segger.com/downloads/supported-devices.php 1. PC -> USB -> AudioMoth USB plug (normal USB connection for an AudioMoth) 2. PC -> USB -> JLink Debug Probe -> SWD via Dupont Connectors -> AudioMoth Debug pads Here's a couple of photos to highlight what I'm doing. Sure, those connections are soldered a little rough but have been verified to be fine. As a simple dump, here's what I'm using. I'm expecting you're doing something similar when modifying the firmware. JLinkExe
SEGGER J-Link Commander V6.52c (Compiled Oct 11 2019 15:44:58)
DLL version V6.52c, compiled Oct 11 2019 15:44:50
....
Type "connect" to establish a target connection, '?' for help
J-Link> connect
Please specify device / core. <Default>: EFM32WG980F256
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF> S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "EFM32WG980F256" selected.
Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 003BB923 TPIU-Lite
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
J-Link> SWORead
0 bytes read (0 bytes in host buffer)
J-Link> SWOView
Receiving SWO data @ 4000 kHz.
Data from stimulus port 0:
-----------------------------------------------
Occasionally I'll get SWO output, but its all garbled and meaningless. On other hardware I would think this was a mismatch of the receiving clock (4000 kHz), but maybe I'm attacking this incorrectly. I appreciate this is getting down into the lower levels of core programming on the device but I suspect other users may wish to also understand these debugging aspects when modifying the firmware to suit their needs also. Without a device level debugging capability the only way to check out changes is to flash the device with extra LED flashes to highlight state changes, or log to the microSD via the AudioMoth_appendFile operation. Which SWO debug probe do you use to validate changes to the base firmware? What code changes do you make to enable debugging? Are there Simplicity Studio changes which you utilise to support debugging on the device? Are you debugging the code off the device instead, on a PC using a 32-bit ARM emulator or 32-bit x86 target toolchain? Are you implementing Unit Testing on your version of the firmware?
Hi, Did the LED go green, and then stay green, when the you played the chime tone to the device? If so, then it has the correct firmware installed, and is correctly configured.
If you then move the switch to CUSTOM you should see the green flashing LED whilst the AudioMoth waits until the scheduled recording time. If the green LED is flashing then the batteries are good and the AudioMoth can write to the SD card are okay.
The AudioMoth will start making recordings at 20:00 BST and will stop at 06:30 BST. Whilst it is recording the red LED will be on almost continuously but will be flickering a little. If you are already inside this period when you move the switch to CUSTOM the AudioMoth will wait until the scheduled start time (i.e. the next time that the minutes divisible by 5, such as 20:05 BST or 20:10 BST). The recordings will be 297 seconds long with 3 second gaps regardless of whether there are any bats detecting - there is no triggering mechanism - the AudioMoth makes recordings whether or not there is anything there.
The green light does not stay green. It just blinks every two seconds while I play the chime
Are you using a Mac for formatting cards? I was getting no recordings for some cards. The red and green LEDs would blink once at the proper recording time, then the green LED would resume blinking, waiting for the next recording time. A card formatting problem was discovered:
https://www.openacousticdevices.info/support/sd-card-support/formatting-on-mac
If not on Mac, maybe there is a utility or similar way to get more formatting details for your cards to check this.
Did this AudioMoth come from the Bat Conservation Trust specifically in order to take part in this year's British Bat Survey? If not it won't have the correct firmware and won't respond to the chime. It sounds like it has the correct firmware, but the best way to check is to download the Time App from the website (https://www.openacousticdevices.info/config). The firmware is displayed when the device is plugged into a USB socket and the switch is in USB position. The correct firmware is AudioMoth-BritishBatSurvey 1.0.1.
Assuming it has the correct firmware, and it sounds like it does if the green LED flashes every two seconds when you put it in DEFAULT mode, then the problem is that it can't hear the chime tone correctly when you play it from the website. Can you hear the sound? It should be medium volume and the AudioMoth needs to be reasonably close to the speaker. Try experimenting at different distances? Are you using a laptop or mobile phone to play the sound? Either should work fine. Large desktop speakers may not reproduce the 20kHz data signal very well.