JLink V8

[metal]

You mean this one is safe to buy?

[Top]

You mean this one is safe to buy?

No, I mean this is probably just the same as all the others but with patched firmware.

The GDBFULL trick will be easy for SEGGER to detect in future DLL releases. What you want to see is a clone running 4.50 and reporting GDBFull as a feature and not GDBFULL in uppercase.

I have disassembled the DLL and I have found some code that detects clones; it looks for serial numbers 11111117 or 805306163 and checks for the GDBFull feature if some other flag is set.

If you already have a V8 clone then just reflash with patched firmware.

[chinninitin]

Where can I get patched flashed firmware!

[metal]

No, I mean this is probably just the same as all the others but with patched firmware.

The GDBFULL trick will be easy for SEGGER to detect in future DLL releases. What you want to see is a clone running 4.50 and reporting GDBFull as a feature and not GDBFULL in uppercase.

I have disassembled the DLL and I have found some code that detects clones; it looks for serial numbers 11111117 or 805306163 and checks for the GDBFull feature if some other flag is set.

If you already have a V8 clone then just reflash with patched firmware.

That's what I expected. Unfortunately, I don't have one at hand now to experiment with it.

[Top]

Where can I get patched flashed firmware!

Try my modified firmware and let me know if it works?

I cannot test 100% as I only have v7 hardware

[dipchip]

I have a v8 clone also.
IAR 6.30 updated the firmware to jlink v4.42 and a few power cycles later it bricked.
I am wondering if anyone else has had experience with this?

So far, I cannot recover it.  The ERASE/TST sequence does not put the AT91SAM7S64 back into
usb program mode.  Is the new Segger firmware malicious, or is this just an isolated case
of hardware failure?

Any comments are welcome.

--Chip

[Top]

So far, I cannot recover it.  The ERASE/TST sequence does not put the AT91SAM7S64 back into
usb program mode.  Is the new Segger firmware malicious, or is this just an isolated case
of hardware failure?

I found nothing malicious so maybe it was a hardware fault but does it show up in Device Manager when you connect it?

[dipchip]

@Top
It 'tries' to show up in the device manager.  Win7x64 just shows it as an 'Unknown Device' when ever I plug it in.
I've done the ERASE/TST sequence more than a couple times... left it sit for more than a minute on each phase.
And, yes I have the SAM-BA and friends installed.

So, after hearing you found no malicious code, I'm leaning toward a hardware failure.
This is really bad timing

--Chip

Posted on: July 28, 2012, 08:01:36 20:01 - Automerged
I've found a supplier that sells the J-Link EDU for 60USD, kinda hard to argue with that.
How may disclaimers have you ever read that said "support the developers, if you like it, buy it!"
I'll order another mcu at the same time to try and repair the clone.  Should be an experience.

--Chip

[Top]

It 'tries' to show up in the device manager.  Win7x64 just shows it as an 'Unknown Device' when ever I plug it in.
I've done the ERASE/TST sequence more than a couple times... left it sit for more than a minute on each phase.

Are you sure you're following procedure for entering SAM-BA Boot Recovery?

TST, PA0, PA1 & PA2 pins high, power up, wait 10 seconds, power down. PA0, PA1 & PA2 will default with internal pull-ups but make sure nothing external is pulling them down.

[dipchip]

Top,
Thanks for the time and concern.
I went back to the documentation and re-read it to confirm I am shorting the right pins with the right voltage.
I dug out my logic probe... even sharpened the end of it with a file.. glad no one was watching.. lol.
Checked the levels on PA[012] and seen that they were correct while in TST mode.
I thought maybe the suppressor for DM+/- went bad... but that didn't make sense since I had 3V3 elsewhere.
I've tried the entire procedure on an XP-SP3 box (with SAM-BA installed) also, same result.

Like you... I hate to give up on it but I feel the magic smoke is gone.

--Chip

[orange]

There are many J-Link 8 price in this web site

http://www.aliexpress.com/wholesale?SearchText=j-link&catId=0&manual=y

[monkey]

I can confirm the new Chinese units work with 4.50K and latest .DLL files, and the features are spelt as per prior posts.

[Top]

I can confirm the new Chinese units work with 4.50K and latest .DLL files, and the features are spelt as per prior posts.

You mean with GDBFULL in uppercase?

[nooknikz]

Try my modified firmware and let me know if it works?

I cannot test 100% as I only have v7 hardware

Thank you very much, It work very good

[Alex5532]

has anyone tried the clone of thavali?

[baybay]

solution for verison v4.56d:

open JLinkARM.dll file using a hex editor (for example: HexWorkshop)

go to file offset 0x42220

replace 0xE8 0x8B  bytes to 0xEB 0x03

[BubbleBobble]

For those who need to recover the Chinese JLink clone:

- open the V8 firmware compiled on 2009 which can be found on this forum
- replace "GDBFull" with "GDB" string
- reflash the SAM7S64 using the SAM-BA procedure

I have an original JLink and the correct string is "GDB" and not "GDBFULL" despite it work in both cases.
I have tested it on several bricked JLink and everything is fine 

[reksbg]

solution for verison v4.56d:

open JLinkARM.dll file using a hex editor (for example: HexWorkshop)

go to file offset 0x42220

replace 0xE8 0x8B  bytes to 0xEB 0x03

Thanks baybay, your fix plus the firmware I'm attaching worked fine for me. Also the firmware can be updated to the one in 4.56d without any problem. Thanks again  .

[CrankCase]

I have a pretend J-Link V8 that was working fine until a few days ago on Segger 4.42a with an XP / SP3 system.  Its been working fine for months.  No changes on machine.  Suddenly it won't connect: get the "Device has Malfunctioned", Windows doesn't recognize it, etc.  Power rails are OK, etc.  Try different PC, same thing.  Removed Segger 4.42a from PC, wipe out any j-link USB drivers, reinstall everything, no change.  So I install SAM-BA 2.12, raise the TST pin high on the J-Link SAM7S64, power up the board for 10 sec, power cycle and re-connect.  Same thing - Windows XP shows as Unknown Device in device manager, and now when I go to update driver from list of devices it just shows "Unknown Device" as the only possibility.  Before I did the TST pin rick at least I could select a Segger or Atmel usb to serial driver from the list, but now its really dead.

I'm wondering if this J-Link has bit the dust?

[BubbleBobble]

@CrankCase

I suggest you to:

1- verify the voltage regulator it works supplying the 3V3 to the Atmel microcontroller
2- Boot a Linux live image (like Xubuntu or Mint Mate), open the terminal, then plug the J-Link and see the output of the command "dmesg". At least you can see if the Atmel microcontroller is working or not.

If the Atmel respons, you might think to erase the entire flash using the ERASE pin and then flash a new J-Link firmware. I did this lot of time without any issues.

[CrankCase]

Getting closer - 3.3V rails verified OK.

Yeah, that's what is was.  I had to hit the ERASE pin with the VDD while it was powered up, THEN did the procedure with the TST pin. NOW it will connect up to Windows where I've got SAM-BA installed, and it will install the the driver for "AT91 USB to Serial Converter".  That's all good now.

Except when I run SAM-BA, I select the USB deivce / Com 9 (That's what the driver reports it as) , select 'Sam7S64,, and connect - and the rest of Sam-BA never opens up.  I have double-checked the crystal at 18.432Mhz.

If I could just get to the next step of loading firmware....

Posted on: December 27, 2012, 12:02:50 12:02 - Automerged
Well, I moved to another PC.  Got SAM-BA installed and this time it went slicker than snot - got the modified BIN file loaded, power cycled the cloned J-Link and now it thinks its a J-Link again, and this time Segger 4.58 is running fine.

Seems to be talking to the M3's again.

Thanks BB!!

[chinninitin]

Hi,

can some one help me with .BIN file programing to JLink with SAM-BA, any snapshot of settings or any procedure?

Regards,
Chinni

[BubbleBobble]

@CrankCase
You can find an old version of J-Link V8 firmware on Internet. Google for it.

After found the BIN file, you have to open it with an hex editor and change the string "GDBFull" with "GDB" and also change the serial number.
As far as I remember the serial number is not a string but just raw hex data nearby the address where the "GDBFull" string is located. Remember the raw data are little-endian. For the new serial number use something like "4054xxxx" where xxxx are random numbers.

Save the new BIN file and flash the erased J-Link using SamBa procedure.

At the moment I am on holidays and I can't provide you the BIN file patched just now. If you have any troubles please wait till the second week of this January when I go back to office. Update us how is going.

@chinninitin
At the moment I am on holidays, I can explain step by step the procedure after the 1st week of this January when I go back to office.

[urosg]

I just fixed my cloned jlink with the firmware in attachment.

I did the "ERASE" and "TST" procedure to get the SAM-BA functionality back to the MCU and then flashed it with the new firmware after that I also did the upgrade JLINK software suggested and it works AOK.

[chinninitin]

I just fixed my cloned jlink with the firmware in attachment.

I did the "ERASE" and "TST" procedure to get the SAM-BA functionality back to the MCU and then flashed it with the new firmware after that I also did the upgrade JLINK software suggested and it works AOK.

Hi,
Can you post screenshots/procedure  of SAM-BA, to flash JLINK with .bin file which you posted.

Thanks
Chinni