New KryoFlux not recognised by multiple systems

All questions about how to use KryoFlux go here.
Post Reply
Sphaera
Posts: 3
Joined: Thu Nov 21, 2019 1:52 am

New KryoFlux not recognised by multiple systems

Post by Sphaera » Thu Nov 21, 2019 11:59 pm

Hi,
It appears that the KryoFlux I received this week is faulty straight out of the box. I have read all of the documentation and are clear on all the warnings and the process to use the device (I'm not a newbie). I have also trawled this forum and found no solution.

I have failed to have any of my systems recognise the KryoFlux when it is plugged in, the red status LED is constantly illuminated when plugged in and the other 2 status LEDs have never illuminated.

I am using the supplied FDD cable (correctly oriented) and the supplied USB (plus some other verified working USB cables to test), I am powering an attached drive with the supplied power supply and have used another that is verified to be working, the power supply is not connected to the KryoFlux..

I have tested with a verified working 3.5" FDD and multiple verified working 5.25" TEAC FD-55GFR FDDs all independently powered form the power supply - not powered form the KryoFluxb.

I have tested with and without a drive attached to the KryoFlux, checked the jumpers, pressed the reset button, done the flash erase, used multiple USB cables that work with other devices, and attempted to use it on a Windows 7 desktop, a Windows 7 Laptop, a Linux Mint 19.2 desktop and a Linux Mint 18.3 ASUS UN42 Vivo and an Apple Airbook - none recognise the KryoFlux when it is plugged in.

When I use dtc -c2 on any of my machines while both the FDD is connected and not, I get the 'Device not found' message on all systems.

The GUI starts, settings are accessible and when I go to Calibrate I get an error

Command: ./dtc -l15 -d0 -c2
HostStartedEvent
DeviceError(DeviceNotFound)
HostFinishedEvent(true)

Linux 'lsusb' returns no new devices and when using 'udevadm monitor' and 'dmesg -w', no messages are generated when I connect the KryoFlux into a working USB port, but when I plug into the same USB port with any other device using the same cable I get connection messages from both commands.

On Windows 7, I see no system events telling me there is a new device attached, no new device appears in Device Manager and Windows does not prompt for the driver etc.

UPDATE - Also on windows
wmic path CIM_LogicalDevice where "Description like 'USB%'" get /value
does not show the attached KryoFlux.

Cheers
Chris

brightcaster
Posts: 224
Joined: Fri Nov 08, 2013 10:48 pm

Re: New KryoFlux not recognised by multiple systems

Post by brightcaster » Sat Nov 23, 2019 7:01 pm

Please check if there is a firmware.bin file in the same directory as DTC...

David

Sphaera
Posts: 3
Joined: Thu Nov 21, 2019 1:52 am

Re: New KryoFlux not recognised by multiple systems

Post by Sphaera » Sun Nov 24, 2019 12:38 am

Hi David,

Thanks for replying, I will focus on the Linux install.

As per the distribution, firmware_kf_usb_rosalie.bin is in the dtc directory with the dtc script. Another copy of the same .bin is locate in the firmware_fast directory. No other .bin files are in the distribution.

Here is the file structure from kryoflux_2.6_linux.tar.bz2 package.
.
├── ./docs
│   ├── ./docs/DTC_2.50_addendum.pdf
│   ├── ./docs/kf_quickstart.pdf
│   ├── ./docs/kryoflux_manual.pdf
│   └── ./docs/kryoflux_stream_protocol.pdf
├── ./DONATIONS.txt
├── ./dtc
│   ├── ./dtc/dtc
│   ├── ./dtc/firmware_fast
│   │   ├── ./dtc/firmware_fast/firmware_fast_README.txt
│   │   └── ./dtc/firmware_fast/firmware_kf_usb_rosalie.bin
│   ├── ./dtc/firmware_kf_usb_rosalie.bin
│   ├── ./dtc/i686
│   │   ├── ./dtc/i686/dynamic
│   │   │   └── ./dtc/i686/dynamic/dtc
│   │   ├── ./dtc/i686/libcapsimage.so -> libcapsimage.so.5.1
│   │   ├── ./dtc/i686/libcapsimage.so.5 -> libcapsimage.so.5.1
│   │   ├── ./dtc/i686/libcapsimage.so.5.1
│   │   └── ./dtc/i686/static
│   │   └── ./dtc/i686/static/dtc
│   ├── ./dtc/kryoflux-ui.jar
│   ├── ./dtc/kryoflux-ui_README.txt
│   └── ./dtc/x86_64
│   ├── ./dtc/x86_64/dynamic
│   │   └── ./dtc/x86_64/dynamic/dtc
│   ├── ./dtc/x86_64/libcapsimage.so -> libcapsimage.so.5.1
│   ├── ./dtc/x86_64/libcapsimage.so.5 -> libcapsimage.so.5.1
│   ├── ./dtc/x86_64/libcapsimage.so.5.1
│   └── ./dtc/x86_64/static
│   └── ./dtc/x86_64/static/dtc
├── ./g64_demo
│   ├── ./g64_demo/BBSB
│   │   ├── ./g64_demo/BBSB/bbsb.g64
│   │   ├── ./g64_demo/BBSB/BOUNTYBOBSTRIKESBACK_LICENCE.txt
│   │   └── ./g64_demo/BBSB/README.txt
│   └── ./g64_demo/DOTC
│   ├── ./g64_demo/DOTC/DEFENDEROFTHECROWN_LICENCE.txt
│   ├── ./g64_demo/DOTC/DefenderOfTheCrown_s0.g64
│   ├── ./g64_demo/DOTC/DefenderOfTheCrown_s1.g64
│   └── ./g64_demo/DOTC/README.txt
├── ./ipf_demo
│   ├── ./ipf_demo/lethalxcess_licence.txt
│   ├── ./ipf_demo/LethalXcess-WingsOfDeathII_DiskA.ipf
│   └── ./ipf_demo/LethalXcess-WingsOfDeathII_DiskB.ipf
├── ./LICENCE.txt
├── ./README.linux
├── ./RELEASE.txt
└── ./schematics
├── ./schematics/kryoflux_rosalie_rev_b.pdf
├── ./schematics/kryoflux_rosalie_rev_c.pdf
├── ./schematics/kryoflux_rosalie_rev_d2.pdf
├── ./schematics/kryoflux_rosalie_rev_d3_e.pdf
├── ./schematics/kryoflux_rosalie_rev_d.pdf
└── ./schematics/schematics_README.txt


From a system point of view the KryoFlux as a USB device is not being detected at the a hardware and kernel level and therefore it is not assigned a logical device in the operating system and so does not exist for any program to interact with.

brightcaster
Posts: 224
Joined: Fri Nov 08, 2013 10:48 pm

Re: New KryoFlux not recognised by multiple systems

Post by brightcaster » Sun Nov 24, 2019 11:01 am

Okay, if you just plug it in (without starting DTC) it should come up as "Atmel Corp. at91sam SAMBA bootloader" (with lsusb on your linux system). Maybe you missed that, because there is no name "Kryflux" involved at this stage.

If you start DTC the first time the firmware file gets loaded to the board and the LEDs should start to flash.

And yes, I wasn't aware the the name of the firmware file changed from firmware.bin to firmware_kf_usb_rosalie.bin some times ago.

So everything looks right and should work. As you said you have already done the test jumper procedure I have no further idea! I guess you have to send it in for a replacement...

David

Sphaera
Posts: 3
Joined: Thu Nov 21, 2019 1:52 am

Re: New KryoFlux not recognised by multiple systems

Post by Sphaera » Sun Nov 24, 2019 11:38 am

Hi David,
I can confirm that when the KyroFlux is plugged in to any of my systems no new device is added, lsusb does not report any additional devices after the KyroFlux is connected.

After launching DTC, no LEDs have flashed, only the red LED on constantly.

Well thanks for your help, who should I contact to arrange for a return for replacement?

Cheers
Chris

brightcaster
Posts: 224
Joined: Fri Nov 08, 2013 10:48 pm

Re: New KryoFlux not recognised by multiple systems

Post by brightcaster » Sun Nov 24, 2019 11:47 am

I think you should contact the people where you bought it from. If you bought it in the webstore at kryflux.com you may contact them per E-Mail at store@kryoflux.com...

David

Rakki
Posts: 753
Joined: Fri Jun 03, 2011 8:29 pm
Location: Jyväskylä, Finland

Re: New KryoFlux not recognised by multiple systems

Post by Rakki » Sun Nov 24, 2019 5:00 pm

Hi Chris,

Ok. The board seems faulty so we'll replace it. Please send an email to store@kryoflux.com and we'll provide details for returning the board.

https://kryoflux.com/?page=comp_contact

Post Reply