BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team @ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Darren

Pages: 1 [2]
16
Discussion - EVE / Re: ESD (4.14.0) - Emulator Executable (Flash files)
« on: February 21, 2022, 12:05:39 PM »
Hello,

Many thanks for your assistance, looking forward to a solution.

Kind Regards
Darren

17
Discussion - EVE / Re: ESD (4.14.0) - Eclipse Exported (Flash files)
« on: February 18, 2022, 08:52:40 AM »
Hello Community,

Retested on latest 4.15.0 with the same outcome, please would it be possible to receive an update on progress?

Kind Regards
Darren

18
Discussion - EVE / Re: ESD (4.14.0) - Emulator Executable (Flash files)
« on: February 18, 2022, 08:52:08 AM »
Hello Community,

Retested on latest 4.15.0 with the same outcome, has anybody successfully been able to use Emulator executable with Flash binary?

Kind Regards
Darren

19
Discussion - EVE / Re: New User - Adding Custom Images to Flash with ESD
« on: February 16, 2022, 11:12:27 AM »
Hi,

If your using ESD you can directly add your assets and select which are to be stored in Flash memory.

See ESD User Guide (BRT_AN_029) v1.3 p40 "Add Bitmap Resource"

ESD will build the required Flash binary when you build an executable (FT4222 / MPSSE) or export to Eclipse project which will require code in your final project to load into the displays flash memory, for devleopment purposes you can load the generated binary into the display using Eve Asset Builder after which run the generated .exe

See EAB User Guide (BRT_AN_054) v1.7 p22 "Program Flash"

Hope this helps.

20
Discussion - EVE / Re: ESD (4.14.0) - Build Executable (.dll files)
« on: February 07, 2022, 09:07:22 AM »
Hello,

Many thanks for your assistance.

Regards
Darren

21
Discussion - EVE / Re: ESD (4.14.0) - Build Executable (.dll files)
« on: February 03, 2022, 11:28:22 AM »
Hello,

Many thanks for confirming the default behaviour.

Please would it be possible to make a feature request to add a menu option to automatically include required dll's for Emulator/MPSSE generated executables?

This would maintain the default intended behaviour while providing the user an option to have required dependencies automatically included while acknowledging any such dependencies as when a project is cleaned the generated directory including manually copied dll is removed.
Also if a custom project directory location is used the ESD installtion directory containing the required dll's may not be local for ease of manually copying frequently.

Regards
Darren

22
Discussion - EVE / Re: ESD (4.14.0) - Eclipse Exported (Flash files)
« on: February 01, 2022, 01:39:19 PM »
Hello Community,

Update: Further investigation into the produced Flash Binary (from Export as Eclipse Project) reveals their is indeed a Blob file present within the Flash Binary while not been listed within the corresponding .map file.
The file size remains an issue at this time due to the extra padding applied which is different to that produced by MPSSE executable.

Many Thanks

23
Discussion - EVE / Re: ESD (4.14.0) - Build Executable (.dll files)
« on: February 01, 2022, 01:35:18 PM »
Hello,

Many thanks for looking into this issue and escalating to the development team, I look forward to a future update with dll's automatically included  :)

Regards
Darren

24
Discussion - EVE / ESD (4.14.0) - Eclipse Exported (Flash files)
« on: February 01, 2022, 10:45:31 AM »
Hello Community,

I am finding the generated Flash Binaries vary in both size and content when generated by MPSSE Build Executable and Export as Eclipse Project from the same project. (Only Host Platform was changed between generating MPSSE executable and Exporting Eclipse project. (Export as Eclipse Project unavailable under MPSSE))

It appears when Exporting an Eclipse project the generated Flash Binary does A) not include a Blob file and B) Pad the Flash file (when checked with Hex editor) (Results in longer thaan required transfer times).
When Building a MPSSE Executable the generated Flash Binary includes the required Blob file and maintains a minimal file size for the assets contained as can be seen in attachment ESD_4.14.0_ExportFlashCompare.png.

Q) Is it possible via alternative selections or config change to ESD to achive a Flash Binary as generated by MPSSE executable when Exporting as Eclipse Project?

Your experience and knowledge is greatly appreciated.
Many Thanks

25
Discussion - EVE / ESD (4.14.0) - Emulator Executable (Flash files)
« on: January 28, 2022, 03:46:55 PM »
Hello Community,

When attempting to launch an Emulator executable generated from a project that uses assets stored in EVE connected Flash a prompt is presented 'Select flash file (or press ENTER to use no flash):' Entering the binary or map file name results in a 'Failed to load flash library' message been displayed as per attached screenshot.

Q) Is there any specific requirements when entering Flash file name when using a generated Emulator executable or a method to output more detail as to why the load failed?

Your experience and knowledge is greatly appreciated.
Many Thanks

26
Discussion - EVE / ESD (4.14.0) - Build Executable (.dll files)
« on: January 28, 2022, 03:20:09 PM »
Hello Community,

When attempting to launch an executable built from within ESD for either MPSSE or Emulator an error is displayed stating the relevent .dll is missing as per screenshots.

From a default installation of ESD the missing .dll files are easily located at "C:\Users\Public\Documents\EVE Screen Designer" and when manually copied into the Bin folder the .exe launches as expected.

Q) Is the expected behaviour upon executable build for a copy of the .dll to be placed automatically by ESD or use the .dll from it's default location?

Q) Is there a setting or config required to achive either of the options previously queried or is this a bug within ESD?

Your experience and knowledge is greatly appreciated.
Many Thanks


Pages: 1 [2]