DryOS, continued.As written previously, the "event shell" communicates directly with the UART driver. However, the various event procedures seem to use stdin/stdout. I have verified this by starting "drysh" via a script: I was able to talk to it and get its output.
Next step: remote console over PTP.
Quote from: srsa_4c on 20 / December / 2013, 12:29:28DryOS, continued.As written previously, the "event shell" communicates directly with the UART driver. However, the various event procedures seem to use stdin/stdout. I have verified this by starting "drysh" via a script: I was able to talk to it and get its output.I would be interested to see code for this, even if it's very rough.
Quote Next step: remote console over PTP.One approach would be to make lua functions that let you read from / write to the console.
I would be interested to see code for this, even if it's very rough.
One approach would be to make lua functions that let you read from / write to the console.
=== Dry-shell start ===Dry> ?[Debug] task sem event mq mutex cond timer mkobjsize extask kill suspend resume release delete prio mkcfg meminfo xd xm memmap objinfo [Misc] vers exit dminfo [Network] arp mbufs ping route ifconfig netstat pngl netrace [TMN] tm rt wps ibss [WiFi] wprd wtst
elph130 hasCode: [Select][Network] arp mbufs ping route ifconfig netstat pngl netrace [TMN] tm rt wps ibss [WiFi] wprd wtst The last 3 sections are interesting
[Network] arp mbufs ping route ifconfig netstat pngl netrace [TMN] tm rt wps ibss [WiFi] wprd wtst
One complication is that some of the eventprocs I want to call are interactive (prompt for some value, wait for input, prompt, etc), so would probably need to be called from a different task than the one that was feeding it input and reading output.
I have found something that's worrying:D10 NAME ID STATE PRI WAIT(ID) STACK % SP PTPSession 01fd0044 WAIT 25 RCVMQ(01fa004c) 0fa8/1000 97 002fe240 A470 NAME ID STATE PRI WAIT(ID) STACK % SPPTPSession 01c60041 WAIT 25 RCVMQ(01c30041) 0e74/1000 90 0028b908Looks like a high chance for stack overflow...
camcon [eventproc]
$ chdkptp -c -iconnected: Canon PowerShot ELPH 130 IS, max packet size 512con> =call_event_proc_task('drysh')con 1> =return cam_con_gets()2:return:'=== Dry-shell start ===Dry> 'con 2> =return cam_con_puts('?\n')3:return:2con 3> =return cam_con_gets()4:return:'?[Debug] task sem event mq mutex cond timer mkobjsize extask kill suspend resume release delete prio mkcfg meminfo xd xm memmap objinfo[Misc] vers exit dminfo[Network] arp mbufs ping route ifconfig netstat pngl netrace[TMN] tm rt wps ibss[WiFi] wprd wtstDry> 'con 4> =return cam_con_puts('exit\n')5:return:5con 5> =return cam_con_gets()6:return:'exitlogout==== Dry-shell end ===='con 6> =return get_task_result()7:return:0
Started by ..::T3::.. Creative Uses of CHDK
Started by alvm General Discussion and Assistance
Started by dclaar General Discussion and Assistance
Started by bootstrap DryOS Development