Alesis Photon X25 firmware?

[merlyn]

You're welcome.

It was @BillB who saved the day and shared the X25 firmware with me. Thanks again Bill!

[BillB]

No problem - I don’t recall exactly where I got it from. Possibly the Alesis site many years ago, maybe a support forum... shame it is not on the Alesis website right now.

My view is that manufacturers have a moral obligation (and reputational incentive) to support all of their old gear with manuals, firmwares etc. I don’t expect to be able to call their support desk to know why a decade-old bit of kit isn’t working. But they should, at the very least, be able to host all previously-produced digital information and support files for their legacy products.



Rant over!

[Drew Stephenson]

My view is that manufacturers have a moral obligation (and reputational incentive) to support all of their old gear with manuals, firmwares etc. I don’t expect to be able to call their support desk to know why a decade-old bit of kit isn’t working. But they should, at the very least, be able to host all previously-produced digital information and support files for their legacy products.



Rant over!

Rant may be over but it's very much supported!

[omitho]

I'm sure I speak for many here. My Px25 seems to be bricked. From reading all these posts, perhaps not. Using dfu-util might be straight-forward for you but I'm completely lost. I've tried loading XP to a usb drive but it crashes on install saying it could be shadowing / vid drivers etc. I don't want to study about legacy crap to get things working and I don't want to buy anything to replace the x25. I'd like to use it to use softsynths as well as my microKORG. The only thing it does is the lights flash on, on power up using a DC PS. In usb mode it does nothing. I've gone through the procedures as explained but cannot get it to do anything.
When using ubuntu the dfu doesn't see the device at all. From what I read this means the firmware is erased already. How would i know where to send the new firmware if I cannot see the device? I tried dfu-util -l but it returns nothing.
In windows 10 I can switch between PS and USB and hear a noise but nothing pops up nor does the device LCD display show anything at all, like its dead completely. I have checked device manager and cannot see anything there either. I am using an Alesis multimix8 which i have unplugged trying to get this to work.
A lot of legacy devices are awesome this was one of them - i bought new and would love to use again. If anyone could help that would be great.
My studio:
Fantom x8
NI Maschine
Yamaha TX81Z
Roland JV1010
Roland SH32
Roland SP808EX
Alesis Multimix8
Midiman Radium
MicroKORG

Thanks in advance !
O

[merlyn]

When using ubuntu the dfu doesn't see the device at all. From what I read this means the firmware is erased already.

No, if the firmware is erased dfu-util should see it. If

Code: Select all

$ dfu-util -l

returns nothing, check the basics. There is a push switch on the back of the PhotonX25 that chooses between USB power and an external PSU. Make sure that is on USB. Then, is the USB cable good?

What does

Code: Select all

$ lsusb

show? If I remember correctly when the X25 has its firmware erased it shows up as 'unknown device' or 'dfu device', something like that.

[omitho]

In windows 10 it is showing up as unknown, with a second device under it as unknown device this is in device manager. But the dfu program they use / in the package doesn't see it at all in win 10. Ubuntu doesn't appear to have a device manager and makes no sound at all when switching the x25 on. In Win 10 it does make a sound. There is absolutely no sign of life on the x25 the entire time.

Thanks for the help,
O

[merlyn]

When I looked into this some of the solutions I saw for Windows 10 were to use Windows Subsystem for Linux (WSL) so if you have an Ubuntu system available you may as well use that.

On Ubuntu there are programs that are similar to device manager on Windows, but I would just use the command line. The lsusb command lists all USB devices connected. Open a terminal, type lsusb then press 'enter'. On my system this is the output (the dollar sign is the command prompt for a normal user) :

Code: Select all

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 13b2:000a Alesis PhotonX25
Bus 001 Device 005: ID 1462:7c56 Micro Star International MYSTIC LIGHT 
Bus 001 Device 004: ID 047d:1020 Kensington Expert Mouse Trackball
Bus 001 Device 003: ID 046a:00ab Cherry GmbH Mechanical Keyboard
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[omitho]

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 006: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 003 Device 005: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 003 Device 004: ID 08bb:2900 Texas Instruments PCM2900 Audio Codec
Bus 003 Device 010: ID ffff:fffe Unknown Unknown **
Bus 003 Device 003: ID 0763:1015 M-Audio M-Audio Keystation
Bus 003 Device 007: ID 0cf3:e004 Qualcomm Atheros Communications Bluetooth USB Host Controller
Bus 003 Device 002: ID 040a:0001 Kodak Co. DVC-323
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I added the **
the filename to add to dfu-util is QP0 1_04 20070724 DFU ONLY - No Presets
dfu-util is a little confusing as is a lot of linux command lines based on what you see, can you give me a cut n paste cmd line?

thanks again!
O

[merlyn]

That looks good. The 'Unknown' device will be the X25.

First I would check you have dfu-util installed and it's working with

Code: Select all

$ dfu-util -l

That should show something.

The firmware ends in .bin, so you need a path to that. Is QP0 1_04 20070724 DFU ONLY - No Presets the folder the firmware is in?

[omitho]

I have all this. I can find the folder (i think LOL) Ive been looking around at different things but the way it's identified through ubuntu is puzzling compared to other things I have seen .
I'm not well versed in Linux, but I'm not completely lost. Thinking back to when there wasn't a single www page there was UNIX.... and I could get around so, I get it a little but if you don't use it , you lose it. Here's what I got today:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 010: ID 1acc:1534 Midiplus Co, Ltd.
Bus 003 Device 006: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 003 Device 005: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 003 Device 004: ID 08bb:2900 Texas Instruments PCM2900 Audio Codec
Bus 003 Device 011: ID ffff:fffe Unknown Unknown
Bus 003 Device 003: ID 0582:006d Roland Corp. FANTOM-X
Bus 003 Device 007: ID 0cf3:e004 Qualcomm Atheros Communications Bluetooth USB Host Controller
Bus 003 Device 002: ID 040a:0001 Kodak Co. DVC-323
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I've looked at sample dfu-util command lines and based on those it's hard to tell what I need at this point, And I appreciate all your help. Next I'm going to dig into Fantom X8 midi...but thats something else....LOL

Thanks
OmithO

[omitho]

also, sudo dfu-util - l returns this:
Deducing device DFU version from functional descriptor length
Found Runtime: [ffff:fffe] ver=0100, devnum=11, cfg=1, intf=0, path="3-5", alt=0, name="EEPROM", serial="UNKNOWN"

This is where I am puzzled the name and serial doesn't look like the dfu-util is going to work.

O

[merlyn]

That output looks fine. Flashing the firmware is as simple as

Code: Select all

$ dfu-util -D /path/to/firmware

-D for download. dfu-util is intelligent enough to select the correct dfu device if there is only one connected.

Replace /path/to/firmware with the path to where the firmware is. If the firmware is on your Windows machine and you're booting from a USB stick the path will be something like /media/<bunch of numbers>/ followed by the path on the Windows machine.

Use a file manager to find the firmware, then copy the path.

[omitho]

dfu-util -D /home/omitho/Downloads/PhX QP1 1_04 20070725 DFU ONLY - No Presets.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: File size is too big: Success

Not sure what is going on the file size is 5973 bytes ..........any ideas?
O

[merlyn]

You need sudo in front of it and spaces need special treatment in a file name. What I would do is use 'Tab'. Type in the start of the filename then hit 'Tab' and the terminal completes what you're typing. if there are multiple possibilities 'Tab' doesn't do anything. Hit 'Tab' again and you get a list of possibilities. Type another letter and repeat the process until you get the full path. Doing it that way means you can't make a typo.

5973 is the right size, so it should work.

[omitho]

Tab did nothing at all, I read somewhere it was due to the spaces. I actually went to file manager, copied the path first and pasted it in and then the filename as if I were going to rename it but left as is, so I wouldn't make a mistake. Would it make a difference if I just named it to a one word.bin filename. I mean it says parent folder: /home/omitho/Downloads/PhX do I need a / after PhX?
I tried using quotes sudo dfu-util -D /home/omitho/Downloads/PhX "QP1 1_04 20070725 DFU ONLY - No Presets.bin"
fu-util: File size is too big: Success
My prompt looks like this, is there something there I need to include?
omitho@omitho-XPS-8700:~$
On another note the photon has been showing up in Ableton as Legacy MIDI keyboard but still no lights....
O

[omitho]

and I have tried it with / after PhX/ same results I believe

[merlyn]

Just to check the 'Tab' thing -- try this :

Code: Select all

$ /h 

then hit 'Tab'. I've never used a Linux system where that didn't work. I'm not saying it's impossible though.

[omitho]

it returned /home/

[omitho]

is the x25 looking for a specific filename or could it be named basic.bin and it still work? I wish I wasn't having such a hard time with this. I bought a midiplus 2x2 to replace the edirol 2x2 that replaced an m-audio 1010LT my ex kept in my computer...that replaced an OPCODE 10 (wish I could make that dinosaur work!!). I get some strange glitches in the midiplus, cant say I really like it, but seemed like a solution at the time....the other issue i told ya about on that other device started working but doing weird things....

[merlyn]

OK. Maybe that's too complicated for just now. If PhX is a directory (folder) the copy and paste version is this :

Code: Select all

$ sudo dfu-util -D /home/othmay/Downloads/PhX/QP1\ 1_04\ 20070725\ DFU\ ONLY\ -\ No\ Presets.bin

To paste into a terminal use 'Ctrl+Alt+v'.

[omitho]

You would think if they were a superior product they would offer a fit decal to make it correct. They could put the letters over the ports and black out the bottom. I mean I kind of started laughing when you were saying "something better" and I read their ports are labeled backwards and its a "design flaw" . I mean other than those fancy worthless yellow and green LED lights that tell u midi is passing through it's description is about the same as my el cheapo midiplus. I was happy using 1 midi out from my Delta 1010LT and thru/out 5 synthesizers never had any issues surprisingly.
Merlyn.....seems to have worked...
dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
ID ffff:fffe
Run-time device DFU version 0100
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
dfu-util: WARNING: Runtime device already in DFU state ?!?
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0100
Device returned transfer size 64
Copying data from PC to DFU device
Download [=========================] 100% 5973 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present

ctrl+alt V just dinged the terminal i right clicked and pasted and fixed the othmay typo
OmithO

[omitho]

woohoo now it dont say unknown unknown
Bus 003 Device 008: ID 0cf3:e004 Qualcomm Atheros Communications Bluetooth USB Host Controller
Bus 003 Device 009: ID 13b2:000a Alesis PhotonX25
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I really appreciate it and yes I have learned quite a lot about linux that i didn't know. there was a minute i was locked out of SOS couldn't read or post for a day or two so I was reading all kinds of stuff to try and figure out what to do...

O

[omitho]

your subzero says:

This product is currently not available for purchase

the midiplus is $45 at newegg, to me it's like a repackaged edirol UM-2

[merlyn]

Copying data from PC to DFU device
Download [=========================] 100% 5973 bytes
Download done.

That's what you want to see. After that power cycle the X25 and the lights should come on.