Shop OBEX P1 Docs P2 Docs Learn Events
HELP -- "No Propeller chip found" killed COM after Remote Desktop flash attempt — Parallax Forums

HELP -- "No Propeller chip found" killed COM after Remote Desktop flash attempt

courtenscourtens Posts: 101
edited 2012-05-10 18:19 in Propeller 1
Yes -- I tried to "flash" my Propeller over a Remote Desktop Connection (do not try this out !!!) This is your warning -- don't try this!

Setup:
- Computer A, Propeller connected to computer A and working fine (recognized)
- Computer B: was working on B and connected to A over a Remote Desktop Connection session; I was programming using the Propeller Tool.

After my first, and unsuccessful attempt, to flash the propeller over the Remote Desktop Connection using Computer B, I went back using computer A.

Now the Propeller Chip is no longer visible! I am getting "No Propeller chip found on any serial port" and it lists the different ports it scanned.

The propeller is on a board with one other Propeller chip on it. The one that I attempted flashing will no longer connect, but the other propeller chip gets recognized just fine. So it is not the cable, the power, the connection ... but it's the chip or the memory ... but I am thinking it's the chip.

During my flash attempt I got a super long error message which I unfortunately ignored. I thought -- oh well -- just go back to Computer A to flash the thing.

I really do not want to unsolder the Propeller Chip from the board. Any ideas what could be happening, and if there is a way to fix this?

When pressing F7 the bad connecting Propeller restarts but no initiation is happening.....

Thanks!

PS: using Win 7 64-bit

Comments

  • Mike GreenMike Green Posts: 23,101
    edited 2012-05-10 17:52
    DO NOT unsolder the Propeller chip. There's no flash memory on the chip and you can't damage the Propeller trying to download to it over a remote desktop connection. When you download to a Propeller, you're first downloading to the Propeller's hub RAM via a program running from the Propeller's on-chip ROM. If you ask to download to EEPROM, the Propeller itself copies the program from RAM to the attached EEPROM, a standard I2C 32K or 64K (or even 128K) EEPROM.

    We can't give you any advice about what's going on without more information about your setup (schematic please). Most likely it's something going on with Windows.
  • courtenscourtens Posts: 101
    edited 2012-05-10 18:19
    Thanks Mike,

    That is so good to know.

    I how hooked up my scope directly to the plug -- and sure enough! Somehow it found the prop. The bad connection must have been in the plug. Strange.

    Thanks again!
Sign In or Register to comment.