Jack, Thanks. For reference, the way to enter the command in the KATCP directly (at least in my version) is:
?tap-start Riometer0 one_GbE 192.168.6.29 4321 02:02:00:00:00:00 Where Riometer0 - name of the device one_GbE - Simulink name of the yellow block 192.168.6.29 - IP Address 4321 - Fabric Port address 02:02:00:00:00:00 - MAC address (built into the yellow block). I still do not get pings to this device (or anything useful), but I am getting this message in the KATCP window: #log info 964232438571 raw detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232438.574052s #log info 964232439151 raw detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232439.154737s #log info 964232439732 raw detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232439.735326s #log info 964232440313 raw detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232440.315948s -Joe Kujawski On Wed, Mar 12, 2014 at 3:10 PM, Jack Hickish <[email protected]> wrote: > I think you need an extra argument which didn't used to exist (missing > it is causing the MAC address to be interpreted as a register name). > From the python tap_start (in python it really does have an > underscore) documentation: > > r.tap_start(self, tap_dev, device, mac, ip, port) > > Program a 10GbE device and start the TAP driver. > > @param self This object. > @param device String: name of the device (as in simulink name). > @param tap_dev String: name of the tap device (a Linux identifier). > If you want to destroy a device later, you need to use this name. > @param mac integer: MAC address, 48 bits. > @param ip integer: IP address, 32 bits. > @param port integer: port of fabric interface (16 bits). > > Please note that the function definition changed from corr-0.4.0 to > corr-0.4.1 to include the tap_dev identifier. > > On 12 March 2014 19:05, Kujawski, Joseph <[email protected]> wrote: > > Jack, > > > > Thanks, I found the command, however, when executed, this is the result: > > > > ?tap-start Riometer0 02:02:00:00:00:00 192.168.6.29 4321 > > > > #log error 964230869860 raw > > no\_register\_of\_name\_02:02:00:00:00:00\_available > > #log error 964230869860 raw unable\_to\_initialise\_tap\_module > > !tap-start invalid > > > > > > > > > > On Wed, Mar 12, 2014 at 2:59 PM, Jack Hickish <[email protected]> > wrote: > >> > >> admittedly it was tap-start, rather than tap_start as I said, so I > >> might have caused grep to fail you :) > >> > >> On 12 March 2014 18:58, Jack Hickish <[email protected]> wrote: > >> > On 12 March 2014 18:44, Kujawski, Joseph <[email protected]> wrote: > >> >> Jack, > >> >> > >> >> tap_start is not a command on the embedded version of KATCP for the > >> >> ROACH2: > >> >> > >> >> #version test-584-g9ebe0bd-dirty > >> >> #build-state 2012-06-26T09:26:06 > >> >> #version-connect katcp-library test-584-g9ebe0bd-dirty > >> >> 2012-06-26T09:26:06 > >> >> #version-connect katcp-protocol 4.9-M > >> >> #version-connect kernel 3.4.0-rc3+ > >> >> #14\_Tue\_May\_29\_17:05:02\_SAST\_2012 > >> >> ?help > >> >> #help client-list displays\_client\_list\_(?client-list) > >> >> #help system-info report\_server\_information\_(?system-info) > >> >> #help version > >> >> > >> >> > version\_operations\_(?sensor\_[add\_module\_version\_[mode]|remove\_module]) > >> >> #help sensor > >> >> sensor\_operations\_(?sensor\_[list|create|relay\_job-name]) > >> >> #help process > >> >> > >> >> > register\_a\_process\_command\_(?process\_executable\_help-string\_[mode] > >> >> #help arb arbitrary\_callback\_manipulation\_(?arb\_[list] > >> >> #help define runtime\_definitions\_(?define\_[mode\_name] > >> >> #help job > >> >> > >> >> > job\_operations\_(?job\_[list|process\_notice-name\_exec://executable-file|network\_notice-name\_katcp://net-host:remote-port|watchdog\_job-name|match\_job-name\_inform-message|stop\_job-name]) > >> >> #help notice notice\_operations\_(?notice\_[list|watch|wake]) > >> >> #help dispatch dispatch\_operations\_(?dispatch\_[list]) > >> >> #help chassis-led set\_a\_chassis\_led > >> >> #help chassis-start initialise\_chassis\_interface > >> >> #help tap-info > >> >> > >> >> > displays\_diagnostics\_for\_a\_tap\_instance\_(?tap-info\_register-name) > >> >> #help tap-stop deletes\_a\_tap\_instance\_(?tap-stop\_register-name) > >> >> #help tap-start > >> > > >> > There it is :) > >> > > >> > Not sure why the alphabetization is so weird. > >> > > >> > > >> >> > >> >> > start\_a\_tap\_instance\_(?tap-start\_(?tap-start\_tap-device\_register-name\_ip-address\_[port\_[mac]]) > >> >> #help delbof deletes\_a\_gateware\_image\_(?delbof\_image-file) > >> >> #help listbof display\_available\_bof\_files\_(?listbof) > >> >> #help listdev lists\_available\_registers\_(?listdev\_[size|detail] > >> >> #help fpgastatus > display\_if\_the\_fpga\_is\_programmed\_(?fpgastatus) > >> >> #help progdev program\_the\_fpga\_(?progdev\_[filename]) > >> >> #help wordread > >> >> > >> >> > read\_data\_from\_a\_named\_register\_(?wordread\_name\_word-offset:bit-offset\_word-count) > >> >> #help wordwrite > >> >> > write\_data\_to\_a\_named\_register\_(?wordwrite\_name\_index\_value+) > >> >> #help read > >> >> > >> >> > read\_data\_from\_a\_named\_register\_(?read\_name\_byte-offset:bit-offset\_byte-length:bit-length) > >> >> #help write > >> >> > >> >> > write\_data\_to\_a\_named\_register\_(?write\_name\_byte-offset:bit-offset\_value\_byte-length:bit-length) > >> >> #help register > >> >> > >> >> > name\_a\_memory\_location\_(?register\_name\_position\_bit-offset\_length) > >> >> #help upload > >> >> upload\_a\_compressed\_bitstream\_to\_device\_(?upload\_port) > >> >> #help mode mode\_change\_command\_(?mode\_[new-mode]) > >> >> #help version-list list\_versions\_(?version-list) > >> >> #help sensor-limit > >> >> adjust\_sensor\_limits\_(?sensor-limit\_[sensor]\_[min|max]\_value) > >> >> #help sensor-value query\_a\_sensor\_(?sensor-value\_sensor) > >> >> #help sensor-sampling > >> >> > configure\_sensor\_(?sensor-sampling\_sensor\_[strategy\_[parameter]]) > >> >> #help sensor-list lists\_available\_sensors\_(?sensor-list\_[sensor]) > >> >> #help watchdog pings\_the\_system\_(?watchdog) > >> >> #help log-record > >> >> generate\_a\_log\_entry\_(?log-record\_[priority]\_message) > >> >> #help log-default > >> >> > >> >> > sets\_the\_minimum\_reported\_log\_priority\_for\_all\_new\_connections\_(?log-default\_[priority]) > >> >> #help log-level > >> >> sets\_the\_minimum\_reported\_log\_priority\_(?log-level\_[priority]) > >> >> #help help displays\_this\_help\_(?help\_[command]) > >> >> #help restart restarts\_the\_system\_(?restart) > >> >> #help halt shuts\_the\_system\_down\_(?halt) > >> >> #help search search\_[tag1\_tag2\_...] > >> >> #help set set\_[key]\_[value\_value\_...]\_to\_database > >> >> #help get get\_[key]\_(n)\_from\_database\_(n\_optional) > >> >> #help dict dict\_[key]\_{key0:value0,key1:value1,...} > >> >> !help ok 43 > >> >> > >> >> Any suggestions? > >> >> > >> >> -Joe Kujawski > >> >> > >> >> > >> >> On Tue, Mar 11, 2014 at 6:10 PM, Jack Hickish <[email protected] > > > >> >> wrote: > >> >>> > >> >>> Hi Joe, > >> >>> > >> >>> That's the port you want. There is a "one_GbE" yellow block to > control > >> >>> it, > >> >>> which you can set up with the tap_start katcp command just like the > >> >>> ten gig > >> >>> interface. > >> >>> > >> >>> Cheers, > >> >>> Jack > >> >>> > >> >>> On 11 Mar 2014 21:00, "Kujawski, Joseph" <[email protected]> > wrote: > >> >>>> > >> >>>> There is an Ethernet port on the ROACH-2 labeled 'V6 NET'. Is this > >> >>>> connected to the Xilinx FPGA? If so, what 'yellow block' is used > to > >> >>>> access > >> >>>> its functionality? > >> >>>> > >> >>>> Thanks, > >> >>>> > >> >>>> -Joe Kujawski > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> ************************************** > >> >> * Joe Kujawski > >> >> * Siena College > >> >> * Dept. of Physics and Astronomy, RB 113 > >> >> * 515 Loudon Road > >> >> * Loudonville, NY 12211-1462 > >> >> * > >> >> * Email: [email protected] > >> >> * Phone: 518-782-6885 > >> >> * Fax: 518-783-2986 > >> >> ************************************** > >> >> > > > > > > > > > > -- > > ************************************** > > * Joe Kujawski > > * Siena College > > * Dept. of Physics and Astronomy, RB 113 > > * 515 Loudon Road > > * Loudonville, NY 12211-1462 > > * > > * Email: [email protected] > > * Phone: 518-782-6885 > > * Fax: 518-783-2986 > > ************************************** > > > -- ************************************** * Joe Kujawski * Siena College * Dept. of Physics and Astronomy, RB 113 * 515 Loudon Road * Loudonville, NY 12211-1462 * * Email: [email protected] * Phone: 518-782-6885 * Fax: 518-783-2986 **************************************
