If we would like to modify the ADuCM355 code in order customize what are the software tools that you recommend? What do you use for the programmer or debugger? J-Link? for the IAR C-SPY?
The software examples which will be released are developed in IAR Embedded Workbench. I recommend using this tool. In terms of the programmer/debugger, we tested the system with J-Link and also CMSIS-DAP (from mbed). In fact, there is a CMSIS-DAP debugger included on the ADICUP3029 board and it can be used to program the ADuCM355 daughter boards. You can find information about how to do this HERE
Are you able to tell me when the software will be released? I have a CN-0429 board that is not working and thought that if I tried flashing it, new code it might start working again. The board doesn't ever initialize no matter what position it is placed on the ADuCM Arduino Interposer board.
Can you explain more about your setup? Do you have a picture (or few you can share)? What IDE tools are you trying to use for the programming? What debugger are you using when you are trying to upload the code again?
What happened to the initial code on the CN0429 where you believe it got corrupt? Were you trying to reprogram it with any your custom code?
This is the setup that I have using the CN-0429 gas sensor board, ADuCM355 Arduino Interposer board and the EVAL-ADICUP3029.
The board that is seen in position 2 will not initialize as seen with the other two boards in position 1 and 4. My guess it that the code got corrupted due to ESD, possibly so I was going to try to flash new code to it to see it that solved my problem.
I see now that all the code is available on line and I have downloaded and installed everything. I am using IAR with CMSIS-DAP debugger. I have cut the 3 traces on the EVAL-ADICUP3029 as described in the user manual and using the ribbon cable to connect the debugger to the Interposer board.
I have not had luck so far getting the code for the ADuCM355 onto the board. I was hoping for a little bit more instruction on how to do with with IAR. I have very little background with firmware and using IDE tools.
My first question is what configuration do I need to set it to, Release or debug?
When I was in debug mode I was able to compile the code but unsuccessful downloading and debugging. The following is from the Debug Log;
Thu Jan 31, 2019 11:13:20: IAR Embedded Workbench 8.32.2 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\bin\armproc.dll) Thu Jan 31, 2019 11:13:20: Loaded debugee: C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\iar\Debug\Exe\M355_CN0429.out Thu Jan 31, 2019 11:13:20: Download error at 0x00000000: downloading into non-writable memory. Thu Jan 31, 2019 11:13:20: Download error at 0x00000000: memory write failed. Thu Jan 31, 2019 11:13:20: The downloaded program doesn't seem to match the expected memory layout of the target system: Thu Jan 31, 2019 11:13:20: There are linked memory segments outside known memory areas or with incompatible memory attributes. Thu Jan 31, 2019 11:13:20: Memory is specified as follows: Thu Jan 31, 2019 11:13:20: 0x00000000 - 0x1FFFFFFF ROM/Flash Thu Jan 31, 2019 11:13:20: 0x20000000 - 0x21FFFFFF RAM Thu Jan 31, 2019 11:13:20: 0x22000000 - 0x23FFFFFF RAM Thu Jan 31, 2019 11:13:20: 0x40000000 - 0x41FFFFFF Uncached/SFR Thu Jan 31, 2019 11:13:20: 0x42000000 - 0x43FFFFFF Uncached/SFR Thu Jan 31, 2019 11:13:20: 0xE0000000 - 0xFFFFFFFF Uncached/SFR Thu Jan 31, 2019 11:13:20: Segments are linked as follows: Thu Jan 31, 2019 11:13:20: 0x00000000 - 0x0000013F ROM/Flash Thu Jan 31, 2019 11:13:20: 0x00000180 - 0x00000197 ROM/Flash Thu Jan 31, 2019 11:13:20: 0x000007FC - 0x000007FF RAM Thu Jan 31, 2019 11:13:20: 0x00000800 - 0x00005D77 ROM/Flash Thu Jan 31, 2019 11:13:20: 0x20000000 - 0x200005C6 RAM Thu Jan 31, 2019 11:13:20: 0x200005C8 - 0x20000BAB RAM Thu Jan 31, 2019 11:13:20: 0x20001C00 - 0x20001FFF RAM Thu Jan 31, 2019 11:13:20: 0x20040000 - 0x2004464F RAM
When I change the configuration to Release ( I am in the understanding that this is what I need in order to program the micro-controller) I am not able to to compile the code. The following is what is found from the Build log file;
Building configuration: M355_CN0429 - Release Updating build tree... AfeTiaLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\AfeTiaLib.h 31 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler AfeAdcLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\AfeAdcLib.h 28 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler AfeWdtLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\AfeWdtLib.h 24 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler AfeDacLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\AfeDacLib.h 28 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler EIS_Test.c Fatal Error[Pe1696]: cannot open source file "ADuCM355_Peri.h" C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\M355_Sensor_Meas.h 29 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler Capa_Test.c Fatal Error[Pe1696]: cannot open source file "ADuCM355_Peri.h" C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\M355_Sensor_Meas.h 29 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler DioLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\DioLib.h 28 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler ClkLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\ClkLib.h 29 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler M355_Sensor_Meas.c Fatal Error[Pe1696]: cannot open source file "ADUCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\M355_Sensor_Meas.c 21 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler M355_calibration.c Fatal Error[Pe1696]: cannot open source file "ADuCM355_Peri.h" C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\M355_calibration.c 20 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler I2cLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\I2cLib.h 27 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler GptLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\GptLib.h 25 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler PwrLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\PwrLib.h 26 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler SpiLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\SpiLib.h 30 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler RstLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\RstLib.h 26 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler MVH3000D_Prog_Functions.c Fatal Error[Pe1696]: cannot open source file "ADUCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\MVH3000D_Prog_Functions.c 18 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler virtual_i2c_interface.c Fatal Error[Pe1696]: cannot open source file "ADUCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\virtual_i2c_interface.c 17 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler UrtLib.c Fatal Error[Pe1696]: cannot open source file "ADuCM355.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\UrtLib.h 36 searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler system.c Fatal Error[Pe1696]: cannot open source file "system.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\IAR\system.c 53 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\IAR\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler startup.c Fatal Error[Pe1696]: cannot open source file "startup.h" C:\Analog Devices\ADuCM355V2.1.0.54\common\IAR\startup.c 48 searched: "C:\Analog Devices\ADuCM355V2.1.0.54\common\IAR\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\" searched: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\c\" current directory: "C:\Users\April.Fisher\Desktop" Error while running C/C++ Compiler Total number of errors: 20 Total number of warnings: 0
Are you able to provide any guidance on how to program the code onto the CN0429?
Thanks in advance,
April
So I think I am getting a little bit further. I didn't have the mbed driver installed. Now that's installed, I have just been working with the debug configuration.
Thu Jan 31, 2019 16:12:06: IAR Embedded Workbench 8.32.2 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\bin\armproc.dll) Thu Jan 31, 2019 16:12:06: Loading the CMSIS-DAP driver Thu Jan 31, 2019 16:12:06: Probe: CMSIS-DAP probe SW module ver 1.17 Thu Jan 31, 2019 16:12:06: Probe: Connecting to DAPLink CMSIS-DAP:0600000041114e45003f3006bcf000500571000097969900 firmware v.1.0 Thu Jan 31, 2019 16:12:06: Emulation layer version 4.42 Thu Jan 31, 2019 16:12:07: Notification to init-after-power-up hookup. Thu Jan 31, 2019 16:12:07: Notification to core-connect hookup. Thu Jan 31, 2019 16:12:07: Connected DAP v1 on SWD. Detected IDCODE=0x2ba01477. Thu Jan 31, 2019 16:12:07: Connecting to TAP#0 DAP AHB-AP-CM port 0 (IDR=0x24770011). Thu Jan 31, 2019 16:12:07: Recognized CPUID=0x412fc231 Cortex-M3 r2p1 arch ARMv7-M Thu Jan 31, 2019 16:12:07: Debug resources: 2 instruction comparators, 1 data watchpoints. Thu Jan 31, 2019 16:12:07: MultiCore: Asynchronous core execution FORCED. Thu Jan 31, 2019 16:12:07: MultiCore: Synchronous core execution DISABLED. Thu Jan 31, 2019 16:12:07: LowLevelReset(hardware, delay 200) Thu Jan 31, 2019 16:12:08: Loaded debugee: C:\Analog Devices\ADuCM355V2.1.0.54\examples\M355_CN0429\iar\Debug\Exe\M355_CN0429.out Thu Jan 31, 2019 16:12:08: The downloaded program doesn't seem to match the expected memory layout of the target system: Thu Jan 31, 2019 16:12:08: There are linked memory segments outside known memory areas or with incompatible memory attributes. Thu Jan 31, 2019 16:12:08: Memory is specified as follows: Thu Jan 31, 2019 16:12:08: 0x00000000 - 0x1FFFFFFF ROM/Flash Thu Jan 31, 2019 16:12:08: 0x20000000 - 0x21FFFFFF RAM Thu Jan 31, 2019 16:12:08: 0x22000000 - 0x23FFFFFF RAM Thu Jan 31, 2019 16:12:08: 0x40000000 - 0x41FFFFFF Uncached/SFR Thu Jan 31, 2019 16:12:08: 0x42000000 - 0x43FFFFFF Uncached/SFR Thu Jan 31, 2019 16:12:08: 0xE0000000 - 0xFFFFFFFF Uncached/SFR Thu Jan 31, 2019 16:12:08: Segments are linked as follows: Thu Jan 31, 2019 16:12:08: 0x00000000 - 0x0000013F ROM/Flash Thu Jan 31, 2019 16:12:08: 0x00000180 - 0x00000197 ROM/Flash Thu Jan 31, 2019 16:12:08: 0x000007FC - 0x000007FF RAM Thu Jan 31, 2019 16:12:08: 0x00000800 - 0x00005D77 ROM/Flash Thu Jan 31, 2019 16:12:08: 0x20000000 - 0x200005C6 RAM Thu Jan 31, 2019 16:12:08: 0x200005C8 - 0x20000BAB RAM Thu Jan 31, 2019 16:12:08: 0x20001C00 - 0x20001FFF RAM Thu Jan 31, 2019 16:12:08: 0x20040000 - 0x2004464F RAM Thu Jan 31, 2019 16:12:08: Download error at 0x00000000: downloading into non-writable memory. Thu Jan 31, 2019 16:12:08: Download error at 0x00000000: memory write failed.
I can't seem to get past this point, hope you can shed some light on this for me.
Is anyone able to help me out with this? Is this a memory mapping issue?