USBJTAG NT crash issue

Report bugs found in the software. New release will fix those busg.
Boxnut
Posts: 20
Joined: Wed Feb 12, 2020 2:46 am
Location: Northwest US
Contact:

USBJTAG NT crash issue

Post by Boxnut » Sat Mar 07, 2020 12:54 am

Hi folks. I have a bad issue, USBJTAG NT crash. About to scrap this so tested it on a known good development board.
Now the board works just fine save for some problems with work around, but I have 6 satellite IRDs looking to jtag.
one on the front burner is Samsung sir-s70. I recall this functioning at one time but unreliable results.
Crash problem now if the target is powered at all, message popup. USBJTAG has stopped working.(unknown problem) and windows closes the program.
Sequence of starting up doesnt matter, the jtag will idle, them power up the target it crashes. target powered, starting the program, it crashes.
Cant help but wonder if this is a problem with my XML addon. Read through the sketchy XML how to.
Would it be too much work posting detailed field data. including extended fields and on-CPU memory. That would help add to the XML list.
Found my old jtag files from 2003 and an add to the 'DEF' file for JKEYS. That jtags anything, so have any info that may be needed.
The basics:
CPU - STi 5518MVB, St20 core (in XML)
RAM - Samsung K4S641632F --- I could add that if I knew the XML field details.
FLASH - Intel 28F320J3 (in XML)
EEPROM - 24LC128 (in XML) (yet need to confirm the SPI port this is on) 0,0 seems to work.
Sure would love to use USBJTAG NT for all my jtag work so any help would be hot.
Some of my information may be incorrect, incomplete,or just plain wrong. Seems I am human. :D

usbbdm
Posts: 8550
Joined: Mon Jul 18, 2005 9:33 pm

Re: USBJTAG NT crash issue

Post by usbbdm » Sat Mar 07, 2020 6:46 am

Please attach the XML file here

usbbdm
Posts: 8550
Joined: Mon Jul 18, 2005 9:33 pm

Re: USBJTAG NT crash issue

Post by usbbdm » Sat Mar 07, 2020 9:12 am

I am glad people reporting bugs here instead of me trying to find bugs.
If I can reproduce your crash I sure will release a fix in no time.

usbbdm
Posts: 8550
Joined: Mon Jul 18, 2005 9:33 pm

Re: USBJTAG NT crash issue

Post by usbbdm » Sat Mar 07, 2020 9:16 am

Could be a NULL pointer somewhere. Need to step on the issue to be able to fix it.

Boxnut
Posts: 20
Joined: Wed Feb 12, 2020 2:46 am
Location: Northwest US
Contact:

Re: USBJTAG NT crash issue

Post by Boxnut » Sun Mar 08, 2020 6:58 pm

usbbdm wrote:
Sat Mar 07, 2020 9:12 am
I am glad people reporting bugs here instead of me trying to find bugs.
If I can reproduce your crash I sure will release a fix in no time.
Lets see if I can make this work.
<Test>
<Name>SIR S-70</Name>
<Cat>DishIrd</Cat>
<Protocol>DCU</Protocol>
<SubProtocol></SubProtocol>
<Endian>Little</Endian>
<IRLength>5</IRLength>
<Programram>0x7fc00000</Programram>
<Memorys>
<Memory>
<Name>Ram</Name>
<Type>0</Type>
<Address>0x40000000</Address>
<Size>0x400000</Size>
</Memory>

<Memory>
<Name>flash</Name>
<Type>0x1</Type>
<Address>0x7FC00000</Address>
<Size>0x400000</Size>
</Memory>
</Memorys>
</Test>
>>Keep in mind this works just fine with an ARM development board, Just doesn't seem to like boxes with STi5518MVB.
Some of my information may be incorrect, incomplete,or just plain wrong. Seems I am human. :D

Boxnut
Posts: 20
Joined: Wed Feb 12, 2020 2:46 am
Location: Northwest US
Contact:

Re: USBJTAG NT crash issue

Post by Boxnut » Sun Mar 08, 2020 7:08 pm

Tried this on a SB6121 and also works,,that is 2 of your XML are working,,none of mine do. May be MY bad, but until I can get field detail for the XMLs I feel like sailing with no rudder in the water.
Some of my information may be incorrect, incomplete,or just plain wrong. Seems I am human. :D

usbbdm
Posts: 8550
Joined: Mon Jul 18, 2005 9:33 pm

Re: USBJTAG NT crash issue

Post by usbbdm » Mon Mar 09, 2020 11:22 am

I will try to find if I still have the 5518 box and try your xml.

usbbdm
Posts: 8550
Joined: Mon Jul 18, 2005 9:33 pm

Re: USBJTAG NT crash issue

Post by usbbdm » Mon Mar 09, 2020 5:22 pm

I could not find the STi5518 box any more. But you can try replace with this line
<Programram>0x80000200</Programram>

Boxnut
Posts: 20
Joined: Wed Feb 12, 2020 2:46 am
Location: Northwest US
Contact:

Re: USBJTAG NT crash issue

Post by Boxnut » Wed Mar 11, 2020 3:38 pm

usbbdm wrote:
Mon Mar 09, 2020 5:22 pm
I could not find the STi5518 box any more. But you can try replace with this line
<Programram>0x80000200</Programram>
I will give that a shot. A new thing I found that may be the source of the problem is creating the XMLs with notepad.
Put a few under the hex workshop scope and found working XMLs have 09h for white space, where mine have 20h.
Re edited the XML and will try that and keep you posted, also on your entry.
Some of my information may be incorrect, incomplete,or just plain wrong. Seems I am human. :D

Boxnut
Posts: 20
Joined: Wed Feb 12, 2020 2:46 am
Location: Northwest US
Contact:

Re: USBJTAG NT crash issue

Post by Boxnut » Wed Mar 11, 2020 3:43 pm

I remember years back working with JKEYS def files, they are very critical but will ignore space,cr-lf pairs so notepad works with those.
These XMLs are not much different.
Some of my information may be incorrect, incomplete,or just plain wrong. Seems I am human. :D

usbbdm
Posts: 8550
Joined: Mon Jul 18, 2005 9:33 pm

Re: USBJTAG NT crash issue

Post by usbbdm » Wed Mar 11, 2020 6:24 pm

Someone will send me a box of DCU target and I hope I can find the issue.

Boxnut
Posts: 20
Joined: Wed Feb 12, 2020 2:46 am
Location: Northwest US
Contact:

Re: USBJTAG NT crash issue

Post by Boxnut » Thu Mar 12, 2020 10:52 am

An update for you. My notion and your change to the programming field did not help, this still crashes when the target is powered up.
This does the same with an ADTH 8600 IRD also, near the same hardware as the S70.
I believe in Einstein that every problem has a solution so I will pick away at this until I solve it.
Thank you much for the time you are distracted with this.
Some of my information may be incorrect, incomplete,or just plain wrong. Seems I am human. :D

Post Reply