• Visit https://www.embeddedcomputers.net/ for Hardware; Software and all other things related to FlashcatUSB

Samsung K9F1G08U0C with FCUSB Export 2.0 crashes software ver. 577 or higher

Sparks

New Member
When I try to use FlashCat build 577, 578, or 580 to read a Samsung K9F1G08U0C NAND chip, the program crashes back to the desktop without any error messages.

This is what I found in the Windows Event Log:

Faulting application name: FlashcatUSB.exe, version: 1.0.0.0, time stamp: 0x5d5a7c26
Faulting module name: KERNELBASE.dll, version: 10.0.17763.615, time stamp: 0x832170f2
Exception code: 0xe0434352
Fault offset: 0x0011fd62
Faulting process id: 0x146c
Faulting application start time: 0x01d560508209bc18
Faulting application path: C:\Users\Sparks\Downloads\FCUSB_BUILD580_081919\FlashcatUSB.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 285c16e1-b2a0-4ec5-a49e-55089512f732
Faulting package full name:
Faulting package-relative application ID:

Details:

- <Event xmlns=" ">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-08-31T23:06:45.393290400Z" />
<EventRecordID>5282</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-VACF3C8</Computer>
<Security />
</System>
- <EventData>
<Data>FlashcatUSB.exe</Data>
<Data>1.0.0.0</Data>
<Data>5d5a7c26</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.17763.615</Data>
<Data>832170f2</Data>
<Data>e0434352</Data>
<Data>0011fd62</Data>
<Data>146c</Data>
<Data>01d560508209bc18</Data>
<Data>C:\Users\Sparks\Downloads\FCUSB_BUILD580_081919\FlashcatUSB.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>285c16e1-b2a0-4ec5-a49e-55089512f732</Data>
<Data />
<Data />
</EventData>
</Event>

Directly under that in the event log is this entry:
Event 1026, .NET Runtime
Application: FlashcatUSB.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at FlashcatUSB.PARALLEL_NOR_NAND.DeviceInit()
at FlashcatUSB.MainApp.DetectDevice(FCUSB_DEVICE)
at FlashcatUSB.MainApp.OnConnectedEvent(FCUSB_DEVICE)
at FlashcatUSB.MainApp.OnUsbDevice_Connected(FCUSB_DEVICE)
at FlashcatUSB.USB.HostClient.ConnectionThread()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Details:

<Event xmlns=" ">
- <System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-08-31T23:06:45.163180600Z" />
<EventRecordID>5281</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-VACF3C8</Computer>
<Security />
</System>
- <EventData>
<Data>Application: FlashcatUSB.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at FlashcatUSB.PARALLEL_NOR_NAND.DeviceInit() at FlashcatUSB.MainApp.DetectDevice(FCUSB_DEVICE) at FlashcatUSB.MainApp.OnConnectedEvent(FCUSB_DEVICE) at FlashcatUSB.MainApp.OnUsbDevice_Connected(FCUSB_DEVICE) at FlashcatUSB.USB.HostClient.ConnectionThread() at System.Threading.ThreadHelper.ThreadStart_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart()</Data>
</EventData>
</Event>
 
I have also tried with a Samsung K9F1G08U0B nand chip (listed as a compatible chip) with the same result.
However, I am able to successfully dump both chips using Flashcat build 576 and board firmware version 5.04

I have attached the log from Flashcat build 576 in case it provides the developers with any clues. Please note that this is using the Samsung K9F1G08U0C chip, even though it is detected as a K9F1G08U0B.


FlashcatUSB Script Engine build: 302
Welcome to the FlashcatUSB interfacing software, build: 576
LibUsbDotNet version: 2.2.8.104
Running on: Microsoft Windows 10 Pro (64 bit)
Serial NOR memory database loaded: 376 devices supported
Serial NAND database loaded: 35 devices supported
Parallel NOR memory database loaded: 305 devices supported
Parallel NAND memory database loaded: 152 devices supported
OTP/UV EPROM memory database loaded: 16 devices supported
Connected to FlashcatUSB XPORT, firmware version: 5.04
Firmware features supported: SPI, I2C, EXTIO
Initializing EXT I/O hardware board
EXT I/O board successfully initialized
Attempting to automatically detect Flash device
Mode NAND X8 returned ident code: 0xECF1009540
Successfully detected device in NAND X8 mode
Connected to Flash (CHIP ID: 0xECF1009540)
Flash detected: Samsung K9F1G08U0B (134,217,728 bytes)
Programming mode: EXT I/O (Parallel)
Flash page size: 2048 bytes (64 bytes extended)
Block size: 0.13 MB
Device interface: NAND (X8 3.3V)
NAND block manager disabled
NAND memory map complete: 65,536 pages available for access
 
Using FlashcatUSB build 582 no longer crashes the program, but the contents of my Samsung K9F1G08U0C chip is now shown as all zeros, and I am unable to read the chip. If I try to refresh with the F1 key, the "Nand X8 Flash" tab vanishes, and the program no longer responds. I need to reset the FCUSB by unplugging it and plugging back in, or using the black reset button on the hardware before the software will see the FCUSB Export harware again.

Should I start a new thread in the hardware section?
Is there anything I can do to help the developers fix this problem?

Here is the log file just in case:

FlashcatUSB Script Engine build: 305
Welcome to the FlashcatUSB interfacing software, build: 582
LibUsbDotNet version: 2.2.8.104
Running on: Microsoft Windows 10 Pro (64 bit)
Serial NOR memory database loaded: 387 devices supported
Serial NAND database loaded: 35 devices supported
Parallel NOR memory database loaded: 307 devices supported
Parallel NAND memory database loaded: 161 devices supported
OTP/UV EPROM memory database loaded: 16 devices supported
Connected to FlashcatUSB XPORT, firmware version: 5.08
Firmware features supported: SPI, I2C, EXTIO
Initializing EXT I/O hardware board
EXT I/O board successfully initialized
Attempting to automatically detect Flash device
Mode NAND X8 ASYNC returned ident code: 0xECF1009540
Successfully detected device in NAND mode
Connected to Flash (CHIP ID: 0xECF1009540)
Flash detected: Samsung K9F1G08U0B (134,217,728 bytes)
Programming mode: EXT I/O (Parallel)
Flash page size: 2,048 bytes (64 bytes extended)
Block size: 131,072 bytes
Device interface: NAND (X8 3.3V)
NAND block manager disabled
NAND memory map complete: 65,536 pages available for access
 
Thank you!
Let me know if you need any more info from me, and I will do my best to get it to you in a timely manner.
 
I am still having the same problem using build 585.
Here is the console output if it helps any:

FlashcatUSB Script Engine build: 306
Welcome to the FlashcatUSB interfacing software, build: 585
LibUsbDotNet version: 2.2.8.104
Running on: Microsoft Windows 10 Pro (64 bit)
Serial NOR memory database loaded: 387 devices supported
Serial NAND database loaded: 35 devices supported
Parallel NOR memory database loaded: 307 devices supported
Parallel NAND memory database loaded: 165 devices supported
OTP/UV EPROM memory database loaded: 16 devices supported
Software requires firmware version 5.09
Disconnected from FlashcatUSB Classic device
Software requires firmware version 5.09
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB in bootloader mode
AVR DFU command successful
Beginning AVR flash write (27660 bytes)
AVR flash written successfully
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB XPORT, firmware version: 5.09
Firmware features supported: SPI, I2C, EXTIO
Initializing EXT I/O hardware board
EXT I/O board successfully initialized
Attempting to automatically detect Flash device
Flash device not detected in Extension I/O mode
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB XPORT, firmware version: 5.09
Firmware features supported: SPI, I2C, EXTIO
Initializing EXT I/O hardware board
EXT I/O board successfully initialized
Attempting to automatically detect Flash device
Flash device not detected in Extension I/O mode
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB XPORT, firmware version: 5.09
Firmware features supported: SPI, I2C, EXTIO
Initializing EXT I/O hardware board
EXT I/O board successfully initialized
Attempting to automatically detect Flash device
Mode NAND X8 ASYNC returned ident code: 0xECF1009540
Successfully detected device in NAND mode
Connected to Flash (CHIP ID: 0xECF1009540)
Flash detected: Samsung K9F1G08U0B (134,217,728 bytes)
Programming mode: EXT I/O (Parallel)
Flash page size: 2,048 bytes (64 bytes extended)
Block size: 131,072 bytes
Device interface: NAND (X8 3.3V)
NAND block manager disabled
NAND memory map complete: 65,536 pages available for access
 
Using the same Samsung memory chip, version 576 will read the contents, but while version 585 detects the chip, it shows it as all zeros. If I try to refresh the device with F1, the NAND X8 Flash tab disappears, and the programmer acts like it's locked up. I have to unplug the usb cable or press the small black reset button on the programmer before it will respond.
576.jpg
585.jpg
Not Responding.jpg
 
Hmmm, this sounds like a RYBY pin issue maybe? I'll double check current software with a K9 NAND and see.
 
OK,
I have verified all traces and solder joints with both visual inspection and by ohm meter, all the way from pin #16 of the Atmel controller (PCINT6/OC.1B) PB6, to pin #7 on the Nand adapter (Ready/Busy Output) and to the top side of pin #7 on the Samsung K9F1GU0B just to make sure the Nand chip was making good contact in the socket.
Short version, everything checks out with zero resistance.
My question is, if it truly is something wrong with the RBO setup, why am I able to read the chip using FlashCat build 576?
 
Back
Top