Customer Stories
Blog
How to Buy
Contact Us
About Digi
Leadership
Locations
Awards
Export Policy
Environment
Careers
Investor Relations
IoT Products and Services
Embedded Systems
Digi XBee Ecosystem
Digi XBee RF Modules
Digi XBee Cellular Modems
Digi XBee Gateways
Digi XBee Tools
System-on-Modules
Single Board Computers
IoT Development Kits
Networking
Cellular Routers
Gateways
Infrastructure Management
Console Servers
Serial Connectivity
USB Connectivity
IoT Software and Services
Digi Remote Manager
Wireless Design Services
Professional Services
TrustFence Security Framework
Featured
5G
FirstNet
Private LTE/CBRS
Zigbee
USB Over IP/AnywhereUSB
XCTU
Digi TrustFence
/
Built-in security framework for the IoT
SmartSense
Solutions
Solutions by Application
Public Transit
Traffic Management
Remote Worker
Kiosks and Digital Signage
Branch Networking
Positive Train Control (PTC)
More Applications
Solutions by Technology
The Journey to 5G
Cellular Failover
FirstNet
Private LTE Based on CBRS
SD-WAN
Smart Out-of-Band Management
Zigbee Wireless Mesh Networking
More Technologies
Solutions by Industry
Energy
Smart Cities
Medical
Industrial
Retail
Transportation
Resources
Resource Library
Events
Webinars
Videos
Examples and Guides
Project Gallery
More Resources
Recent News
Press Releases
News Coverage
Security Center
Certifications
Support
Support Services
Support Forum
Product Returns (RMA)
Warranty Registration
Expert Support Login
Knowledge Base
Drivers
Firmware Updates
Documentation
Diagnostics, Utilities & MIBS
Embedded Patches
Sample Applications
Search
Remember
Register
Home
/
Support
/
Support Forum
/
Digi ESP Connect ME 9210 problems even making the simplest thing
Digi Forum
All Activity
Q&A
Questions
Hot!
Unanswered
Tags
Categories
Users
Ask a Question
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.
All categories
Digi Remote Manager
(352)
Python
(963)
RF Solutions and XBee
(7,999)
Digi TransPort
(730)
Digi Connect Cellular
(410)
DAL
(2)
Embedded Devices
(4,057)
Android
(42)
NET+OS
(2,420)
Linux
(897)
Windows CE
(84)
Plug N' Play
(463)
Rabbit
(3,144)
Console Servers
(340)
Modbus and Industrial Automation
(235)
Realport
(579)
Serial Servers
(807)
Satellite Modules
(24)
USB
(1,216)
Serial Cards
(712)
ConnectPort Display
(54)
Feedback/Wish List
(86)
Other/Legacy
(330)
Digi ESP Connect ME 9210 problems even making the simplest thing
0
votes
I'm experiencing problems even making the simplest thing with ESP...
I'm working on a fresh install of Windows 7 32bit
installed ESP
Create a sample project! Hello World
While building i receive a warning
make[1]: warning: -jN forced in submake: disabling jobserver mode.
Than when lunching the debug session using JTAG most of the times I get errors like
WARNING: Failed to read memory @ address 0x01000000
and the download stops at 8 bytes .
When in some case for reasons I do not understand (since i do not anything differently) I get to complete the download.
I resume the halted thread but the application never get even to the initial breakpoint.
The UI says Running / Executing but nothing happens.
connect
me
9210
asked
Jul 19, 2013
in
NET+OS
by
gavello
New to the Community
(
16
points)
reshown
Jan 22, 2014
by
charliek
A couple of other things. Any chance you are running a machine with virtual machines? Devices such as USB do not share well. I run WIN7 32-bit on my main machine and WINXp on a virtual machine. I have found that for me to run ESP on the WINXP machine, the segger debugger daemon process must be Shut down. I also need to unplug and replug the USB cable from the debugger before things will work correctly. Going the other way, I need to shut down the segger daemon and suspend the WINXP VM before switching to the WIN7 machine. I believe it also helps to unplug and plug the USB cable form the segger debugger before restarting up the segger daemon on the WIN7.
The other thing I can think of is if you forgot to shut down one segger daemon process on (for example) the WIN7 machine and you start a second one, yo get weird results. Shut down both (all) segger daemons. Unplug and plug the USB cable and then try starting the segger debugger up again.
Please
log in
or
register
to add a comment.
Please
log in
or
register
to answer this question.
3 Answers
0
votes
Best answer
Also make sure that after a clean install of Netos 7.5.2 you download all patches available. (When doing a clean install you need to delete all references of the previous Netos and Cygwin install.)
You may want to check your windows and bash paths.
Manually update the path environmental variable to ensure that the paths for V7.5.2 are in the front. To check windows paths just type the word path on a command promt. to check bash see below:
arm-elf$
printenv PATH
/usr/arm-elf/bin:/usr/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/cygdrive/c/Program Files/Common Files/Microsoft Shared/Windows Live:/cygdrive/c/Program Files (x86)/Common Files/Microsoft Shared/Windows Live:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0/:/cygdrive/c/Program Files/Intel/DMIX:/cygdrive/c/Program Files (x86)/Windows Imaging/:/cygdrive/c/Program Files (x86)/Microsoft SQL Server/100/Tools/Binn/VSShell/Common7/IDE/:/cygdrive/c/Program Files (x86)/Microsoft SQL Server/100/Tools/Binn/:/cygdrive/c/Program Files/Microsoft SQL Server/100/Tools/Binn/:/cygdrive/c/Program Files (x86)/Microsoft SQL Server/100/DTS/Binn/:/cygdrive/c/Program Files (x86)/Shoreline Communications/ShoreWare Client/:/cygdrive/c/Program Files (x86)/Windows Live/Shared:/cygdrive/c/Program Files/Internet Explorer:/cygdrive/c/netos75/mibcomp/mibcomp_win321/smi/bin:/cygdrive/c/netos75/bin
arm-elf$
answered
Jul 19, 2013
by
Campbell
Veteran of the Digi Community
(
780
points)
selected
Jul 20, 2013
by
gavello
PATH=C:\Program Files\Dell\DW WLAN Card;;C:\Program Files\AMD APP\bin\x86;C:\Win
dows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPow
erShell\v1.0\;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program F
iles\WIDCOMM\Bluetooth Software\;C:\netos75\mibcomp\mibcomp_win321\smi\bin;C:\ne
tos75\bin
Please
log in
or
register
to add a comment.
0
votes
This could be a path issue, do you have multiple copies of Cygwin or Netos installed on the same machine. Have you done a clean install. Also make sure you have administrative rights on the machine you are trying to do the clean install.
answered
Jul 19, 2013
by
Campbell
Veteran of the Digi Community
(
780
points)
no just one is a fresh install of both the Windows 7 OS and NET+OS
Please
log in
or
register
to add a comment.
0
votes
Actually I'm not using a vistual machine but thanks for the info
answered
Jul 22, 2013
by
gavello
New to the Community
(
16
points)
Well if you are NOT using a virtual machine and you do NOT have more than one segger process running then the only other thing that might cause the issues you are seeing: Are you absolutely sure you selected the correct platform when you set up the project? A debug script gets sent down with the download. IF you selected the wrong platform, then it is possible for the wrong chip selects and all that other jazz to be shipped down, if the wrong platform is selected.
Please
log in
or
register
to add a comment.
...