Multiple Flash Locations

Topics about unsupported flash in here. Also please go here regularly to update your flash.def
Locked
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

Multiple Flash Locations

Post by Jason »

When I connect jtag NT to a 6412 with AMD flash I get
Found Address= 9c000000 AMD 29lv320MB
Found Address= 9c420000 AMD 29lv320MB
Found Address= 9cfc0000 AMD 29lv320MB
When I did the same unit last night I got
Found Address= 9c000000 AMD 29lv320MB
Found Address= 9cfc0000 AMD 29lv320MB
When I do Intel I get (different unit)
Found Address= 9c000000 Intel 28F128J3
Why do I get multiple flash locations? Does it have something to do with the upper and lower memory locations? Does Intel mask the chip to look like one were AMD can't so you see each part you can program? Why did it not give me the center flash type (Found Address= 9c420000 AMD 29lv320MB) sometimes and sometimes it does?
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

Your problem should be perfectly solved with USB JTAG NT 0.18. Try that one. Old JTAG will not detect AMD flash properly.
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

Post by Jason »

I will give it a try. I did notice that this happens only when I load the modified version of the xls file with the plat sectioned out.
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

Post by Jason »

Ok i tried it. It took a while for some reason after I would extract the file into the same directory it still kept the old file. I had to extract to another directory and then copy and paste. I am still seeing 3 flashes when I use my modified xls for mult plats. Could I send or post you that file and you see if I did something wrong? And how do I post or send a file?
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

So Close

Post by Jason »

This is what it said after I upgraded to 0.18
Found Address= 9c000000 S29GL320
Found Address= 9cfc0000 S29GL320
When I use the unmoded dct6412 the flash type was right on the first one. Now that I upgraded I get a different flash type. I'm still gettting three with my moded plat(1,2,3,,) tabs
Thanks again BDM
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

Since you have modified the tabs. I do not know what went wrong. Mayeb you can post your xml for the TDCT6412.xml.
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

File

Post by Jason »

Ok I hope this is how you do it. What about the flash type coming up wrong now that I upgraded? I know the multiple fash locations are because of the modified XML. I also uploaded the flash.xml file incase it's the reason I am getting the wrong flash type after upgrading.
You do not have the required permissions to view the files attached to this post.
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

2 Questions

Post by Jason »

Looked over both flash.xml files. The only difference is AMD 29lv320MB is listed under 0x227E and 0x2200. On version 0.18 0x227E is named S29GL320. Which is what jtag detects. So only the name is different. I guess my question is should a AMD 29LV128ML detect as 0x227E (which is what is happening no matter which version I use)? When I do a search in flash.xml for AMD 29LV128ML (which is what I read on top of the chip) it's not found. Or should the program say what the physical chip says? I hope you can understand all the garbage I just typed. Thanks again bdm.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

0.18 you should use CFI to get the flash. Which will be always be right. Check your flash to see if it is 29G064 instead of 032 or 320.
The CFI has not been implemented to MIPS64 yet and that is a bug. I will try to solve this issue soon.
I will release 0.19 to solve your problem. So no worry. Should be able to release before Saturday.
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

Happy

Post by Jason »

I don't understand all of that (I will research it), but you the man you the man. This has really helped my job..(You have really helped my job) sorry for all the trouble.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

Jason, I have fixed the CFI for MIPS 64. So for DCT6412 I can get the flash right.
Now I want to fix the program speed for AMD with buffer on MIPS 64. If you can setup teamviewer and go online tomorrow night I will be able to debug the next release on your box. It will be about 350KB/s for the AMD flash with buffer write.

This you will get for Intel chip

detect
IDCODE 1703817F
Broadcom BCM7038
IMPCODE 40404001
DMA not supoorted
Found Address= 9c000000 CFI Intel128

AMD will auto detect the 128Mbit flash rather than four duplicate flash.
Jason
Junior Member
Posts: 65
Joined: Fri Nov 09, 2007 4:23 am

Rdy

Post by Jason »

Ok. I went to the site and it answered all my questions. I have it installed. Will I need to have cable input to the box. (I don't think so, but needed to ask)
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

You only need to wait in the chat tonight and no more cable is needed. I will then send you test code and we can have the problem (slow programming on your flash) solved. 0.19 will be released to have following features
1 Add "sgetram" "ssetram" "scmpram" command. This is for future GDB support as well as DCT700 and SB5120 that is bricked and cannot access memory (normal getram and setram will not work).
2. Add CFI support on MIPS64 and fix all the programming issue that is already fixed in MIPS32.
UserName
Junior Member
Posts: 268
Joined: Sat Jun 07, 2008 2:56 pm

Post by UserName »

its the flash settings. that is all.
do not believe what i say 10% its true :confused:
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

Try 0.19 now it should solve your problem now.
Locked

Who is online

Users browsing this forum: No registered users and 4 guests