sudo cp ./dl /usr/local/bin
sudo chmod 755 /usr/local/bin/dl
bkw@miata:~$ ls /dev/ttyUSB*
/dev/ttyUSB0
bkw@miata:~$ cd ~/Documents/TRS-80/Model_200/files
bkw@miata:~/Documents/TRS-80/Model_200/files$ ls
DCPREP.DO RUN-CO.DO SERIAL.DO START.DO
bkw@miata:~/Documents/TRS-80/Model_200/files$
1
On 27 November 2017 at 19:57, Daryl Tester
wrote:
> On Mon, 27 Nov 2017 19:53:47 -0800, Peter Vollan wrote:
>
>> ./dl /dev/ttyUSB0 puts me right back at the command prompt. And I can
>> see ttyUSB0 in the /dev directory. Did I miscompile desklink?
>
>
>
Maybe try it with sudo to see if it’s a permissions problem.
Also type dmesg to see if there are any kernel errors after it exits.
Another possibility would be compile for debug and run it under gdb to see
if it hits an exception. Or step through to see where it fails.
— John.
On Mon, Nov 27,
On Mon, 27 Nov 2017 19:53:47 -0800, Peter Vollan wrote:
./dl /dev/ttyUSB0 puts me right back at the command prompt. And I can
see ttyUSB0 in the /dev directory. Did I miscompile desklink?
What does running "echo $?" immediately after the command return?
--
Regards,
Daryl Tester
./dl /dev/ttyUSB0 puts me right back at the command prompt. And I can
see ttyUSB0 in the /dev directory. Did I miscompile desklink?
On 27 November 2017 at 15:37, John R. Hogerhuis wrote:
> When you plug in your usb serial device you can type
>
> dmesg
>
> And it will print out
hey, josh,
let me know if you want startup capital, I'm happy to help there. I know of at
least 2 other people on list who would probably add to the startup fund.
ray
From: M100 on behalf of Josh Malone
When you plug in your usb serial device you can type
dmesg
And it will print out recent kernel messages. You can usually tell what
/dev/ttyUSBx device just got added from the scrawl.
— John.
On Mon, Nov 27, 2017 at 3:34 PM Peter Vollan wrote:
> I am not certain which
I am not certain which USB port I am on. But on the other hand,
desklink gives the say result whatever port I enter, or if I enter
none at all.
On 27 November 2017 at 15:17, John R. Hogerhuis wrote:
> Shouldn’t do that. It should run and stay running unless you hit ctrl-c
>
>
Shouldn’t do that. It should run and stay running unless you hit ctrl-c
Guessing there’s a hardware problem with the port, or a software /
permissions issue.
You could also try LaddieAlpha.
— John.
On Mon, Nov 27, 2017 at 3:14 PM Peter Vollan wrote:
> When I run "./dl"
When I run "./dl" followed by the usb port of my usb adaptor, I just
get the command line again. Shouldn't dlplus do something else, like
it does in DOS? Dlplus seemed to compile fine in the first place.
I realise that another possible wrinkle is that my cable(s) is not
working. I am using a
Can-do. Thank you.
--
bkw
On Nov 27, 2017 7:14 AM, "Josh Malone" wrote:
> I'd start with cold start, hit enter, type beep, enter, and see if the CPU
> and os is running. Assuming that they aren't, check the reset line with a
> scope to make sure the CPU is being reset
I'd start with cold start, hit enter, type beep, enter, and see if the CPU
and os is running. Assuming that they aren't, check the reset line with a
scope to make sure the CPU is being reset properly on power up and that
it's not held low (I think it's active low) since the nimh is in play on
this
12 matches
Mail list logo