Topic: Nucleo STM32L476RG Memory Write Failure!

Tagged: VisualGDB NUCLEO-STM32L476RG

This topic has 7 replies, 2 voices, and was last updated 8 years, 9 months ago by support.

Viewing 8 posts - 1 through 8 (of 8 total)

Author

Posts
March 10, 2016 at 16:15 #7748

walt71100
Participant

Can anyone assist with resolving this issue.

http://stackoverflow.com/questions/35904027/visualgdb-with-stm32l476rg-nucleo

Thank you in advance!

Walt

March 11, 2016 at 19:18 #7754

support
Keymaster

Hi,

Sure. Please see the answer on StackOverflow.

March 12, 2016 at 04:20 #7764

walt71100
Participant

Hi Bazis,
Thanks for your feedback. Below is output I see in the “All GDB Interaction” window when the error occurs.
If you don’t mind, I’d like to use this forum for working through the issue, and then post a summary of the final solution back to StackOverflow. This forum provides more room for log details, etc.
I formatted a few words in bold near the bottom of the text block below, where I believe the write error occurs.
===
Your VisualGDB trial expires in 29 days!
C:\SysGCC\arm-eabi\bin\arm-eabi-gdb.exe –interpreter mi C:\Users\walt71100\src\STM32\SerialTest\STM32L4Demo/Debug/STM32L4Demo.elf
-gdb-version
=thread-group-added,id=”i1″
GNU gdb (GDB) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “–host=i686-pc-mingw32 –target=arm-eabi”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type “help”.
Type “apropos word” to search for commands related to “word”…
Reading symbols from C:\Users\walt71100\src\STM32\SerialTest\STM32L4Demo/Debug/STM32L4Demo.elf…
done.
GNU gdb (GDB) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “–host=i686-pc-mingw32 –target=arm-eabi”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type “help”.
Type “apropos word” to search for commands related to “word”.
OK
-list-features
^done,features=[“frozen-varobjs”,”pending-breakpoints”,”thread-info”,”data-read-memory-bytes”,”breakpoint-notifications”,”ada-task-info”,”language-option”,”info-gdb-mi-command”,”undefined-command-error-code”,”exec-run-start-option”]
-gdb-set stop-on-solib-events 1
OK
-gdb-set disassembly-flavor intel
No symbol “disassembly” in current context.
-gdb-set print demangle off
OK
-break-insert -f main
^done,bkpt={number=”1″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”0x08001036″,func=”main()”,file=”LEDBlink.cpp”,fullname=”C:\\Users\\walt71100\\src\\STM32\\SerialTest\\STM32L4Demo\\LEDBlink.cpp”,line=”14″,thread-groups=[“i1″],times=”0″,original-location=”main”}
target remote :3333
&”target remote :3333\n”
Remote debugging using :3333
=thread-group-started,id=”i1″,pid=”42000″
=thread-created,id=”1″,group-id=”i1″
Reset_Handler () at C:\Users\walt71100\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:944
944 for (pSource = &_sidata, pDest = &_sdata; pDest != &_edata; pSource++, pDest++)
*stopped,frame={addr=”0x0800080c”,func=”Reset_Handler”,args=[],file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c”,line=”944″},thread-id=”1″,stopped-threads=”all”
OK
info shared
&”info shared\n”
No shared libraries loaded at this time.
OK
mon halt
&”mon halt\n”
OK
mon reset init
&”mon reset init\n”
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0800080c msp: 0x20020000
adapter speed: 4000 kHz
OK
load
&”load\n”
Loading section .isr_vector, size 0x188 lma 0x8000000
+download,{section=”.isr_vector”,section-size=”392″,total-size=”58290″}
Loading section .text, size 0xfc4 lma 0x8000188
+download,{section=”.text”,section-size=”4036″,total-size=”58290″}
Loading section .init_array, size 0x4 lma 0x800114c
+download,{section=”.init_array”,section-size=”4″,total-size=”58290″}
Loading section .fini_array, size 0x4 lma 0x8001150
+download,{section=”.fini_array”,section-size=”4″,total-size=”58290″}
Loading section .data, size 0x4 lma 0x8001154
+download,{section=”.data”,section-size=”4″,total-size=”58290″}
Start address 0x800080c, load size 4440
Transfer rate: 1 KB/sec, 888 bytes/write.
OK
-data-evaluate-expression “sizeof(void *)”
^done,value=”4″
-data-evaluate-expression “sizeof(int)”
^done,value=”4″
-data-evaluate-expression “sizeof(short)”
^done,value=”2″
-data-evaluate-expression “sizeof(long)”
^done,value=”4″
-data-evaluate-expression “sizeof(long long)”
^done,value=”8″
-data-evaluate-expression “sizeof(char)”
^done,value=”1″
-data-evaluate-expression “sizeof(wchar_t)”
No symbol “wchar_t” in current context.
-data-evaluate-expression “sizeof(float)”
^done,value=”4″
-data-evaluate-expression “sizeof(double)”
^done,value=”8″
-data-evaluate-expression “sizeof(long double)”
^done,value=”8″
info target
&”info target\n”
Symbols from “C:\Users\walt71100\src\STM32\SerialTest\STM32L4Demo\Debug\STM32L4Demo.elf”.
Remote serial target in gdb-specific protocol:
Debugging a target over a serial line.
While running this, GDB does not access memory from…
Local exec file:
`C:\Users\walt71100\src\STM32\SerialTest\STM32L4Demo\Debug\STM32L4Demo.elf’, file type elf32-littlearm.
Entry point: 0x800080c
0x08000000 – 0x08000188 is .isr_vector
0x08000188 – 0x0800114c is .text
0x0800114c – 0x08001150 is .init_array
0x08001150 – 0x08001154 is .fini_array
0x20000000 – 0x20000004 is .data
0x20000004 – 0x20000024 is .bss
OK
-break-insert -f C:/Users/walt71100/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:961
&”No line 961 in file \”C:/Users/walt71100/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c\”.\n”
^done,bkpt={number=”2″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”<PENDING>”,pending=”C:/Users/walt71100/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:961″,times=”0″,original-location=”C:/Users/walt71100/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:961″}
-file-list-exec-source-files
^done,files=[{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c”},{file=”LEDBlink.cpp”,fullname=”C:\\Users\\walt71100\\src\\STM32\\SerialTest\\STM32L4Demo\\LEDBlink.cpp”},{file=”c:\\sysgcc\\arm-eabi\\arm-eabi\\sys-include\\machine/_default_types.h”,fullname=”c:\\sysgcc\\arm-eabi\\arm-eabi\\sys-include\\machine\\_default_types.h”},{file=”c:\\sysgcc\\arm-eabi\\arm-eabi\\sys-include/stdint.h”,fullname=”c:\\sysgcc\\arm-eabi\\arm-eabi\\sys-include\\stdint.h”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/CMSIS_HAL/Device/ST/STM32L4xx/Include/stm32l476xx.h”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\CMSIS_HAL\\Device\\ST\\STM32L4xx\\Include\\stm32l476xx.h”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/STM32L4xx_HAL_Driver/Inc/stm32l4xx_hal_gpio.h”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\STM32L4xx_HAL_Driver\\Inc\\stm32l4xx_hal_gpio.h”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/CMSIS_HAL/Include/core_cm4.h”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\CMSIS_HAL\\Include\\core_cm4.h”},{file=”../../../../../../../newlib-2.2.0/newlib/libc/misc/init.c”,fullname=”/q/gnu/auto/newlib-bu-2.24+gcc-5.3.0+gmp-5.1.3+mpfr-3.1.2+mpc-1.0.2+newlib-2.2.0-arm-eabi/arm-eabi/thumb/cortex_m4/newlib/libc/misc/../../../../../../../newlib-2.2.0/newlib/libc/misc/init.c”},{file=”system_stm32l4xx.c”,fullname=”C:\\Users\\walt71100\\src\\STM32\\SerialTest\\STM32L4Demo\\system_stm32l4xx.c”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/CMSIS_HAL/Include/core_cmInstr.h”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\CMSIS_HAL\\Include\\core_cmInstr.h”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_rcc.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\STM32L4xx_HAL_Driver\\Src\\stm32l4xx_hal_rcc.c”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_gpio.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\STM32L4xx_HAL_Driver\\Src\\stm32l4xx_hal_gpio.c”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/CMSIS_HAL/Include/core_cmInstr.h”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\CMSIS_HAL\\Include\\core_cmInstr.h”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/CMSIS_HAL/Include/core_cm4.h”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\CMSIS_HAL\\Include\\core_cm4.h”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\STM32L4xx_HAL_Driver\\Src\\stm32l4xx_hal_cortex.c”},{file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\STM32L4xx_HAL_Driver\\Src\\stm32l4xx_hal.c”}]
-break-delete 2
OK
-break-insert -f C:\Users\walt71100\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32\STM32L4xxxx\StartupFiles\startup_stm32l476xx.c:961
&”No line 961 in file \”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c\”.\n”
^done,bkpt={number=”3″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”<PENDING>”,pending=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c:961″,times=”0″,original-location=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c:961″}
-break-delete 3
OK
Warning: your GDB version refuses to accept fully-qualified file names.
VisualGDB is now defaulting to file name-only syntax.
This might cause strange bugs if you have multiple files with the same name in different directories.
It is highly recommended to update your GDB version!
It is highly recommended to update your GDB version!
-break-insert -f startup_stm32l476xx.c:961
&”No line 961 in file \”startup_stm32l476xx.c\”.\n”
^done,bkpt={number=”4″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”<PENDING>”,pending=”startup_stm32l476xx.c:961″,times=”0″,original-location=”startup_stm32l476xx.c:961″}
-break-info 4
^done,BreakpointTable={nr_rows=”1″,nr_cols=”6″,hdr=[{width=”7″,alignment=”-1″,col_name=”number”,colhdr=”Num”},{width=”14″,alignment=”-1″,col_name=”type”,colhdr=”Type”},{width=”4″,alignment=”-1″,col_name=”disp”,colhdr=”Disp”},{width=”3″,alignment=”-1″,col_name=”enabled”,colhdr=”Enb”},{width=”10″,alignment=”-1″,col_name=”addr”,colhdr=”Address”},{width=”40″,alignment=”2″,col_name=”what”,colhdr=”What”}],body=[bkpt={number=”4″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”<PENDING>”,pending=”startup_stm32l476xx.c:961″,times=”0″,original-location=”startup_stm32l476xx.c:961″}]}
-break-after 4 0
OK
-break-insert -f C:/Users/walt71100/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:20
^done,bkpt={number=”5″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”0x08000280″,func=”NMI_Handler”,file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c”,line=”20″,thread-groups=[“i1″],times=”0″,original-location=”C:/Users/walt71100/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:20″}
-break-info 5
^done,BreakpointTable={nr_rows=”1″,nr_cols=”6″,hdr=[{width=”7″,alignment=”-1″,col_name=”number”,colhdr=”Num”},{width=”14″,alignment=”-1″,col_name=”type”,colhdr=”Type”},{width=”4″,alignment=”-1″,col_name=”disp”,colhdr=”Disp”},{width=”3″,alignment=”-1″,col_name=”enabled”,colhdr=”Enb”},{width=”10″,alignment=”-1″,col_name=”addr”,colhdr=”Address”},{width=”40″,alignment=”2″,col_name=”what”,colhdr=”What”}],body=[bkpt={number=”5″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”0x08000280″,func=”NMI_Handler”,file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c”,line=”20″,thread-groups=[“i1″],times=”0″,original-location=”C:/Users/walt71100/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:20″}]}
-break-after 5 0
OK
info symbol 0x8000280
&”info symbol 0x8000280\n”
NMI_Handler + 4 in section .text
OK
info line *0x8000280
&”info line *0x8000280\n”
Line 20 of “C:\Users\walt71100\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c” starts at address 0x8000280 <NMI_Handler+4> and ends at 0x8000282 <NMI_Handler+6>.
OK
-exec-continue
Note: automatically using hardware breakpoints for read-only addresses.
^running
*running,thread-id=”all”
Program received signal
SIGTRAP, Trace/breakpoint trap.
HardFault_Handler () at C:\Users\walt71100\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c:28
28 asm(“bkpt 255″);
*stopped,reason=”signal-received”,signal-name=”SIGTRAP“,signal-meaning=”Trace/breakpoint trap”,frame={addr=”0x08000290″,func=”HardFault_Handler”,args=[],file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c”,line=”28″},thread-id=”1″,stopped-threads=”all”
-data-read-memory-bytes 0x8000290 4
^done,memory=[{begin=”0x08000290″,offset=”0x00000000″,end=”0x08000294″,contents=”ffbe00bf”}]
-stack-list-frames –thread 1
^done,stack=[frame={level=”0″,addr=”0x08000290″,func=”HardFault_Handler”,file=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32/STM32L4xxxx/StartupFiles/startup_stm32l476xx.c”,fullname=”C:\\Users\\walt71100\\AppData\\Local\\VisualGDB\\EmbeddedBSPs\\arm-eabi\\com.sysprogs.arm.stm32\\STM32L4xxxx\\StartupFiles\\startup_stm32l476xx.c”,line=”28″},frame={level=”1″,addr=”0xfffffff9″,func=”<signal handler called>”},frame={level=”2″,addr=”0x00000000″,func=”??”}]
-stack-list-arguments –thread 1 0
^done,stack-args=[frame={level=”0″,args=[]},frame={level=”1″,args=[]},frame={level=”2″,args=[]}]

March 13, 2016 at 19:52 #7769

walt71100
Participant

Bazis,

I really like the VisualStudio IDE, and the features provided by VisualGDB. I want to start using this on the STM32 Nucleo board, but can’t get going until I’m past this memory write failure issue. Can you provide any more insight into what may be wrong in my setup?

Thank you,

Walt

March 13, 2016 at 19:54 #7770

support
Keymaster

Hi,

It looks like an obvious bug in our device definitions, so there is no action needed on your side, we’ll simply release a BSP update fixing this within the next 24 hours.

March 13, 2016 at 20:15 #7771

support
Keymaster

OK, the update is out. Please update your BSP via Tools->Embedded Tools Manager.

March 14, 2016 at 02:54 #7773

walt71100
Participant

Thank you very much, the BSP update fixed the problem.

March 15, 2016 at 06:11 #7777

support
Keymaster

Good to know it worked. Let us know if you encounter further problems.
Author

Posts

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.