Ok, maybe this is a stupid question and I shouldn't probably ask it but ... to talk to the board you must have it booted with the TAQOZ either from the SD card or from the P2 ROM. Do you have the SD card installed in your P2D2 board ?
If you do not have the card inserted and preloaded with the TAQOZ then your only option at the moment is to hit > then a space bar then an Esc key and the board will boot with the TAQOZ in ROM. You also need to change the baud rate to 115200 as that is the default for the TAQOZ in ROM.
I very much love systems I can not understand fully. This is not true for computers. That's what I like with the Propeller. It's clean and simple and I can manage to understand everything I do. As I limit my efforts to a small area. A self contained system is not far away. But I hate systems that force me to do things I have no chance to follow up. So now I gave it another try with a different W10 PC and the CP1201 was recognized, but no COM-Port assigned. As I removed and reconnected the P2D2 COM3 was established. And then I came to the same point: I could not open a connection using Teraterm. ... I know, once I overcome this hurdle, I will be stuck in joy with Tachyon. ;-) But that's what I love.
Now I restarted the W10 PC and when it booted is hang until I removed the P2D2. Then the port COM5 was assigned after reconnect. The manager finds the port and tells everything's fine and working. When I open teraterm the message is "can not open COM5; Not found" Putty also not working. I now why I still morn for CP/M
I thought it was just me but yeah, I occasionally need to jump through a couple of hoops to establish a connection with the USB/UART cable on both W10 and even my rock-solid XP system.
If you were using RS232, I would suggest flipping RX/TX but I don't know if this could ever be an issue with these cables(?)
I just raised this question too: 3.298V I measured at to Pins of P2D2. Also I had a very short USB cable to limit voltage drop but another one showed the same result. Tried to install another driver and a setup program from Silab without success.
SiLabs 21xx Customization Utility doesn't find the device even when present in the device manager ;-) Now I see another behavior: An earlier try showed COM7 in the device manager, the USB-Uart bridge is enumerated, but not this one. While Teraterm offers COM7 to selection and then doesn't find the port.
Hope that tip helps. The CPxxxx seems to work for a lot of people without going through hoops. I'm still awaiting my ~30 pieces from Peter to help out.
I very much love systems I can not understand fully. This is not true for computers. That's what I like with the Propeller. It's clean and simple and I can manage to understand everything I do. As I limit my efforts to a small area. A self contained system is not far away. But I hate systems that force me to do things I have no chance to follow up. So now I gave it another try with a different W10 PC and the CP1201 was recognized, but no COM-Port assigned. As I removed and reconnected the P2D2 COM3 was established. And then I came to the same point: I could not open a connection using Teraterm. ... I know, once I overcome this hurdle, I will be stuck in joy with Tachyon. ;-) But that's what I love.
Since you have W10, to prove a few things, run PST (Parallax Serial Terminal). You may need to select the COM port number. It's really simple and dumb so there's not much to go wrong. It will help prove if you can communicate with the P2.
I ran some tests with this on a Win10 system and it already knows about it as VID=10C4 & PID=EA60 which is what PnP uses, not the description. It also worked fine in TeraTerm. So I tried on another Win10 system that has never had a USB serial before and the device manager could see it, but W10 wouldn't do anything about "finding" the driver. In previous Windows systems it would just work etc. Now I ask it to find the driver and it "can't". This is a real backward step for Windows Plug'n'Pray.
So I went to Silabs and downloaded "CP210x Universal Windows Driver" and installed that manually. So much for Windows. Anyway after replugging the P2D2 it was recognized as a COM port, so I also installed TeraTerm and was able to communicate with the P2D2.
Linux systems btw just seems to work with practically anything and without any fuss or "bing bong" as I say (which is what Windows does when it is being "helpful" .... bing bong....Windows is searching for a driver....sometime later ...bing bong..... Your device is now ready......). Linux doesn't bing bong, it just works instantly.
dmesg output from Linux when I plug in the P2D2
[89289.509951] usb 1-2: new full-speed USB device number 16 using xhci_hcd
[89289.663604] usb 1-2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 2.56
[89289.663610] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[89289.663613] usb 1-2: Product: EFM8UB3 uPORT SERIAL WATCHDOG UB3_2.5.8C
[89289.663616] usb 1-2: Manufacturer: Silicon Labs
[89289.663619] usb 1-2: SerialNumber: 0005
[89289.665245] cp210x 1-2:1.0: cp210x converter detected
[89289.666143] usb 1-2: cp210x converter now attached to ttyUSB0
These are the relevant areas in the UB3 chip that the user can change if need be via I2C. Notice the 10C4 and EA60 at address 8012 (big endian)
@"Peter Jakacki" said:
I ran some tests with this on a Win10 system and it already knows about it as VID=10C4 & PID=EA60 which is what PnP uses, not the description. It also worked fine in TeraTerm. So I tried on another Win10 system that has never had a USB serial before and the device manager could see it, but W10 wouldn't do anything about "finding" the driver. In previous Windows systems it would just work etc. Now I ask it to find the driver and it "can't". This is a real backward step for Windows Plug'n'Pray.
So I went to Silabs and downloaded "CP210x Universal Windows Driver" and installed that manually. So much for Windows. Anyway after replugging the P2D2 it was recognized as a COM port, so I also installed TeraTerm and was able to communicate with the P2D2.
Following up on this, I see Silabs have a new 2021 driver (CP210x Universal Windows Driver v10.1.10 1/14/2021),
so I just downloaded the 2021 Silabs driver 10.1.10.103, and even tho the release notes say this MCUSW-651 | Support baud rate up to 2187500 for CP2102, CP2104, CP2109
it now allows me to enter any value up to 12Mbd for UB3 & connects fine (UB3 is COM38 here), without coughing any (bogus in my mind) SW error for values above 1MBd, so they have fixed that user SW value issue
( I asked them to allow VCP aka UB3 users to be allowed to enter any baud rate, to give users the full control they could expect. The peripheral HW then determines what is possible, not some PC code.
On UB3 you can actually ask for 24MBd and it will try to TX that, tho note it has no chance of RX at 24MBd. Practical Baud two way limits for UB3 look to be ..4.8M.N.8.1, 6M.N.8.2 and 8M.N.8.2 (ie use 2 stop bits at the very top baud rates)
It’s not possible to actually buy one of these is it? I seem to recall ordering mine because it was supposed to be the first P2 board available. Now Parallax has at least two and others are offering them as well. I suppose mine will eventually arrive some day......
I managed to receive a few here in Europe. Some work was done, but still there is no breakthrough in production. Maybe Peter will one day able to explain the pitfalls, for now I just hope, we all are fine and stay healthy ;-)
Hi, currently I have some first prototypes here, but I'm not ready to distribute something already. We still lack finishing of the first prototype series, for some reason Peter is not able to finish, maybe he's sidetracked filling the fridge ;-) For him it's nothing to earn money now. I hope to receive some more board in the next future, and believe, there has to be a second source (or is it the first ?)
Sorry not to have another Easter surprise.
So quiet here ....
Have people lost their faith or just silently saving up for the goodies when they surface ? Because they eventually will .... some day.
Comments
Ok, maybe this is a stupid question and I shouldn't probably ask it but ... to talk to the board you must have it booted with the TAQOZ either from the SD card or from the P2 ROM. Do you have the SD card installed in your P2D2 board ?
If you do not have the card inserted and preloaded with the TAQOZ then your only option at the moment is to hit > then a space bar then an Esc key and the board will boot with the TAQOZ in ROM. You also need to change the baud rate to 115200 as that is the default for the TAQOZ in ROM.
I very much love systems I can not understand fully. This is not true for computers. That's what I like with the Propeller. It's clean and simple and I can manage to understand everything I do. As I limit my efforts to a small area. A self contained system is not far away. But I hate systems that force me to do things I have no chance to follow up. So now I gave it another try with a different W10 PC and the CP1201 was recognized, but no COM-Port assigned. As I removed and reconnected the P2D2 COM3 was established. And then I came to the same point: I could not open a connection using Teraterm. ... I know, once I overcome this hurdle, I will be stuck in joy with Tachyon. ;-) But that's what I love.
Now I restarted the W10 PC and when it booted is hang until I removed the P2D2. Then the port COM5 was assigned after reconnect. The manager finds the port and tells everything's fine and working. When I open teraterm the message is "can not open COM5; Not found" Putty also not working. I now why I still morn for CP/M
@ErNa
I thought it was just me but yeah, I occasionally need to jump through a couple of hoops to establish a connection with the USB/UART cable on both W10 and even my rock-solid XP system.
If you were using RS232, I would suggest flipping RX/TX but I don't know if this could ever be an issue with these cables(?)
Silly question but there is definitely power to the P2 board, right?
I just raised this question too: 3.298V I measured at to Pins of P2D2. Also I had a very short USB cable to limit voltage drop but another one showed the same result. Tried to install another driver and a setup program from Silab without success.
SiLabs 21xx Customization Utility doesn't find the device even when present in the device manager ;-) Now I see another behavior: An earlier try showed COM7 in the device manager, the USB-Uart bridge is enumerated, but not this one. While Teraterm offers COM7 to selection and then doesn't find the port.
Ah, can't even open.
Apparently, Windows can assign ports that are already in use. There is a way to manually reassign it to something else but I don't remember how.
In DM, did you try right clicking it, disabling and re-enabling it?
Maybe the Silabs utility will let you reassign. Seems that my virtual com ports are always enumerated with a double digit number
Aha!
https://www.silabs.com/community/interface/knowledge-base.entry.html/2010/09/24/reassign_com_portnu-bZRl
Hope that tip helps. The CPxxxx seems to work for a lot of people without going through hoops. I'm still awaiting my ~30 pieces from Peter to help out.
Since you have W10, to prove a few things, run PST (Parallax Serial Terminal). You may need to select the COM port number. It's really simple and dumb so there's not much to go wrong. It will help prove if you can communicate with the P2.
I ran some tests with this on a Win10 system and it already knows about it as VID=10C4 & PID=EA60 which is what PnP uses, not the description. It also worked fine in TeraTerm. So I tried on another Win10 system that has never had a USB serial before and the device manager could see it, but W10 wouldn't do anything about "finding" the driver. In previous Windows systems it would just work etc. Now I ask it to find the driver and it "can't". This is a real backward step for Windows Plug'n'Pray.
So I went to Silabs and downloaded "CP210x Universal Windows Driver" and installed that manually. So much for Windows. Anyway after replugging the P2D2 it was recognized as a COM port, so I also installed TeraTerm and was able to communicate with the P2D2.
Linux systems btw just seems to work with practically anything and without any fuss or "bing bong" as I say (which is what Windows does when it is being "helpful" .... bing bong....Windows is searching for a driver....sometime later ...bing bong..... Your device is now ready......). Linux doesn't bing bong, it just works instantly.
dmesg output from Linux when I plug in the P2D2
These are the relevant areas in the UB3 chip that the user can change if need be via I2C. Notice the 10C4 and EA60 at address 8012 (big endian)
Are we going to see physical P2D2s in 2021?
It's real, belive me. And it's great.
That would be incredibly cool.
Following up on this, I see Silabs have a new 2021 driver (CP210x Universal Windows Driver v10.1.10 1/14/2021),
so I just downloaded the 2021 Silabs driver 10.1.10.103, and even tho the release notes say this MCUSW-651 | Support baud rate up to 2187500 for CP2102, CP2104, CP2109
it now allows me to enter any value up to 12Mbd for UB3 & connects fine (UB3 is COM38 here), without coughing any (bogus in my mind) SW error for values above 1MBd, so they have fixed that user SW value issue
( I asked them to allow VCP aka UB3 users to be allowed to enter any baud rate, to give users the full control they could expect. The peripheral HW then determines what is possible, not some PC code.
On UB3 you can actually ask for 24MBd and it will try to TX that, tho note it has no chance of RX at 24MBd. Practical Baud two way limits for UB3 look to be ..4.8M.N.8.1, 6M.N.8.2 and 8M.N.8.2 (ie use 2 stop bits at the very top baud rates)
How much would 3 or 4 P2D2s cost for some friends here in the UK? Any idea of delivery time?
I'm interested in buying a P2D2 as well - Bob Edwards SW U.K.
It’s not possible to actually buy one of these is it? I seem to recall ordering mine because it was supposed to be the first P2 board available. Now Parallax has at least two and others are offering them as well. I suppose mine will eventually arrive some day......
Right now P2D2 is like the fabled Snow Leopard. A thing of beauty but scarce and difficult to locate in the wild. Hopefully it's not endangered.
Did they ever make it to the USA? I think I paid for one.
I managed to receive a few here in Europe. Some work was done, but still there is no breakthrough in production. Maybe Peter will one day able to explain the pitfalls, for now I just hope, we all are fine and stay healthy ;-)
Yeah, this is my world; 99% is just a matter of doing it but the last 1% kicks my butt 😁
@"Peter Jakacki" / @ErNa
I'am sorry, I am pretty busy in the latest couple of month thus I can't follow the forum as I would like.
Any news? Has the P2D2 come to Europe?
Yes we are eagerly waiting.
Hi, currently I have some first prototypes here, but I'm not ready to distribute something already. We still lack finishing of the first prototype series, for some reason Peter is not able to finish, maybe he's sidetracked filling the fridge ;-) For him it's nothing to earn money now. I hope to receive some more board in the next future, and believe, there has to be a second source (or is it the first ?)
Sorry not to have another Easter surprise.
So quiet here ....
Have people lost their faith or just silently saving up for the goodies when they surface ? Because they eventually will .... some day.
As for me, I'm a believer.
It would be nice to have an update.
Yes it would. Paging Peter!
There is a light...