Ok I was all stoked when I got home from work today because all my cables arrived from xconsoles. Used Uber's tut to update the nandx with my ck3i and bam I get and error during the verify state that said something about hex blah blah blah. So I start over and turn the power off and on and try and run it again and now all I get is autobaud error everytime.:mad2: Now I've done some reading about a usb hub, which I don't have, and resetting the nandx or changing ports. Looks like this happening to a few folks and I use TX products only, no homemade stuff or off brand stuff here. Any other ideas would be greatly appreciated because I feel like I just got my bubble burst.:frown:
Nandx autobaud error
- Thread starter bigO73
- Start date
Ubergeek
Xecuter Groupie
rdubbs007
VIP Member
I had that error with a sh*tty nettop I used in the garage, brought it in to use on my real desktop and bam worked like a champ.... just updated like 35 NAND-Xs too in about an hour an 15. So it is pretty much the bees knees.
Just saying maybe try a different computer or at least a different USB port (preferrably one that is not on the front of the PC, but directly headed on the motherboard).
Just saying maybe try a different computer or at least a different USB port (preferrably one that is not on the front of the PC, but directly headed on the motherboard).
Well honestly your guide is the only thing I have to go on lol. Tried putting in the 14.745 #, or something like that, and still getting autobaud error. It was updating when I first plugged it up but got some hex verify error towards the end. Can't be the computer because I just built this pup and its a beast.
I was pulling my hair last night because of this problem. I went to bed then had a bright idea.
Make sure the COM/USB switch on your CK3 Rev D is on USB!
LOL
Edit: You said CK3i mine was a CK3 Rev D
Make sure the COM/USB switch on your CK3 Rev D is on USB!
LOL
Edit: You said CK3i mine was a CK3 Rev D
Last edited:
Even though CG's vid was good, Ubers tut was sufficient enought. It's pretty straight forward actually. Just can't get it to program now. Autobaud error everytime after hours of fooling around with it.
Ok got a chance to work with this thing after working all week so after reading and trying to figure this out I've come up with a few issues. First I have just one red light on the nandx when I plug it up to the ck3i, which is normal. Second I notice that when I just plug up the nandx only I still get one red light and it does not show up in my device manager at all. As I said in another post when I originally hooked it up everything was programming fine until I got to the verify stage and got some kind of hex error. Now it looks like the nandx is completely blank and it won't show up on my computer at all. I figure if I can get it back to its original state I can try reflashing with no problems. Currently it looks like flash magic erase the original firmware and the nandx is just blank. Any suggestions would be appreciated.
Another user with Autobaud error.
Hardware :-
USB 2.0 and 3.0 tested (Intel X58 mobo)
Nand-X , brand new V2 , works as a reader/flasher
CK3 Pro (non rev D) PID 2303 , Driver 1.3.0 , works for DVD flashing
Update cables , branded TX and DIY cable (tested , has <0.03ohm resistance on all connections).
Flash Magic 5.94.2515 , settings exactly as per tut.
Any further details required to bug-fix this issue , just ask.
Hardware :-
USB 2.0 and 3.0 tested (Intel X58 mobo)
Nand-X , brand new V2 , works as a reader/flasher
CK3 Pro (non rev D) PID 2303 , Driver 1.3.0 , works for DVD flashing
Update cables , branded TX and DIY cable (tested , has <0.03ohm resistance on all connections).
Flash Magic 5.94.2515 , settings exactly as per tut.
Any further details required to bug-fix this issue , just ask.
mousey01
VIP Member
I had the same problem at first with my home made cable soldered directly to the nandx board, but on further investigation i noticed a single stand of wire had bridged onto another point of the board, once i sorted that it updated like a charm using ubers guide.
Just out of curiousity , I have just ordered a CK3i interface to see if that resolves the issue without changing any other factor in the equation.
I have 100% confidence in both cables (both the TX and diy ones) and in the NAND-X product. My PC is stable and 100% functional in all other uses so, my suspicion is that the 'issue' is either with the drivers not liking certain PC hardware configs (i.e. the drivers require further development) or that some 'older' revisions of the CK3 Pro are annoyingly temperamental when trying to flash the NAND-X.
Time will tell , next update will be when I get my CK3i and see if the issue is resolved by it or, persists.
I have 100% confidence in both cables (both the TX and diy ones) and in the NAND-X product. My PC is stable and 100% functional in all other uses so, my suspicion is that the 'issue' is either with the drivers not liking certain PC hardware configs (i.e. the drivers require further development) or that some 'older' revisions of the CK3 Pro are annoyingly temperamental when trying to flash the NAND-X.
Time will tell , next update will be when I get my CK3i and see if the issue is resolved by it or, persists.
I already have the ck3i and still have the problem. Tried the phillips app and it can't find the nandx. I'm just going to send it back to xconsoles and see if they can flash it cool, I'll pay the fee. If not just send me another one. My nandx has the one red light whether its hooked up through the ck3i or not. And it won't show up in device manager when I hook it up directly.
I'm in the same boat. I have a older ck3 pro and have tried 3 different pcs. All of them gave me the autobaud error. I've also tried the Phillips LPC2000 program. I get cannot communicate to test board with that program. So frustrating....
I am sure someone at TX will confirm this but , that sounds to me like you have somehow managed to erase the bootloader.
I am somewhat concerned by the lack of feedback from TX on this issue. Maybe they now believe that some people have a genuine issue (instead of assuming its a PEBKAC) but, would be nice to hear they are looking into it instead of us being seemingly being ignored.
Ubergeek
Xecuter Groupie
What do you mean by lack of feedback ?
There is no issue aside from some users setups not working as instructed. The hardware works as advertised. Every one sent back with this error we have been able to program immediately with no problems.
The instructions are clear. Alternative methods have been given and troubleshooting tips have been posted. Many many users have posted what they did to solve this problem. Aside from all that the next thing we can do for you is programming it for you.
To say there has been no feedback from us is ludicrous.
There is no issue aside from some users setups not working as instructed. The hardware works as advertised. Every one sent back with this error we have been able to program immediately with no problems.
The instructions are clear. Alternative methods have been given and troubleshooting tips have been posted. Many many users have posted what they did to solve this problem. Aside from all that the next thing we can do for you is programming it for you.
To say there has been no feedback from us is ludicrous.
Thanks for the reply Uber.
My feedback comment was purely in relation to the 'why is this occurring' not to actual answers on the forums.
So far we have had suggestions that users are incapable of doing it right (shouldn't be the default position no matter how often we see it to be the case), instructions from users of how they managed to 'Heath Robinson / Rube Goldberg' a way passed the problem and the addition of a secondary app to do the flashing (which in your own words was an awful program). This is all helpful in a community.
The fact that so far you have found it a simple process to flash every NAND-X that has been returned confirms that (assuming I and the handful of others aren't idiots) that the issue is driver based in the CK3/CK3i on some hardware configs (hence me posting mine).
I will end this with , I have EVERY faith in TX products (that's why I have been using them almost exclusively for 7 years). I also am 100% confident that this is not a hardware issue but, only an (annoying) configuration anomaly which will be hard to reproduce. That however doesn't remove the need for it to be addressed.
My feedback comment was purely in relation to the 'why is this occurring' not to actual answers on the forums.
So far we have had suggestions that users are incapable of doing it right (shouldn't be the default position no matter how often we see it to be the case), instructions from users of how they managed to 'Heath Robinson / Rube Goldberg' a way passed the problem and the addition of a secondary app to do the flashing (which in your own words was an awful program). This is all helpful in a community.
The fact that so far you have found it a simple process to flash every NAND-X that has been returned confirms that (assuming I and the handful of others aren't idiots) that the issue is driver based in the CK3/CK3i on some hardware configs (hence me posting mine).
I will end this with , I have EVERY faith in TX products (that's why I have been using them almost exclusively for 7 years). I also am 100% confident that this is not a hardware issue but, only an (annoying) configuration anomaly which will be hard to reproduce. That however doesn't remove the need for it to be addressed.
TimboZero, did the CK3i fix your issue. I think I am going to purchase one hoping that the issue is my old ck3 pro.
Won't have it till tomorrow , will update then.
One thing I wouldn't mind getting cleared up is when the CK3 Pro became a rev D with the need to reconnect the RXD. Was it when the capacitors were added or when the comms switch was ?
One thing I wouldn't mind getting cleared up is when the CK3 Pro became a rev D with the need to reconnect the RXD. Was it when the capacitors were added or when the comms switch was ?