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

Need help with a 25L40 on a Via APC

Steve Zingman

New Member
I'm trying to read and then program a 25L40 in a Via APC (http://apc.io/)
The flash according to Via is a MXIC, part no. 25L4006E.
Below is the console log.

I have tried to read the device twice.
When I use the DOS compare (FC)
I get quite a few errors.
I also tried comparing the 2 files with Hex Workshop
Same result.
Any suggestions?

Thanks, Steve

LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 202
Welcome to FlashcatUSB interfacing software, build: 330
Running on: Microsoft Windows 7 Professional (32 bit)
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (JEDEC: C2 2013)
Flash detected: MXIC MX25L40 (524,288 bytes)
Programming mode: SPI (high-speed)
Beginning memory read from SPI Flash
Start address: 0 (0x00) Length: 524289
Read operation complete
Read 524289 bytes in 1.4 seconds, 375,296 Bytes/s
Beginning memory read from SPI Flash
Start address: 0 (0x00) Length: 524289
Read operation complete
Read 524289 bytes in 1.36 seconds, 386,644 Bytes/s
 
I am assuming you just have the FCUSB connected to the board and you are not using any other power source on the VIA board itself ?
If so it is strange that you should have different readings . Is this board bricked at the moment or is it in a working order ?
If it is currently bricked , do you get mismatch errors when writing to the device as well ?
I am hoping it is not a software issue as i am presently looking for a new coder to look into some issues we have with the software.
 
The VIA board is not powered by any other power source.
I have 1 bricked board and 1 working board. I do get mismatch errors when writing to the bricked board.
I tried clearing the bricked board with a console command you posted here on the board. It does show all FF
on the bricked board after the clearing command. Write still reports mismatch errors.

This is the first time I've used the FCUSB and I'm interested in recovering the bricked board,
but this is more about getting comfortable with the FCUSB and the software then a need to get the board running right away.

I can upload the dumps of the read if that will help debug.

Thanks, Steve
 
Apologies for the late reply , i have been busy at work.
I need to get someone to look at the code to see if there is any issues that stick out. Once i have got this checked i will reply here.
 
Sorry for not replying , but as of yet i am still unable to help.
The current developer/coder of blackcatusb is no longer around for a while , so in the meantime i have to search for a new coder.
As i only setup this forum for tech support i am now in the position where i would have to find a coder and fund the development out of my own pocket.
I do not sell any of these devices so i have no affiliation to anyone.So i do not profit from sales or anything of the kind.
So if you can be patient for a little while longer , hopefully i will find the person i need , to assist in the coding.
 
Sure I can wait. I was just wondering if you had any progress on finding a coder or if there was any work around I should try.

Thanks, Steve
 
Have a person in line for this , just waiting to see if he is interested ,,,

I was thinking what you could possibly try , if you get the Datasheet for your specific chip and in the SPI settings Tab , insert the relevant info from the datasheet onto that and see if this allows you a proper read/write
 
I have the same device.
Can you please, give me information how do you connect the board with Blackcat?
I'm getting error that the device is not supported.
 
@ Steve

I have managed to buy one of these devices , i should have it soon , and then hopefully i will be able to see where the issue lies ,,,, sorry for the amount of time it has taken , but i still have no coder , and these devices have been out of stock.
I have managed to read/write to this specific chip in a stand alone adapter , so it is possible that there may not be enough power from the FCUSB to power the chip properly
 
@ Steve

I have managed to buy one of these devices , i should have it soon , and then hopefully i will be able to see where the issue lies ,,,, sorry for the amount of time it has taken , but i still have no coder , and these devices have been out of stock.
I have managed to read/write to this specific chip in a stand alone adapter , so it is possible that there may not be enough power from the FCUSB to power the chip properly

No problem for the delay. If I knew you needed one to test, I would have sent you one.
I had no luck with the datasheet values. I did get a copy of the ROM from Via. I wrote it.
FlashCat reported errors, but I was then able to boot. I don't see anything wrong, but errors are errors. :)
 
I have the same device.
Can you please, give me information how do you connect the board with Blackcat?
I'm getting error that the device is not supported.

Hi,
I saw your post on the APC forum. When I get home tonight I'll post the connection info.

Steve
 
Hmm , interesting , so it booted fine after flashing a ROM from via ? even though you had mismatch errors ?

Tell me did you have as many mismatch errors with the new ROM as you did with your previous ones ?
 
I see what you mean with the errors now , in hex compare , i erased the whole flash using the Memory.EraseBulk() command and programmed a ROM back , i can see from the original ROM in hex there are the odd discrepancies , but it powers up ok.
I think this has something to do in the code with this being a smaller capacity Chip. I have tested it using usbjtagNT and that works perfectly . Once i can find someone who knows what to look for in the code i will get this rectified .
 
The diagram is fine , what firmware version are you using on the FCUSB ?
 
Back
Top