Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
lucky1

Pin2Dmd Colorprism V3.0 Firmware

Recommended Posts

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

Share this post


Link to post
Share on other sites
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

 

Share this post


Link to post
Share on other sites

i tried 3.0 on stm32 but result is black screen like for some other guys too. back on 2.67 now

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites
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 ?

 

Share this post


Link to post
Share on other sites
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 ?

Share this post


Link to post
Share on other sites

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

 

  • Upvote 1

Share this post


Link to post
Share on other sites
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.

 

Share this post


Link to post
Share on other sites

With v3. 00 I found problems on real pinball DatabEast Hook 128 x 16 that the images were all distorted and sometimes blocked

Share this post


Link to post
Share on other sites
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 ? 

Share this post


Link to post
Share on other sites

3.x Not working with freezy dll. Only works with Lucky.dll... so i wont Update my pin2dmd

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

Hi everyone, it's the same for me.  it works very well with lucky but black screen with freezy.

Share this post


Link to post
Share on other sites

Just look at lucky1 s latest post...

Rename freezys dmddevice.dll to dmdscreen.dll and set Pin2dmd = false in dmddevice.ini

Copy dmddevice.dll from official pin2dmd GitHub into vpinmame folder and you should be good to go.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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

  • Upvote 1

Share this post


Link to post
Share on other sites

New version with improved sync for 128x16 machines is out

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...