Hi, We have came to a situation where my Tiny6410 doesn't boot anymore. When I turn the board on, it lights D1 Led and keeps beeping without stop. There is no messages in COM0 (console) and it doesn't matter what position is S2 switch. I think I have bricked the board. I want to know if there is any chance to save it using some procedure. Best Regards,
Do you have a PC with a parallel port (not an adapter - the real thing) and the JTAG adapter that ships with the units?
I have the PC but not the JTAG (I received none). Is it a Wriggler? I can mount one, in that case, which procedure should I use?
I mean, which procedure should I use to recover Tiny6410 board once I have a Wriggler JTAG on my hand?
You wold need to rewrite the NOR version of the boot loader (superboot), in what is called the boot position of the NAND/Boot switch. I have not had to do it for a 6410 and will have to ask one of the engineers. If it is the same as the copy of superboot on the DVD, then SD-Flasher might be able to do the job. I'll ask one of the engineers who works on 6410. (I'll probably get referred to a user manual page I have not translated yet).
Thanks Charles, I have checked 6410 processor and it seems it has an IROM boot loader. I didn't get deep enough on docs to understand how it works, but I suppose that is what I should recover. I might be wrong. I will wait for further instructions from you. Best Regards,
Have you tried making a new SD to load the OS?
Yes! No console message, nothing. I think I might have burned the CPU.
It sounds like something is borken. Try sliding the NAND switch back and forth rapidly for a while. It is not the most reliable switch in the world. Knock the board against a hard table on all four edges. A tiny solder ball could be lodged between two leads or under the S3C BGA. Check that none of the pins in the headers and sockets are bent and touching another. Make sure the push buttons are not stuck. Where did you get the board? ARMWorks has a 2 year warranty.
What happened is that one of our employees applied -7V in input (7V inverted). I though it could have just erased some bootloader, but after studying the processor and IROM embedded bootloader I think that the board actually got burned out.