©2019 Open Acoustic Devices

Oct 21, 2017

software update

9 comments

I have tried to install the new update for the audio moth, I am getting a message windows protected your pc, I have selected run anyway and now McAfee has put it into quarantine with ref number EC!A8359F727218, please can you help me get over this problem.

 

Regards Pete

 

Oct 22, 2017

Hi Andy,

Thanks for that I have now got the software working but now have another problem, I have set the device to 48 sample rate and recorded some sounds but for some reason it is recording at a sample rate of 13428728 Hz, not sure what I am doing wrong.

 

Regards Pete

Oct 28, 2017

Hi Andy,

I am still having problems, I can't run flash on either of my laptops, not sure what I am doing wrong

Oct 28, 2017Edited: Oct 28, 2017

Hi Pete,

Do you have Windows, Mac or Linux? If you have Windows, the first thing you can try, when you get to Step 3, is to make sure that you open the command window in the folder where you downloaded the flash.exe. This can be done in Windows by holding the shift key while clicking the right mouse button over the folder containing flash.exe. This brings up the following menu.

If you click on "Open command window here" and run the flash.exe. It should work.

 

If you are using another operating system other than Windows let us know.

 

Thanks,

Andy

Oct 29, 2017

Hi Andy,

 

I am running windows 10 on both of my laptops, one is a Lenovo the other is a HP, the HP gives me a open command window the Lenovo gives me a open powershow window, the later does not reconise the flash.exe and the HP does but it still tells me that I can not run this app on this PC.

 

Regards Pete.

 

Oct 29, 2017

Hi Pete,

I'll send you an email to arrange a call to get this working. I am putting together a walk though video to help out updating the hardware too.

Thanks Andy

Nov 7, 2017

Hi Andy,

 

that would be great, I have tried but every time I get the message you can not run this app on your pc, my phone number is 07774454266, I am normally home after 16:15 but not on Wednesdays.I have got 10 on order will these already have been sorted for the new software.

 

Regards Pete

Nov 7, 2017

Hi Pete,

Yes, the 10 you ordered will have the latest software.

Thanks,

Andy

New Posts
  • Hi, in all my recordings there's a "clicking" noise (26-28kHz). This is an issue that I had before with some recordings but now the noise is louder and it is present in all recordings. The batteries are Energizer AA (new) and the SD card is the SanDisk Extreme 32GB. Is there Anything I can do to make the "clicking" noise disappear?
  • Amazing work! https://www.openacousticdevices.info/mmoth Clearly it is early days, but obviously so many questions pop into mind ... - Off board Lithium ion battery, with a onboad connecter? (So you can choose any size LiOn? or LiPo? like - https://hobbyking.com/en_us/turnigy-2000mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html ?) - Any Battery life / runtime estimates vs AM1.1? - Cost? Double side so more expensive? - etc, etc, etc ... Anything else to share with us yet??
  • 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?
Before posting, be sure to check the FAQ.