Shop OBEX P1 Docs P2 Docs Learn Events
Chameleon and SimpleIDE on MacOSX — Parallax Forums

Chameleon and SimpleIDE on MacOSX

dossicdossic Posts: 38
edited 2013-12-08 22:45 in Propeller 1
Dear friends,
I have a Chameleon bord I'm very satisfied with. Until recently, I used Propeller Tool and SimpleIDE on Windows to program it (on Propeller side, obviously). Few weeks ago, I moved to a MacBook Air computer, I abandoned Propeller Tool, and I started woking on SimpleIDE on Mac. Mac and SimpleIDE recognizes the Chameleon board (after downloading and installing FTDI drivers), but Propeller-Load can't see it :

propeller-load -S5 -Dreset=dtr -r Amel2559_Firmware ver 120r1.binary -p /dev/cu.usbserial-A800edo7
error: no propeller chip on port '/dev/cu.usbserial-A800edo7'
(p.s. the port is actually that seen on Mac using ls /dev/tty.* on Terminal)
I tried setting delay to 1 thru 50, but nothing changed. When I come back to Windows, downloading is OK again.

Can you please suggest me a possible solution?

Greetings from Lake Como

carlo

Comments

  • David BetzDavid Betz Posts: 14,516
    edited 2013-12-08 11:34
    dossic wrote: »
    Dear friends,
    I have a Chameleon bord I'm very satisfied with. Until recently, I used Propeller Tool and SimpleIDE on Windows to program it (on Propeller side, obviously). Few weeks ago, I moved to a MacBook Air computer, I abandoned Propeller Tool, and I started woking on SimpleIDE on Mac. Mac and SimpleIDE recognizes the Chameleon board (after downloading and installing FTDI drivers), but Propeller-Load can't see it :

    propeller-load -S5 -Dreset=dtr -r Amel2559_Firmware ver 120r1.binary -p /dev/cu.usbserial-A800edo7
    error: no propeller chip on port '/dev/cu.usbserial-A800edo7'
    (p.s. the port is actually that seen on Mac using ls /dev/tty.* on Terminal)
    I tried setting delay to 1 thru 50, but nothing changed. When I come back to Windows, downloading is OK again.

    Can you please suggest me a possible solution?

    Greetings from Lake Como

    carlo
    propeller-load should automatically detect the port if you leave off the -p option. Also, it looks like you're using a filename with spaces in it. You'll need to put quotes around that so that propeller-load doesn't think it is several arguments.
  • dossicdossic Posts: 38
    edited 2013-12-08 13:49
    David Betz wrote: »
    propeller-load should automatically detect the port if you leave off the -p option. Also, it looks like you're using a filename with spaces in it. You'll need to put quotes around that so that propeller-load doesn't think it is several arguments.

    Hi! Thanks for the reply!
    Actually, I wasn't using propeller-load on terminal, but the message appeared on SimpleIDE when trying to compile the file (alt+F11 on Mac). I tried with a new filename without spaces, but no changes. It doesn't find any propeller on the USB port.
    I'll try again, and I'll keep you informed.
    Yours Carlo
  • jazzedjazzed Posts: 11,803
    edited 2013-12-08 14:23
    dossic wrote: »
    Hi! Thanks for the reply!
    Actually, I wasn't using propeller-load on terminal, but the message appeared on SimpleIDE when trying to compile the file (alt+F11 on Mac). I tried with a new filename without spaces, but no changes. It doesn't find any propeller on the USB port.
    I'll try again, and I'll keep you informed.
    Yours Carlo

    What kind of a board are you using Carlo?

    I suspect there is some kind of a reset problem or serial communications problem. Do you see any LED blinking during the load attempt?

    You shouldn't need to have loader-delay set at all (-S1 reflects Properties->General->Loader Delay as 1).

    --Steve
  • David BetzDavid Betz Posts: 14,516
    edited 2013-12-08 17:25
    dossic wrote: »
    Hi! Thanks for the reply!
    Actually, I wasn't using propeller-load on terminal, but the message appeared on SimpleIDE when trying to compile the file (alt+F11 on Mac). I tried with a new filename without spaces, but no changes. It doesn't find any propeller on the USB port.
    I'll try again, and I'll keep you informed.
    Yours Carlo
    Are you sure you have the programming jumper set to select the Propeller rather than the AVR/PIC? Which Chameleon do you have? I have both the AVR and the PIC board so I can try to duplicate your problem. I don''t think we've ever tried any of our tools on the Chameleons but I don't see why they wouldn't work together.
  • dossicdossic Posts: 38
    edited 2013-12-08 22:45
    David Betz wrote: »
    Are you sure you have the programming jumper set to select the Propeller rather than the AVR/PIC? Which Chameleon do you have? I have both the AVR and the PIC board so I can try to duplicate your problem. I don''t think we've ever tried any of our tools on the Chameleons but I don't see why they wouldn't work together.
    Hi David!
    My board is the Chameleon AVR, sorry for forgetting to specify it in my previous post.
    Then I did a bunch of experiment, I'm summarizing here.
    1.Switch was always selected to allow USB to talk to the Propeller.
    2. My Chameleon-AVR board is working properly with SimpleIDE in Windows (emulated in VirtualBox).! Tried again with SimpleIDE on Mac, no luck, Propeller chip wasn't found.
    3. Then I connected my old demo board to SimpleIDE on Mac;everything worked fine.

    So, apparently my Chameleon doesn't like the Mac!!! Thanks for helping me to find a solution.
    Carlo
Sign In or Register to comment.