Home › ELEKTOR FORUMS › DigiButler (April & May 2008) › TBLCF - Error: Connect failed

ELEKTOR FORUMS

Please log in to post a reply or subscribe / unsubscribe to topics

Topic: TBLCF - Error: Connect failed

Author Post

EvFarm

15 posts

Popping In
Popping In

Read post 10-12-2008 17:29

OK, I built the digibutler - seems to work OK (I get serial port output) but I need to change the IP address so...

I bought TBLCF board and parts. Assembled OK. Followed instructions in TBLCF manual to install the drivers and program - seems fine.

Then I downloaded and installed CodeWarrior 7.1
I modified the Digibutler source as described elsewhere on this forum and recompiled - seems OK, no errors.

Set jumpers on Digitbutler as described. Plugged everything in (pin1 on TBLCF to pin1 on Digibutler connector) Selected "Tools/Flash programmer".
Then I set the Target Configuration as described (well almost, there is no config file called M52235EVB_pne.cfg but I did find one called M52235EVB.cfg so I picked that).
Then I went to the flash config menu and selected CFM_MCF52230 (there is no 25MHz option).
Then I went to the erase menu and pressed the "ERASE" button but I just get "Error: Connect failed".

Any idea where I am going wrong? I am a little concerned that the exact config options described in the magazine don't seem to actually exist.

Please help - I've come a long way with this project and don't want to be defeated so close to finishing.

- Andy

EvFarm

15 posts

Popping In
Popping In

Read post 10-12-2008 17:43

A small update. Still not working though.

I realised I had not loaded the settings on the Flash programmer dialog correctly. Also I now found the MCF5223_pne.cfg file (not MCF52235 as described) - it's in the project zip. So I loaded that. Then I tried load settings and selected the setup.xml from the DHCP post on this forum. But now I get a new error message from CodeWarrior 7.1. It says:-

"TBLCF GDI connection setting in current configuration file is not available; setting connection to first in list"

What does that mean?

- Andy

EvFarm

15 posts

Popping In
Popping In

Read post 10-12-2008 18:03

Ok OK, progress!
After poking about a bit more to see how things work I realised I had not completed the final stage of the TBLCF instructions - that part where you tell CodeWarrior how to connect to the TBLCF.

SO, now I've done that.
The erase and blank check passed.
Then I selected "Program" and downloaded the updated "web coordinator.S19" image file.

Yay! It works, and it is on my new IP address too.

Well, that was all a bit of an ordeal. There are a lot of stages to get just right to get this far. The result is not quite the simple turnkey ICSP solution I am used to with PICs and AVRs. If anyone implements a serial bootloader for CF chip I'm sure that could make things much simpler (and would then not need the TBLCF after the first time).

My advice to anyone struggling with this is to persevere (and post in here).

Thanks for the "cardboard cutout" support. If I had not written my experiences to somoeone I would not have found the problem.

- Andy

hakann

62 posts

Frequent Visitor
Frequent Visitor

Read post 13-12-2008 10:48

Good you got there with the new firmware loaded! Yes, there are some steps on the road. One have to be careful and not forget something. I did the mistake of first activating DHCP, and then regretting it, going for another hardcoded address instead. This had some implications on "defines" in the code. I didn't give up and finally solved it.

I also have made the reflection that a bootloader would be nice. Once loaded, you don't need any TBLCF unless doing debugging. A bootloader in from the start would be good. No need for any TBLCF at all for reflashing.

Groen

10 posts

Popping In
Popping In

Read post 29-12-2008 14:50

Hi,

I have some problems with programming the firmware in the interface. Following the manual step 6 (page 16) the messages appeared:
found 1 HC08JB16 ICP device(s)
Boot sector contents different, performing mass erase
Mass erase done, programming boot sector
Programming done, verifying boot sector
Verification done, boot sector OK. You can start breathing again.
Erasing block at address: 0xF800
Programming block from 0xBA00 to 0xcc74
USB communiation problem or programming failure

I've tried it several times but the same results.

Any sugegstions?
Thanks,
Bas

Please log in to post a reply or subscribe / unsubscribe to topics

Subscribe now

Free Newsletter!

News, tips, offers, videos and more. Take out a free membership to Elektor.POST. In your email inbox each Friday!

 

Enter your Email address:

Follow Elektor

      

Act now!

FAQ

Before submitting questions, review our FAQ section!

Package Deals

Elektor Bundles

Check our Package Deals and save money! Discounts up to 19% now available!

Price Slashed

Elektor OSPV

This Open Source People Vehicle is perfect for factory halls, warehouses, hospitals, colleges, schools etc.