Chesco Posted December 1, 2022 Author Share Posted December 1, 2022 1 hour ago, lucky1 said: You are not connected to the CPU ! Mine is not that, mine is this: Link to comment Share on other sites More sharing options...
Chesco Posted December 1, 2022 Author Share Posted December 1, 2022 Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 1, 2022 Content Provider Share Posted December 1, 2022 Now you should be able to connect with putty and continue like described in the howto text 3. Open a telnet session to openocd by using 127.0.0.1 and port 4444 (see putty.png) 4. In your telnet terminal enter "reset_config srst_only" 5. Connect the reset pin to ground on your device 6. Enter "kinetis mdm mass_erase" 7. Disconnect reset pin from ground 8. Enter "kinetis mdm halt" 9. Enter "flash write_image pin2dmd.bin" 10. Wait till image is fully written 11. Enter "reset" 12. You should see your device starting up with pin2dmd firmware. Link to comment Share on other sites More sharing options...
Chesco Posted December 1, 2022 Author Share Posted December 1, 2022 Link to comment Share on other sites More sharing options...
Chesco Posted December 1, 2022 Author Share Posted December 1, 2022 Open On-Chip Debugger > reset_config srst_only srst_only separate srst_nogate srst_open_drain connect_deassert_srst > kinetis mdm mass_erase SWD DPIDR 0x2ba01477 Polling target k60.cpu failed, trying to reexamine MDM: failed to read ID register SWD DPIDR 0x2ba01477 k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Halt timed out, wake up GDB. > kinetis mdm halt Halt timed out, wake up GDB. > flash write_image pin2dmd.bin Kinetis MK10DX8xxx5 detected: 2 flash blocks 1 PFlash banks: 8k total 1 FlexNVM banks: 0k total, 0k available as data flash, 16384bytes FlexRAM MAXADDR0 0x00 check failed, please report to OpenOCD mailing list Target not halted error writing to flash at address 0x00000000 at offset 0x00000000 Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine MDM: failed to read ID register SWD DPIDR 0x2ba01477 k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine MDM: failed to read ID register SWD DPIDR 0x2ba01477 k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. SWD DPIDR 0x2ba01477 Failed to write memory at 0xe0002014 k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine MDM: failed to read ID register SWD DPIDR 0x2ba01477 k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints Polling target k60.cpu failed, trying to reexamine SWD DPIDR 0x2ba01477 MDM: Chip is unsecured. Continuing. k60.cpu: hardware has 6 breakpoints, 4 watchpoints > flash write_image pin2dmd.bin Target not halted error writing to flash at address 0x00000000 at offset 0x00000000 Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 1, 2022 Content Provider Share Posted December 1, 2022 Did you make a connection between RESET and GND ? Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 1, 2022 Content Provider Share Posted December 1, 2022 Did you remove the reset connection after mass erase ? 26 minutes ago, Chesco said: Target not halted kinetis mdm halt and then if it is halted flash write_image pin2dmd.bin Link to comment Share on other sites More sharing options...
Chesco Posted December 1, 2022 Author Share Posted December 1, 2022 (edited) Now I have the correct image by running "dap.bat" and I can establish a Putty connection. I can enter "reset_config srst_only" I make a connection between GND and RESET of the MK66 and the other end of the cable to the GND of the CMSIS, but there is no way. Open On-Chip Debugger > reset_config srst_only srst_only separate srst_nogate srst_open_drain connect_deassert_srst > kinetis mdm mass_erase Halt timed out, wake up GDB. > kinetis mdm halt Halt timed out, wake up GDB. > flash write_image pin2dmd.bin Kinetis MK10DX8xxx5 detected: 2 flash blocks 1 PFlash banks: 8k total 1 FlexNVM banks: 0k total, 0k available as data flash, 16384bytes FlexRAM MAXADDR0 0x00 check failed, please report to OpenOCD mailing list Target not halted error writing to flash at address 0x00000000 at offset 0x00000000 > This is the way to connect GND and RESET together (the other end of the wire is on GND of the CMSIS) Edited December 1, 2022 by Chesco Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 1, 2022 Content Provider Share Posted December 1, 2022 It makes no sense to initiate the other command when the mdm mass_erase already fails. It is easier to make the connection from reset to one of the GND pins of the DMD connector. That way you can keep the GND wire to the DAPLINK. The mdm mass_erase can be a bit tricky. Try toggling the reset pin when initiating the mdm mass erase. Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 1, 2022 Content Provider Share Posted December 1, 2022 Maybe try "reset halt" before kinetis mdm mass_erase Here are the instructions that helped me . Only point 3 is important for your configuration. https://jcard0na.github.io/2016/11/11/recover-from-kinetis-in-secured-state.html Link to comment Share on other sites More sharing options...
Chesco Posted December 2, 2022 Author Share Posted December 2, 2022 Thanks you very much @lucky1 I will do it again 🤞🏼 Link to comment Share on other sites More sharing options...
Chesco Posted December 2, 2022 Author Share Posted December 2, 2022 14 hours ago, lucky1 said: Maybe try "reset halt" before kinetis mdm mass_erase Here are the instructions that helped me . Only point 3 is important for your configuration. https://jcard0na.github.io/2016/11/11/recover-from-kinetis-in-secured-state.html Link to comment Share on other sites More sharing options...
Chesco Posted December 2, 2022 Author Share Posted December 2, 2022 (edited) I finally got it... 1. Connect your cmsis dap adapter to the device 2. Start openocd by executing "dap.bat" 3. Open a telnet session to openocd by using 127.0.0.1 and port 4444 (see putty.png) 4. In your telnet terminal enter "reset_config none separate" 5. Connect the reset pin to ground on your device 6. Enter "kinetis mdm mass_erase" 7. Disconnect reset pin from ground 8. Enter "kinetis mdm halt" 9. Enter "flash write_image pin2dmd.bin" 10. Wait till image is fully written 11. Enter "reset" 12. You should see your device starting up with pin2dmd firmware. Edited December 2, 2022 by Chesco Link to comment Share on other sites More sharing options...
Chesco Posted December 2, 2022 Author Share Posted December 2, 2022 I have updated to version 4.41 with the file pin2dmd.upd and a MicroSD. However, now there is another small problem... This Display DMD MK66 has no Mini USB port and no Menu buttons. How can I change from "VIRTUAL PINBALL" to another setting such as "BALLY/WILLIAMS"??? I also can't see the serial number of the device completely 🤔 Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 2, 2022 Content Provider Share Posted December 2, 2022 30 minutes ago, Chesco said: This Display DMD MK66 has no Mini USB port and no Menu buttons. You can generate a config file (pin2dmd.dat) with the pin2dmd.exe tool and save it to a microsd 31 minutes ago, Chesco said: I also can't see the serial number of the device completely I have to check. Link to comment Share on other sites More sharing options...
Chesco Posted December 2, 2022 Author Share Posted December 2, 2022 Great... I'm waiting for the SN and key. Thanks. Link to comment Share on other sites More sharing options...
Chesco Posted December 2, 2022 Author Share Posted December 2, 2022 All's perfect! Thanks @lucky1 Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 3, 2022 Content Provider Share Posted December 3, 2022 @Chesco Could you please change the topic from "Update Pin2dmd" to "Update DMDMK66 to PIN2DMD firmware" Link to comment Share on other sites More sharing options...
trueno92 Posted December 3, 2022 Share Posted December 3, 2022 Wow nice job guys. Lucky1 your skills are amazing. Link to comment Share on other sites More sharing options...
Chesco Posted December 3, 2022 Author Share Posted December 3, 2022 56 minutes ago, lucky1 said: @Chesco Could you please change the topic from "Update Pin2dmd" to "Update DMDMK66 to PIN2DMD firmware" Done. 👍🏼 Link to comment Share on other sites More sharing options...
Chesco Posted December 12, 2022 Author Share Posted December 12, 2022 (edited) Hello again. I tell you the latest "advances" with DMD MK66 updated with Pin2DMD firmware. As the device does not have menu buttons, reset... I have created a "pin2dmd.dat" file with the "Williams/Bally" configuration and I have exported that *.dat file to the MicroSD card. The device reboots and shows the selected configuration for a WCS 94 (Williams/Bally). However, I can't get it to work... With the MicroSD card inserted, the device boots and when starting the game (after the Test Report), the screen goes completely black and shows nothing. If I remove the MicroSD card from the device, it starts up and passes the Test Report, but after a few moments, the image remains frozen on the Display... Any suggestions? Thanks. https://es.files.fm/u/277mpsck4 https://es.files.fm/u/xcjbbk3b7 Edited December 12, 2022 by Chesco Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 12, 2022 Content Provider Share Posted December 12, 2022 Since you are the first one who successfully installed this version, it is practically a beta version which has not been thoroughly tested. I have to see if I can reproduce the problem, to see what is going wrong. Link to comment Share on other sites More sharing options...
Chesco Posted December 12, 2022 Author Share Posted December 12, 2022 18 minutes ago, lucky1 said: Since you are the first one who successfully installed this version, it is practically a beta version which has not been thoroughly tested. I have to see if I can reproduce the problem, to see what is going wrong. Thanks you very much @lucky1 Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted December 13, 2022 Content Provider Share Posted December 13, 2022 I could not reproduce the freeze. I guess it is caused by a voltage drop on your machine. Could you please try powering the display with a external power supply and check if the freeze without active colorization occurs ? Link to comment Share on other sites More sharing options...
Chesco Posted December 13, 2022 Author Share Posted December 13, 2022 (edited) 43 minutes ago, lucky1 said: I could not reproduce the freeze. I guess it is caused by a voltage drop on your machine. Could you please try powering the display with a external power supply and check if the freeze without active colorization occurs ? Ok. Give me an hours.. Although I highly doubt that the freezing is due to a pinball voltage drop. This was tested with a Pin2dmd EVO Display and it worked PERFECTLY. Thanks. Edited December 13, 2022 by Chesco Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now