Tower S08LL64 Boards Won't Communicate with Three Different PCs!
What we've got here is a basic failure to communicate. Hopefully someone out there can help. Is anybody aware of anything that could cause non-communication between a tower S08LL64 board and 3 different PCs?
- Just got two brand new S08LL64 tower kits a few weeks ago.
- Either S08LL64 board will light up and run demo properly when PC is USB-connected directly to S08LL64 board NOT plugged into elevator boards (as outlined in the Quick Start Guide). Yes, driver seems to configure just fine.
- Either S08LL64 will light up and run demo properly when USB-connected directly to S08LL64 board properly plugged into elevator boards (primary card-edge connector attached to functional tower connector).
- CodeWarrior Quick Start project on DVD would not compile, so Freescale Tech Support had me download the latest version from their website. That newer version builds just fine, but when I try to download and debug, HiWave debugger says there is no communication with the hardware. Says "CHECK CABLE", but cable is fine.
- The Accelerometer demo project also will not download or debug. Same error message.
- In debugger, Connect option yields same error message.
- The above are all true for each of 3 different PCs, one running Win7 and two running XP. Only one of the PCs has ever had CW previously installed, but the other two PCs have fresh CW installs.
I'm not new to Freescale products and I've never had this much trouble with setting up any of their other demo boards in the past, so I hope I'm just missing something simple. However, the DVD-provided Quick Start CW project would not build, so maybe the docs also contain errors, like maybe the jumper settings are wrong? Or maybe CW 6.3 is the problem?
Thanks for any advice and suggestions.
Joel
Tags: S08LL64, bad, basic, communicate, failure, file, frustrating, project, won't
Replies to This Discussion
-
Permalink Reply by Philip Drake on -
Hi Joel,
I'm sorry to hear you are having trouble. I developed the code for the tower board and have had several occasions where the communications was not possible. And I'm speaking of the single wire debug communications not the serial communications. I was able to communicate through the RS232 interface with no issues. I think this is your case as well, correct.
So I understand that after you installed codewarrior and the update to codewarrior from the web and plugged in the tower board the drivers configured properly. That's great.
What I learned on earlier versions of codewarrior and earliy versions of the open-source BDM that is on the board is that when the LL64 was running in stop mode most of the time that the OSBDM would not be able to wake it up. I experimented with it a bit and found that if I was in one of the other demo states that the communcation worked ok.
I will looked up the procedure to update the OSBDM version. I believe laters versions have fixed this issue.
So try pushing button 2 which steps it to one of the other states, the light sensor versus pot comparison and then try to communicate with the debugger.
And you are correct in saying that you cannot communicate with the LL64 debugger through the elevator usb plug. You can power up and use the LL64 module but you cannot do debug through the elevator card. The Quick start guide refers to the LL64 board and the TWR-S08LL64 module.
I hope this helps.
-
Permalink Reply by Joel Koblich on -
Good day Philip,
Changing the demo mode solved the CW comm problem for both tower LL64 boards, alright. Thank you for pointing out this simple solution. I see now what is meant by the note in the lab pdf:
6. If the MCU is in low-power stop mode you
may see the message “There is currently
no communication…”Click “OK.”
Re-establish communication by hitting SW2
and under the Component > Set Connection,
set HCS08 and FSL open source BDM.
This re-establishes BDM communications.
I'd read that note before, but it was not quite clear, plus only the first half applied and "re-establish" seemed to imply that communication had already been established, but for us it had not. Thanks for clarifying.
We're currently evaluating the Tower for possible use by engineering university freshmen, so it's important that we get past these simple setup obstacles and make the tower as easy to use as possible.
Yes, if you can find the info on how to update the OSBDM and share it here, that would be great.
Also, you asked "And I'm speaking of the single wire debug communications not the serial communications. I was able to communicate through the RS232 interface with no issues. I think this is your case as well, correct."
Yes, that was our situation. The LL64 board RS232-to-PC comm link was fine.
-
Permalink Reply by ErichS on
-
Hello,
I had a similar problem: I was not able to communicate with my TWR-LL64 from several PC's. Even the trick with entering non-STOP mode (SW2) above did not work for me.
Finally, after some hardware modifications and a firmware upgrade I was able to overcome all my issues.
So I tried to use my P&E USB Multilink cable to connect to the board with soldering the 3x2 connector (J400) on the board.
First thing I noticed: the connnector is too close to the LCD glass, so you need to be really careful plugin in the BDM connector, as it conflicts physically with the LCD. But then I noticed that P&E did not work neither. I then got the tip to remove the 0-Ohrm resistor R411 (on the backside of the bord, near the J400). And guess what: the P&E Multilink was able to connect and flash the board!
But: if you remove the R411 resistor, you will not be able to use the OSBDM, or you close the R411 again. I'm checking if I could solder/glue a jumper on the backside of the board as re-soldering the SMD resisistor is a big pain.
Now about the OSBDM itself: I have found a new firmware which is supposed to solve a lot of issues, and one of it is the low power mode. But in order to flash the new firmware, you either solder the J402 (near the RESET switch) connector (and to use a BDM cable like P&E Multilink) or you solder the JP400 (near the RESET switch) jumper header. Install a jumper on the JP400 and use the Freescale JM60 GUI application to flash the new firmware with the bootloader.
Now with the updated firmware (firmware b25), I was able to use OSBDM as well :-)
© 2010 Created by TowerGeeks.
