SmartSnippets Toolbox v5.0.6.2196 not working with DA14580

11 posts / 0 new
Last post
Michael Hunold
Offline
Last seen: 1 month 13 hours ago
Joined: 2016-08-05 07:53
SmartSnippets Toolbox v5.0.6.2196 not working with DA14580

I just installed the SmartSnippets Toolbox v5.0.6.2196 on a freshly installed Windows 10.

Next I used a DA14580 development kit and attached a DA14580 device on a PAN1740 module.

Then I launched SmartSnippets Toolbox v5.0.6.2196 from a Windows command prompt.

I selected the JTAG of the attached DA14580 development kit and chose "DA14580-01" for the chip version.

After clicking the "Open" button the application crashes with the following backtrace in the console window:

c:\DiaSemi\SmartSnippetsStudio2.0.6\Toolbox>SmartSnippetsToolbox.exe
Re-init SP
Exception in thread "AWT-EventQueue-0" java.lang.NumberFormatException: For input string: "10,10"
at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
at sun.misc.FloatingDecimal.parseDouble(FloatingDecimal.java:110)
at java.lang.Double.parseDouble(Double.java:538)
at com.dialog.batteryLifetimeEstimator.EstimatorGui.F(Unknown Source)
at com.dialog.batteryLifetimeEstimator.EstimatorGui.M(Unknown Source)
at com.dialog.batteryLifetimeEstimator.A.B(Unknown Source)
at com.dialog.batteryLifetimeEstimator.A.(Unknown Source)
at com.Framework.Z.F(Unknown Source)
at com.Framework.Z.(Unknown Source)
at com.Framework.DA14580.B.(Unknown Source)
at com.Framework.SmartSnippetMain.s(Unknown Source)
at com.Framework.SmartSnippetMain.Ë(Unknown Source)
at com.Framework.V.W(Unknown Source)
at com.Framework.V.J(Unknown Source)
at com.Framework.V$7.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
at java.awt.Component.processMouseEvent(Component.java:6533)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
at java.awt.Component.processEvent(Component.java:6298)
at java.awt.Container.processEvent(Container.java:2236)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2294)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
at java.awt.Container.dispatchEventImpl(Container.java:2280)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:90)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.awt.EventQueue$4.run(EventQueue.java:729)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:109)
at java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:184)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

It seems that an incorrect init value is passed to the batteryLifetimeEstimator subsystem.

Chosing a different chip version like DA14680 does not crash the SmartSnippets Toolbox.

I also installed SmartSnippets Toolbox v5.0.6.2196 on an older, already used Windows 7 and there the problem happens as well.

Can you please check if the latest version SmartSnippets Toolbox v5.0.6.2196 still works with the DA14580 chipset?

Device: 
azimin
Offline
Last seen: 6 days 15 hours ago
Joined: 2018-12-12 12:11
I have the same problem

I have the same problem

MHv_Dialog
Offline
Last seen: 2 days 11 hours ago
Staff
Joined: 2013-12-06 15:10
We are currently

We are currently investigating this issue. The tools appear to work on both Win7 and Win10 in general, but there may be issues with the Java Runtime Libraries installed on your PC. We will be back with additional information shortly.

azimin
Offline
Last seen: 6 days 15 hours ago
Joined: 2018-12-12 12:11
Hello, are there any news

Hello, are there any news with the issue?

PM_Dialog
Offline
Last seen: 10 hours 39 min ago
Staff
Joined: 2018-02-08 11:03
Hi azimin,

Hi azimin,

We don’t have any news on this issue. If we have any update on this, I will let you know.

Thanks, PM_Dialog

PM_Dialog
Offline
Last seen: 10 hours 39 min ago
Staff
Joined: 2018-02-08 11:03
Hi Michael Hunold and azimin,

Hi Michael Hunold and azimin,

Please follow the link below in order to find a possible workaround on this issue.

https://support.dialog-semiconductor.com/forums/post/announcements-and-updates/toolbox-start-issues

Thanks, PM_Dialog

roland
Offline
Last seen: 1 day 13 hours ago
Joined: 2014-01-21 14:45
Related to the above

Related to the above Windows10 and locale settings, using Keil to compile the DA1485x projects show a similar problem complaining about not able to support multi byte due to a setting of a locale.

Look for:
https://developer.arm.com/products/software-development-tools/compilers/...

I had problems compiling the DSPS application on a fresh and new installed system: I had to set "--locale=us_UK" in both the command line options of the c compiler and on the topline of the scatter file...

Then it works......

roland
Offline
Last seen: 1 day 13 hours ago
Joined: 2014-01-21 14:45
Related to the above

Related to the above Windows10 and locale settings, using Keil to compile the DA1485x projects show a similar problem complaining about not able to support multi byte due to a setting of a locale.

Look for:
https://developer.arm.com/products/software-development-tools/compilers/...

I had problems compiling the DSPS application on a fresh and new installed system: I had to set "--locale=us_UK" in both the command line options of the c compiler and on the topline of the scatter file...

Then it works......

PM_Dialog
Offline
Last seen: 10 hours 39 min ago
Staff
Joined: 2018-02-08 11:03
Hi roland,

Hi roland,

Thanks for your indication. You could mark the answer as “accepted” because it contains useful information.

Regards, PM_Dialog

Michael Hunold
Offline
Last seen: 1 month 13 hours ago
Joined: 2016-08-05 07:53
I can confirm that setting

I can confirm that setting the regional settings to "English (United States)" is a suitable workaround for the problem.
However, I had to go to "Additional date, time & regional settings" and use "Change location" and then "Format" and select "English (United States)" there, too.

PM_Dialog
Offline
Last seen: 10 hours 39 min ago
Staff
Joined: 2018-02-08 11:03
Hi Michael Hunold,

Hi Michael Hunold,

Glad that you figured your issue out and thank you for your indication.

Thanks, PM_Dialog