Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
EBlink : can't load device-script : stm32auto.script
#1
Hi,
Have installed EMBITZ 2.63(29) and EBLINK 5.30. For test I defined a small program for stm32f407VG disco using the project wizard. I included use of EBMonitor and ebmon.c and .h  were added to the project.  In the generated main.c  source I added for test of ebmonitor  a printf("\f I am alive \n"); 
As expected the build was ok. However running Debug gives the the message :   "can't load device-script : stm32auto.script".
I've checked the 3 environment vars in windows 11  for EBlink. They are: 
EB_SCRIPT_PATH     C:\Program Files (x86) \EBLINK\scripts  (here it actually resides)
EB_SCRIPT_ PROBE  stlink
EB_SCRIPT_SCRIPT  auto  
which seems allright to me.
I am using   STlink   V4.5

I have no clue were goes wrong, Would appreciate your advice.

Cop
Reply
#2
The device script has changed to stm32(.script).
I will check the wizard, it needs an update to the latest EBlink versions.

You could also set the DEVICE option at the debug interface settings at "auto".

Cheers

P.s. the environment variables are only used by EBlink if started standalone (CLI or via context menu).

Update:

Attached the modified wizard.script for EmBitz. You could replace the old one with this one.
Located: {$embitz}/share/EmBitz/templates/arm/st

   


Attached Files
.script   wizard.script (Size: 31.76 KB / Downloads: 1)
Reply
#3
(18-02-2025, 07:27 PM)embitz Wrote: The device script has changed to stm32(.script).
I will check the wizard, it needs an update to the latest EBlink versions.

You could also set the DEVICE option at the debug interface settings at "auto".

Cheers

P.s. the environment variables are only used by EBlink if started standalone (CLI or via context menu).

Update:

Attached the modified wizard.script for EmBitz. You could replace the old one with this one.
Located: {$embitz}/share/EmBitz/templates/arm/st
Reply
#4
Thank You for fast reaction.

I replaced the wizard.script. However when specifying 'stm32' nor 'auto' Neither 'stm32'nor 'auto' is accepted and results in 'script not found' message'.
In the window "Debug Interface Options" the 'device' entry shows 'auto' but expanding this entry gives an empty window!

COP
Reply
#5
After an uninstall of eblink and embitz have reinstalled both and all runs fine. I do'nt no why but am happy to proceed now. Sorry for the troubles.

COP
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)