Content Provider lucky1 Posted August 1, 2019 Content Provider Share Posted August 1, 2019 Time for a new major release. The main job was to port the firmware to a hardware abstraction layer library which allows us to compile the firmware on almost all STM32 MCUs (F7/H7) (and also MCUs from other manufacturers like NXP) with only little modifications. This is only for future use. Currently the project still relies on the STM32F4 family and there are no plans to change this until we are forced to. - based on hardware abstraction layer library for better portability to different hardware - added autodetection for real pinball machines when in vpin mode (default) - added display panel test to onscreen menu - added signature check and checksum to update files - added Spooky AMH color support with modified AV firmware by herg https://pinside.com/pinball/forum/topic/color-display-for-america-s-most-haunted-it-s-happening/page/4#post-5016434 V3.01 - fix bootloop when used without shield V3.02 - make old palette switch method work with freezy DLL V3.03 - improve sync for 128x16 V3.04 - add Inder / SPinball as devicemode and to autodetection - fix problems with some SD cards - fix activation problem from SD - fix display after boot.fsq playback - fix switch of devicemodes from tool V3.05 - add usb raw transfer directly intp displaybuffer for better speed with P-ROC and MPF - show activation status in onscreen menu V3.06 - add Sleic / Petaco to devicemode and autodetection - add DE128x16 mode for TMNT and CP to autodetection - change timing of autodetection V3.07 - fix buttons in onscreen menu on Nucleo V3.08 - add support for HomePin V3.09 - fix save config problem with 32bit tool v3.10 - fix pin2dmd editor upload function - remove color correction for preset palettes - add bulk update function if pin2dmd.bulk file is present on SD v3.11 - fix first frame for ColorMask layered mode - fix detection of unmasked frames in ColorMask layered mode - allow Event with same hash as colorizations - fix bug in event handling v3.12 - change behaviour of "Replace Masked" mode like suggested by DJRobX - don´t retrigger ColorMask layered scene if scene is already loaded - create dummy file with serial on SD if no valid activation key is found - add USB raw transfer in WPC devicemode (PIN2RPI support) v3.13 - add optimized routine for 128x32 display on XL displays (VPIN) - fix colorization on XL displays in dmddevice.dll - use faster RGB24 routine in dmddevice.dll v3.14 - add option (PAL STORAGE) to onscreen menu to either store .pal file information in local Flash or RAM. Select FLASH for larger projects. v3.15 - fix tests in onscreen menu v3.16 - fix event keyframe only sent once - suppress subsequent events with the same ID v3.17 - enable to take a frame within a lcm scene as trigger to start the lcm scene. v3.18 - fix problem with simple palettes in flash pal storage mode - add init delay to fix issues with some SD cards v3.19 - fix crash on load of small palettes from flash in real pin modes v3.20 - migration release to version 4.x - fix masked replace mode for some devicemodes - refresh flash pal storage on firmware update Link to comment Share on other sites More sharing options...
Benoit33 Posted August 2, 2019 Share Posted August 2, 2019 On 7/15/2019 at 11:36 PM, BaronShadow said: hi the sofware tell me my firware is not good i need to update i upload the pin2dmd master file and i update the stm34 with the new firmware Link to comment Share on other sites More sharing options...
nbcrew Posted August 3, 2019 Share Posted August 3, 2019 i tried 3.0 on stm32 but result is black screen like for some other guys too. back on 2.67 now Link to comment Share on other sites More sharing options...
JustAnotherRat Posted August 4, 2019 Share Posted August 4, 2019 I upgraded to 3.00 however when trying to launch a game on my VPin I either get a completely black DMD or a quick flash of the DMD loading and then a completely black screen. I attempted to downgrade to V2.67 however when running ST-Link I get a message about not being able to communicate. Is there a way to fix this? Do I need to run the FUll Chip Erase from ST-Link? Please offer suggestions as I currently don't have a working Pin2DMD as a result of the new firmware. Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted August 4, 2019 Author Content Provider Share Posted August 4, 2019 5 hours ago, JustAnotherRat said: I upgraded to 3.00 however when trying to launch a game on my VPin I either get a completely black DMD or a quick flash of the DMD loading and then a completely black screen. I attempted to downgrade to V2.67 however when running ST-Link I get a message about not being able to communicate. Is there a way to fix this? Do I need to run the FUll Chip Erase from ST-Link? Please offer suggestions as I currently don't have a working Pin2DMD as a result of the new firmware. ST-Link should always work since it is accessing the processor though the debugging interface. Which upgrade procedure did you use SD-Card or ST-Link ? Maybe you used the wrong USB on the controller board to connect though ST-Link ? Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted August 4, 2019 Author Content Provider Share Posted August 4, 2019 On 8/3/2019 at 2:46 PM, nbcrew said: i tried 3.0 on stm32 but result is black screen like for some other guys too. back on 2.67 now Which hardware ? Link to comment Share on other sites More sharing options...
Dany Posted August 4, 2019 Share Posted August 4, 2019 I installed the v.3.00 on real pinball and it seems to work well beautiful even adding the ability to test the display and see if all the LEDs work as soon as I have done some tests give more info Link to comment Share on other sites More sharing options...
JustAnotherRat Posted August 5, 2019 Share Posted August 5, 2019 On 8/5/2019 at 1:18 AM, lucky1 said: ST-Link should always work since it is accessing the processor though the debugging interface. Which upgrade procedure did you use SD-Card or ST-Link ? Maybe you used the wrong USB on the controller board to connect though ST-Link ? I was using the right USB, not sure why it stopped working once I updated the firmware. I ended up connecting my laptop via the same cable and downgraded and it worked after it failed once I rebooted the laptop and tried again successfully. Link to comment Share on other sites More sharing options...
Dany Posted August 6, 2019 Share Posted August 6, 2019 With v3. 00 I found problems on real pinball DatabEast Hook 128 x 16 that the images were all distorted and sometimes blocked Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted August 6, 2019 Author Content Provider Share Posted August 6, 2019 5 hours ago, Dany said: With v3. 00 I found problems on real pinball DatabEast Hook 128 x 16 that the images were all distorted and sometimes blocked Is it working with 2.67 or which version did you use before ? Link to comment Share on other sites More sharing options...
Dany Posted August 6, 2019 Share Posted August 6, 2019 V.266 is ok Link to comment Share on other sites More sharing options...
nbcrew Posted August 6, 2019 Share Posted August 6, 2019 3.x Not working with freezy dll. Only works with Lucky.dll... so i wont Update my pin2dmd Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted August 6, 2019 Author Content Provider Share Posted August 6, 2019 4 hours ago, Dany said: V.266 is ok Thanks for the info. I will have a look at it. 1 hour ago, nbcrew said: 3.x Not working with freezy dll. Only works with Lucky.dll... so i wont Update my pin2dmd Heard about that too. I forwarded my dmddevice.dll sourcecode with new colorization stuff half a year ago, but it seems there is nobody taking care of freezy´s dll code anymore. I also read a lot about 1.7.2 not working but 1.7.1 is. I personally use my own dll of course. With the latest pinmame it should also be possible to use both by renaming freezy.dll to dmdscreen.dll and turning off pin2dmd in the dmddevice.ini. Link to comment Share on other sites More sharing options...
outhere Posted August 6, 2019 Share Posted August 6, 2019 Try Freezy 1.73 https://vpinball.com/forums/topic/freezy-dmd-question/#post-115676 Link to comment Share on other sites More sharing options...
vamprecords Posted August 6, 2019 Share Posted August 6, 2019 Freezy 1.73 also not working on firmware 3.01 black screen. Link to comment Share on other sites More sharing options...
dom69 Posted August 7, 2019 Share Posted August 7, 2019 Hi everyone, it's the same for me. it works very well with lucky but black screen with freezy. Link to comment Share on other sites More sharing options...
Rappelbox Posted August 7, 2019 Share Posted August 7, 2019 Just look at lucky1 s latest post...Rename freezys dmddevice.dll to dmdscreen.dll and set Pin2dmd = false in dmddevice.iniCopy dmddevice.dll from official pin2dmd GitHub into vpinmame folder and you should be good to go. Link to comment Share on other sites More sharing options...
JoXp Posted August 7, 2019 Share Posted August 7, 2019 Hello, i try the lucky1 solution and don t work with my pin2dmd ... i follow this step: i update with firmware 3.01 rename dmddevice.dll freezy -> dmdscreen.dll copy paste dmddevice.dll from integration folder pin2dmd git -> vpinmame folder in dmddevice.ini i set : [pin2dmd] ; if false, doesn't bother looking for a PIN2DMD enabled = false but nothing to do , not work :x Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted August 7, 2019 Author Content Provider Share Posted August 7, 2019 1 hour ago, JoXp said: Hello, i try the lucky1 solution and don t work with my pin2dmd ... i follow this step: i update with firmware 3.01 rename dmddevice.dll freezy -> dmdscreen.dll copy paste dmddevice.dll from integration folder pin2dmd git -> vpinmame folder in dmddevice.ini i set : [pin2dmd] ; if false, doesn't bother looking for a PIN2DMD enabled = false but nothing to do , not work :x If you use the old libusb-win32 drivers you also need to copy the libusbk.dll to your folder Link to comment Share on other sites More sharing options...
nbcrew Posted August 8, 2019 Share Posted August 8, 2019 not working for me either... It works for ultradmd and Pupdmd tables but every colorrom or altcolor table i tried gives me a black DMD with 3.01... again downgraded to 2.67. hopefully freezy will fix that anytime so everyone can use it Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted August 8, 2019 Author Content Provider Share Posted August 8, 2019 Please try V3.02 I just uploaded Link to comment Share on other sites More sharing options...
dom69 Posted August 8, 2019 Share Posted August 8, 2019 it's okay it turns out at home ? Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted August 12, 2019 Author Content Provider Share Posted August 12, 2019 New version with improved sync for 128x16 machines is out Link to comment Share on other sites More sharing options...
dom69 Posted August 12, 2019 Share Posted August 12, 2019 tested version it's ok Link to comment Share on other sites More sharing options...
Oldschool4 Posted August 13, 2019 Share Posted August 13, 2019 v3.02 works with my STM32 Discovery using Freezys. Thanks lucky1. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.