Today I tried to install build 1797 (or whatever it is) that was released today and first of all Samba-BA v2.10 once again failed to recognize my calculator and MySamba recognizes the COM but I keep getting "Failed to Connect" screen - no matter what COM I choose. I used another computer and that computer didn't even recognize the calculator even AFTER I installed the driver.
I am using EasySync ES-U-1001-R10 (US232R-10) - because that cord worked the last time. However it doesn't now and I'm back to having a dead 20b.
I am using Windows Vista. It doesn't matter how many times I download the driver.
I am putting a request for a cord that goes straight to USB cord without any need for a serial adapter because I can't imagine that I'm the only one with these problems.
-----------------------------------
I should have enough saved up to buy an updated 15CE if HP gets the PSE thing fixed.
Marcus, when you have version 2 stabilized and officially released, I aim to buy an updated WP 34S from you.
Update: I downloaded the MySamba that was just released. Sadly, no success. I keep getting the Unable to Connect error.
Edited: 25 Oct 2011, 11:05 p.m.
Ed. The dead 20b is most probably no longer listening to the serial port due to flat batteries.
1. Only connect the cable while flashing!
2. Once in SAM-BA mode, remove the batteries if you do not succeed on the first try. SAM-BA will eat them quickly.
As for the USB cable you mentioned: Yesterday I built my own from an FTDI 3.3V-TTL cable and the original HP cable. I stripped the level shifter off the board inside the cable case and connected RX/TX/GND directly. In order to power the calculator from the cable, I added an external connector for a wall wart. Using the USB supply would need a 3V voltage regulator which I don't have. Maybe some kind soul redesigns the tiny board to contain a mini USB socket, an FTDI chip, and a voltage regulator, besides the two buttons, to make this a viable option for all of us.
Eddie,
I can tell you that I have gotten MySamBa (Marcus' version of the program available at Sourceforge) to work with Vista and the same USB-to-serial converter that you have, as described here. Did you right click on the MySamBa.exe file and tell it to run in XP compatibility mode?
I may have forgot to do that. I'll check. Thanks.
So I checked the Compatibility Mode, put new batteries, connected the calculator when the cord was flashing (which was all but a millisecond it seems) - STILL THE SAME RESULT: NO CONNECTION.
So I am back to the Samba CDC program - I click on COM 7 - and the program disappears! Then when I unplug the adapter I get this long error message:
error reading "file2d0e110": I/O error
while executing
"read $fd 4"
(procedure "TCL_Read_Int" line 6)
invoked from within
"TCL_Read_Int $target(handle) $cidr_addr err_code"
("foreach" body line 10)
invoked from within
"foreach cidr_addr $addresses {
#Check the processor ID
set err_code 0
set version_mask 0x0FF0..."
invoked from within
"if {$target(board) != "no_board"} {
set srcDevld [file join $libPath(extLib) "devices" "devices.tcl"]
if {[catch {source "$srcDevld"} errMsg]}..."
(file "C:/Program Files/AMTEL Corporation/SAM-BA
v2.10/sam-ba_cdc.exe/lib/tkcon.tcl" line 4950)
invoked from within
"source [file join $starkit::topdir lib/tkcon.tcl]"
(file "C:/Program Files/ATMEL Corporation/SAM-BA
v2.10/sam-ba_cdc.exe/main.tcl" line 7)
This is the in the window "Error in startup script". Hopefully someone knows what is file is missing (if I am understanding this message correctly).
If I click on COM 3, Samba v2.10 will give me that "Old communication error".
I will seek help to get my 20b back to working (if it is possible) but as far as me using the cord to flash calculators is concerned - I'm done. It is too frustrating a process.
Quote:
So I checked the Compatibility Mode, put new batteries, connected the calculator when the cord was flashing (which was all but a millisecond it seems) - STILL THE SAME RESULT: NO CONNECTION.
The sequence of events should be:
- Start MySamba and fill in the fields.
- Connect the cable.
- Reset the calculator.
- Turn on the calculator (you will not see anything). Hold down ON for a second or so.
- Click "Send File" in MySmBa.
If MySamba errors out immediately (no noticeable delay) you have a problem between MySamba and the Windows driver of your serial port. If it takes a second or longer to error out, the problem is between the communication endpoints such as a calculator not answering the packets from the PC.
Download and install "Free Serial Port Monitor". It will show you what is going on on the serial port. I used it to debug the communication between the emulator and the device but it should equally well tell you what is going on (or not) while flashing.
Quote:
... as far as me using the cord to flash calculators is concerned - I'm done. It is too frustrating a process.
That's bad news. :-(
Quote:
The sequence of events should be:
1. Start MySamba and fill in the fields.
2. Connect the cable.
3. Reset the calculator.
4. Turn on the calculator (you will not see anything). Hold down ON for a second or so.
5. Click "Send File" in MySmBa.
If MySamba errors out immediately (no noticeable delay) you have a problem between MySamba and the Windows driver of your serial port. If it takes a second or longer to error out, the problem is between the communication endpoints such as a calculator not answering the packets from the PC.
Download and install "Free Serial Port Monitor". It will show you what is going on on the serial port. I used it to debug the communication between the emulator and the device but it should equally well tell you what is going on (or not) while flashing.
You are a miracle worker! I achieved success this morning and Version 2.2.1782 is on my 20b.
Thanks everyone for your help and your patience with me.
Eddie
You make me curious: What did you change?
Quote:
So I am back to the Samba CDC program...
I have SAMBA 2.10 with my Vista (32 bit) machine. It installed 2 versions. The one with a "_cdc" tag indeed does NOT work. The one
without the "_cdc" works fine with my FTDI USB-to-serial converter.
CDC assumes a working USB device implementation on the target. This is obviously not the case with an HP 20b or 30b.
SAM-BA is awfully slow compared to MySamba. Either Atmel has done a horrible job or Cyrille an extraordinary good one. I assume both is true. Think of 3 minutes versus 20 seconds to reflash the device. Why SAM-BA is so slow and why it is so picky with the execution mode or the serial port driver is beyond me.
Holding down the ON button before clicking on download.