19040625 3114325 3114325 3145737 19073322 19161419 19161420 19161421 3 2012-08-16 17:18:45.410 2012-08-16 17:20:07.877 19040627 19040628 3637515 3114109 3114325 3114109 3145737 3670270 3706655 3706656 3706657 3706658 3706659 3604569 3604572 3604582 3604592 2 2008-04-22 09:58:11.307 2008-04-22 10:01:55.163 3637517 3735580 19040811 3114325 3114325 3145737 19073506 19163824 19163825 19163826 19163827 19163828 19163829 19163830 19163831 19163832 19163833 19163834 19163835 19163836 19163837 19163838 19163839 3 2012-09-10 15:59:38.217 2012-09-10 16:03:37.250 19040814 19040815 3114231 3114109 3114325 3114109 3145737 3179709 4554779 4554780 4554781 3277102 3277103 3277113 3277149 3277162 4620289 14 2008-03-23 11:17:30.410 2008-05-29 09:54:04.047 3114232 3114234 3114371 3114439 3114464 3114467 3114469 3637352 3637374 3637376 3637377 3637378 4456456 3309656 19040813 3114325 3114325 3145737 19073507 19163801 19163802 19163803 19163804 19163805 19163806 19163807 1 2012-09-10 16:01:22.577 2012-09-10 16:01:22.577 3145737 3114324 3114325 3211464 3211465 3211466 3211467 3211468 3211469 3211470 3211471 3211472 3211473 3211474 3211475 3211476 3211477 3211480 3211481 3211482 3211483 3211484 3211485 3211486 3211487 3211488 3211489 3211490 3211491 3211492 3211493 3211494 3211495 3211496 3211497 3211499 3211500 3211501 3211502 3211503 3211504 3211505 3211506 3211507 3211508 3211509 3211510 3211511 3211512 3211513 3211514 3211515 3211516 3211517 3211518 3211519 3211520 3211521 3211522 4882447 4882448 4882449 4882450 4882451 12615738 12615739 19300573 2008-03-24 11:31:02.913 2008-03-24 11:31:02.913 global 10356102 3114325 3114325 3145737 10388828 10459153 10459154 3 2009-09-02 14:39:38.767 2009-09-02 15:34:00.337 10356103 10356105 6259287 3114325 3114325 3145737 6226496 2 2008-10-03 16:14:13.217 2008-10-09 10:34:37.377 6259324 3637523 3114109 3114325 3114109 3145737 3670278 4555242 4555243 4555244 3604575 3604576 4096001 4620303 4849772 5 2008-04-22 10:16:03.100 2008-06-02 09:18:20.817 3932163 3932164 4456516 4456522 4063233 19040630 3114325 3114325 3145737 19073327 19534260 19534261 19534262 25 2012-08-16 17:27:30.563 2013-01-11 16:36:14.957 19040632 19040637 19040638 19040640 19040642 19040644 19040645 19040646 19040648 19040650 19040652 19040654 19040656 19040658 19040660 19040661 19040663 19040664 19040809 19041619 19041620 19041621 19041623 19041624 19040827 3114325 3114325 3145737 19073520 19163858 19163859 19163860 19163861 19163862 19163863 6 2012-09-11 17:54:13.537 2012-09-11 19:02:42.743 19040828 19040831 19040833 19040835 19040837 3114238 3114109 3114325 3114109 3114452 3145737 3179715 3704636 3277105 3277106 3277166 3277167 3277170 3277172 3277173 7 2008-03-23 11:20:18.790 2008-04-18 15:59:13.450 3114239 3114240 3114373 3637397 3637398 3637400 3309657 9372007 3114325 3114325 3145737 9404755 3 2009-03-03 12:53:06.193 2009-03-03 15:07:36.693 9372008 9372012 9502761 9502762 9502763 9502764 9502765 9502766 9502758 9502768 9502769 9502759 9502760 9502767 3114242 3114109 3114325 3114109 3145737 3179718 3704653 3704654 3277109 3277110 3277112 3277115 3277150 3604535 15 2008-03-23 11:21:57.880 2008-04-18 16:11:29.110 3114244 3114256 3114257 3114258 3114259 3114260 3114261 3114262 3114263 3114264 3114375 3637412 3637414 3637415 3309658 3309659 3637488 3114109 3114325 3114109 3145737 3670243 4030477 4030478 4030479 4030480 4030481 4030482 4030483 4030484 4030485 3604554 3604555 3604557 3604642 4096002 4849771 4849773 9 2008-04-22 09:00:30.627 2008-05-21 13:08:56.747 3637490 3637491 3637492 3637494 3637495 3637501 3637886 3932168 3735572 3735573 3735574 3637497 3114109 3114325 3114109 3145737 3670252 4555231 4555232 4555233 4555234 4555235 3604558 3604559 3604570 4620292 4849774 4 2008-04-22 09:19:34.593 2008-05-31 15:36:40.810 3637499 3932166 4456518 3735575 3735576 3637503 3114109 3114325 3114109 3145737 3670258 5013697 5013698 3604562 4620293 4849768 4849769 2 2008-04-22 09:24:39.360 2008-06-06 06:48:58.123 4915265 3735577 3637505 3114109 3114325 3114109 3145737 3670260 4555236 4555237 4555238 4555239 4555240 4555241 3604564 3604566 3604673 5 2008-04-22 09:42:57.407 2008-05-31 15:53:20.920 3637508 3637509 3932169 4456520 3735578 18252651 3114325 3114325 3145737 18285398 19160634 19160635 19160636 23 2011-12-09 15:58:37.633 2012-08-09 13:16:14.513 18252652 18252653 18252657 18252659 18252660 18252661 18252663 18252664 18579470 18579472 19040363 19040365 19040367 19040369 19040371 19040375 19040377 19040380 19040506 19040507 19040509 19040510 3637511 3114109 3114325 3114109 3145737 3670266 4555245 4555246 4555247 4555248 4555249 4555250 3604567 3604573 3604656 2 2008-04-22 09:55:17.747 2008-06-02 09:28:15.937 4456524 3735579 3637328 3114109 3114325 3114109 3145737 3670090 4030490 4030491 3604507 3604509 3604510 4849706 7 2008-04-15 10:13:33.937 2008-05-22 11:17:22.170 3637330 3637416 3637418 3637420 3932161 3932180 9371938 3114325 3114325 3145737 9404687 11863203 11863204 11863205 11863206 11863207 11863208 11863209 11863210 11863211 31 2009-02-26 13:59:15.167 2010-04-14 09:36:40.210 9371942 9371944 9371946 9371948 9371949 9371950 9371952 9371954 9371955 9372041 9372243 9372245 9372247 9372248 9372250 9372253 9372255 9372260 9372269 9797671 9797672 9797729 9797770 9797771 9797772 9798282 9798285 9798287 9798307 11796739 3638124 3114109 3114325 3114109 3145737 3670864 3708686 3604701 3604702 1 2008-05-19 16:51:44.433 2008-05-19 16:51:44.433 3735623 3637883 3114109 3114325 3114109 3145737 3670634 3707948 3707949 3707950 3604652 3604653 3604655 4849718 11 2008-05-07 13:24:08.253 2008-05-07 13:44:44.360 3637884 3637885 3637888 3637889 3637891 3637892 3637893 3637894 3637895 3637897 3735592 3735593 3637905 3114109 3114325 3114109 3145737 3670655 3708050 3708051 3708052 3604659 3604660 3604661 3 2008-05-07 14:29:02.983 2008-05-07 14:34:38.777 3637907 3637910 3735596 3114325 3114109 3114389 3114446 4915268 5275678 5374755 6259287 6259322 6259359 6259368 7766069 9371909 9371938 9372007 10354905 10356102 18252384 18252651 19040558 19040591 19040598 19040608 19040612 19040617 19040625 19040630 19040811 19040813 19040827 19041133 19041144 19041215 3145737 3179799 16515652 16515653 16515654 16515655 16515656 16515657 16515658 16515659 16515660 16515661 16515662 16515663 16515664 16515665 16515666 16515667 16515668 16515669 3277119 3277120 3277121 3277130 3277132 3277154 3277157 3277160 3277164 3277169 3277171 3277189 3604485 3604508 3604528 3604550 4620302 4849683 4849719 9306149 8 2008-03-24 11:31:02.937 2011-03-23 11:46:24.147 3114327 3114328 12484681 12484683 15630865 15630866 16416903 12025858 3637901 3114109 3114325 3114109 3145737 3670652 4030471 4030472 3604658 3604663 3604664 4849763 3 2008-05-07 14:27:52.313 2008-05-21 13:07:05.827 3637911 3932165 3735594 3735595 3637913 3114109 3114325 3114109 3145737 3670663 3708055 3708056 3604665 4096011 1 2008-05-07 14:41:34.140 2008-05-07 14:41:34.140 3735597 3637915 3114109 3114325 3114109 3145737 3670665 3708057 3708058 3604668 3604677 1 2008-05-07 14:46:38.550 2008-05-07 14:46:38.550 3735598 3735599 3637917 3114109 3114325 3114109 3145737 3670667 3708059 3708060 3604669 4096009 1 2008-05-07 14:52:32.897 2008-05-07 14:52:32.897 9371909 3114325 3114325 3145737 9404658 11338774 11338775 11338776 11338777 11338778 11338779 11338780 11338781 11338782 11338783 11338784 11338785 11338786 13 2009-02-25 16:45:05.063 2010-02-03 10:21:11.777 9371911 9371913 9371915 9371917 9371919 9371936 9371940 9372257 9372258 9798273 9798275 11239724 15794179 3114109 3114325 3114123 3114128 3114132 3114136 3114231 3114238 3114242 3637328 3637401 3637431 3637433 3637480 3637488 3637497 3637503 3637505 3637511 3637515 3637523 3637883 3637901 3637905 3637913 3637915 3637917 3638124 3114325 3145737 3179591 5507376 5507377 5507378 5507379 5507380 5507381 5507382 5507383 5507384 5507385 5507386 5507387 5507388 5507389 5507390 5507391 5507392 5507393 5507394 5507395 5507396 5507397 5507398 5507399 5507400 5507401 5507402 5507403 5507404 5507405 5507406 5507407 5507408 5507409 3277052 3277054 3277056 3277057 3277059 3277073 3277074 3277090 3277094 3277097 3277098 3277099 3277125 3277127 3277133 3277153 3277155 3277156 3277168 3277176 3277177 3604484 3604506 3604511 3604529 3604530 3604534 3604536 3604537 3604538 3604541 3604547 3604553 3604556 3604560 3604561 3604563 3604565 3604568 3604571 3604574 3604581 3604654 3604657 3604662 3604666 3604667 3604670 3604703 4849682 4849743 4849770 4849776 4685825 77 2008-03-21 17:04:00.783 2008-07-01 13:50:12.253 3114111 3114113 3114115 3114117 3114118 3114121 3114126 3114127 3114140 3114141 3114142 3114143 3114144 3114145 3114228 3114235 3114253 3114254 3114266 3114268 3114361 3114362 3114364 3114366 3114368 3114370 3114372 3114374 3114376 3114377 3637327 3637380 3637381 3637385 3637387 3637396 3637403 3637422 3637424 3637425 3637427 3637429 3637434 3637436 3637438 3637439 3637456 3637458 3637459 3637462 3637463 3637466 3637469 3637471 3637473 3637481 3637483 3637498 3637500 3637507 3637513 3637519 3637520 3637521 3637524 3637903 3637906 3637908 3637933 3638123 4456459 4456460 4456464 4456465 4456515 5374690 3735568 5275678 3114325 3114325 3145737 5308446 9439808 9439809 6 2008-06-11 11:07:52.247 2009-03-17 14:47:36.060 5275680 5373988 5373996 9372211 9372265 4915268 3114325 3114325 3145737 4948031 5341190 3 2008-06-09 14:42:02.883 2008-06-10 10:29:39.167 4915270 5275655 19041215 3114325 3114325 3145737 19073905 6 2012-11-14 18:40:38.063 2012-11-27 16:12:35.230 19041217 19041218 19041220 19041221 19041336 3244059 FOCE false global ]]> 3244058 2]]> 3244057 theme.key ]]> 3637401 3114109 3114325 3114109 3145737 3670159 3704649 3704650 3604531 3604532 3604533 3604635 6 2008-04-18 15:59:48.483 2008-04-18 16:07:53.157 3637404 3637406 3637408 3637409 3637411 3735567 3114389 3114325 3114325 3145737 3179861 9896465 9896466 9896467 9896468 9896469 9896470 3277131 3277134 3277135 3277136 3277137 3277138 3277139 3277140 3604593 3604641 3604647 4849695 28 2008-03-27 08:13:59.440 2009-04-22 10:00:10.420 3114391 3114393 3114395 3114397 3114398 3114400 3114402 3114404 3114406 3114408 3114413 3114415 3114422 3114425 3114427 3114430 3114432 3114435 3114437 3637856 3932189 3932191 4915272 4915281 5374719 9371907 9797768 7766069 3114325 3114325 3145737 7798833 7864484 7864485 7864486 1 2008-11-13 10:37:50.977 2008-11-13 10:37:50.977 5374755 3114325 3114325 3145737 5407485 7 2008-07-11 10:37:50.190 2008-07-11 11:27:25.390 5374756 5374758 5374759 5374760 5374762 5374764 3114123 3114109 3114325 3114109 3145737 3179604 3704598 3704599 3704600 3704601 3277060 3277061 3277116 3277165 4849748 4849775 17 2008-03-22 13:50:46.927 2008-04-18 14:57:50.240 3114270 3114272 3114273 3114275 3114276 3114278 3114280 3114282 3114284 3114286 3114288 3114289 3114290 3114291 3114363 3637383 3309662 3309663 3309664 3309665 10354905 3114325 3114325 3145737 10387670 10455682 10455683 10455684 10455685 5 2009-06-06 11:55:49.357 2009-06-07 15:06:33.247 10354908 10354910 10354911 10354912 3114128 3114109 3114325 3114109 3145737 3179609 3277062 3277064 3277065 3277066 3277071 3277111 3277126 6 2008-03-22 13:57:49.963 2008-03-25 09:04:37.503 3114246 3114247 3114249 3114251 3114365 3309660 3309661 3114132 3114109 3114325 3114109 3145737 3179613 4292609 4292610 4292611 3277067 3277088 3277089 3277124 3277190 4849762 31 2008-03-22 14:00:47.203 2008-05-28 13:03:21.060 3114205 3114207 3114208 3114210 3114212 3114214 3114215 3114217 3114219 3114220 3114222 3114223 3114224 3114225 3114226 3114367 3114441 3114501 3637361 3637364 3637365 3637366 3637367 3637369 3637370 3637371 3637372 3637379 3637395 4194305 3309653 3309654 3114136 3114109 3114325 3114109 3145737 3179617 3704621 3704622 3704623 3704624 3277069 3277078 3277079 3277083 3277084 3277114 3277128 31 2008-03-22 14:02:36.787 2008-04-18 15:25:52.683 3114154 3114155 3114157 3114159 3114161 3114163 3114165 3114167 3114292 3114294 3114296 3114298 3114300 3114302 3114304 3114306 3114308 3114310 3114311 3114313 3114314 3114316 3114318 3114369 3114444 3114445 3637389 3637390 3637392 3637394 3309649 3309650 3309666 3637480 3114109 3114325 3114109 3145737 3670235 3706479 3706480 3706481 3706482 3604549 3604551 3604552 4620294 4 2008-04-22 08:52:21.083 2008-04-22 08:58:33.510 3637482 3637485 3637486 3735571 19040558 3114325 3114325 3145737 19073259 19163847 19163848 19163849 19163850 19163851 21 2012-08-16 08:24:37.683 2012-09-11 17:47:48.180 19040560 19040562 19040564 19040566 19040568 19040570 19040572 19040574 19040576 19040578 19040580 19040582 19040584 19040585 19040596 19040600 19040601 19040603 19040609 19040825 19234825 19234826 19234827 18252384 3114325 3114325 3145737 18285142 1 2011-10-05 14:39:48.843 2011-10-05 14:39:48.843 19041144 3114325 3114325 3145737 19073835 1 2012-11-07 21:33:34.390 2012-11-07 21:33:34.390 6259368 3114325 3114325 3145737 6226571 16515488 16515489 16515490 16515491 16515492 16515493 18 2008-10-16 15:14:27.940 2011-03-16 13:33:33.317 6259384 6259386 6259387 6259390 6259392 6259394 6259396 6259398 6259400 6259401 6259403 6259404 6259406 7372805 7766131 10356100 16416842 6291601 6291598 6291599 6291600 6291602 6291603 6291604 6291605 6291606 6291608 6291609 6291607 19041133 3114325 3114325 3145737 19073824 5 2012-11-07 16:36:06.830 2012-11-07 17:28:41.507 19041135 19041137 19041139 19041140 6259359 3114325 3114325 8913245 3145737 6226562 16515630 16515631 16515632 16515633 15 2008-10-16 14:24:15.190 2011-03-22 17:25:55.827 6259361 6259364 6259366 6259371 6259373 6259381 7372802 7372803 7372807 9798441 10356098 11796710 16416887 16416889 6291597 19040598 3114325 3114325 3145737 19073296 19161405 19161406 4 2012-08-16 16:22:30.540 2012-08-16 16:48:36.353 19040599 19040614 19040615 3114446 3114325 3114325 3145737 3179918 3277158 3277159 3277161 3277163 4620290 5 2008-04-01 09:42:41.390 2008-04-01 16:53:45.213 3114448 3114450 3114451 3114471 6259322 3114325 3114325 3145737 6226525 6326276 1 2008-10-09 10:31:23.777 2008-10-09 10:31:23.777 19040591 3114325 3114325 3145737 19073290 7 2012-08-16 15:59:18.553 2012-11-07 21:07:12.060 19040593 19040595 19040604 19040606 19040610 19041142 19040612 3114325 3114325 3145737 19073310 1 2012-08-16 16:45:18.003 2012-08-16 16:45:18.003 3637433 3114109 3114325 3114109 3145737 3670189 3708065 3708066 3708067 3604539 3604546 3604672 3 2008-04-18 16:47:51.197 2008-05-07 15:01:56.157 3637923 3637924 3735601 3637431 3114109 3114325 3114109 3145737 3670188 3708068 3708069 3708070 3604540 3604548 3604671 3 2008-04-18 16:47:42.230 2008-05-07 15:02:22.363 3637919 3637925 3735600 19040617 3114325 3114325 3145737 19073314 19161407 2 2012-08-16 16:50:06.677 2012-08-16 16:57:11.557 19040619 19040608 3114325 3114325 3145737 19073306 19161410 19161411 3 2012-08-16 16:39:55.847 2012-08-16 17:14:44.990 19040621 19040623 4849769 2 3637503 2008-06-06 06:49:15.040 2008-06-06 06:50:15.027 4849768 2 3637503 2008-06-06 06:49:15.027 2008-06-06 06:50:15.023 3637517 3670272 1 2008-04-22 09:58:11.307 2008-04-22 09:58:11.307 3637515 19040623 19073320 2 2012-08-16 16:39:55.847 2012-08-16 17:03:09.987 19040608 19040621 19073318 1 2012-08-16 16:39:55.847 2012-08-16 16:39:55.847 19040608 3637521 3670276 64 2008-03-21 17:04:00.783 2008-04-22 10:04:03.943 3114109 4849763 1 3637901 2008-06-05 13:35:15.047 2008-06-05 13:35:15.047 3637520 3670275 63 2008-03-21 17:04:00.783 2008-04-22 10:03:25.203 3114109 19040619 19073316 1 2012-08-16 16:50:06.677 2012-08-16 16:50:06.677 19040617 4849762 1 3114132 2008-06-05 13:34:15.100 2008-06-05 13:34:15.100 3637519 3670274 62 2008-03-21 17:04:00.783 2008-04-22 09:56:19.437 3114109 19040632 19073329 1 2012-08-16 17:27:30.563 2012-08-16 17:27:30.563 19040630 3637524 3670279 65 2008-03-21 17:04:00.783 2008-04-22 10:04:36.953 3114109 19040628 19073325 2 2012-08-16 17:18:45.410 2012-08-16 17:19:51.280 19040625 19040627 19073324 1 2012-08-16 17:18:45.410 2012-08-16 17:18:45.410 19040625 19040642 19073339 5 2012-08-16 17:27:30.563 2012-08-17 08:48:52.883 19040630 19040640 19073337 4 2012-08-16 17:27:30.563 2012-08-17 08:38:31.550 19040630 19040637 19073334 2 2012-08-16 17:27:30.563 2012-08-16 17:42:21.150 19040630 19040638 19073335 3 2012-08-16 17:27:30.563 2012-08-17 08:38:06.550 19040630 4849776 1 3114109 2008-06-06 14:19:15.067 2008-06-06 14:19:15.067 19040650 19073347 10 2012-08-16 17:27:30.563 2012-08-17 09:38:30.730 19040630 4849774 1 3637497 2008-06-06 11:20:15.023 2008-06-06 11:20:15.023 4849775 1 3114123 2008-06-06 13:40:15.033 2008-06-06 13:40:15.033 19040648 19073345 9 2012-08-16 17:27:30.563 2012-08-17 09:33:55.683 19040630 4849772 1 3637523 2008-06-06 11:17:15.023 2008-06-06 11:17:15.023 19040645 19073342 7 2012-08-16 17:27:30.563 2012-08-17 09:32:25.693 19040630 4849773 3 3637488 2008-06-06 11:19:15.023 2008-06-06 12:19:15.090 19040646 19073343 8 2012-08-16 17:27:30.563 2012-08-17 09:32:42.490 19040630 4849770 1 3114109 2008-06-06 06:49:15.060 2008-06-06 06:49:15.060 4849771 1 3637488 2008-06-06 11:06:15.060 2008-06-06 11:06:15.060 19040644 19073341 6 2012-08-16 17:27:30.563 2012-08-17 08:58:21.863 19040630 19040656 19073353 13 2012-08-16 17:27:30.563 2012-08-17 09:58:19.267 19040630 3637483 3670238 57 2008-03-21 17:04:00.783 2008-04-22 08:52:56.930 3114109 3637486 3670241 3 2008-04-22 08:52:21.083 2008-04-22 08:58:09.703 3637480 19040658 19073355 14 2012-08-16 17:27:30.563 2012-08-17 10:01:52.137 19040630 3637485 3670240 2 2008-04-22 08:52:21.083 2008-04-22 08:52:56.950 3637480 19040652 19073349 11 2012-08-16 17:27:30.563 2012-08-17 09:45:14.860 19040630 3637490 3670245 1 2008-04-22 09:00:30.627 2008-04-22 09:00:30.627 3637488 19040654 19073351 12 2012-08-16 17:27:30.563 2012-08-17 09:50:47.013 19040630 3637492 3670247 3 2008-04-22 09:00:30.627 2008-04-22 09:03:44.723 3637488 19040664 19073361 18 2012-08-16 17:27:30.563 2012-08-17 10:15:27.190 19040630 3637491 3670246 2 2008-04-22 09:00:30.627 2008-04-22 09:03:17.357 3637488 19040663 19073360 17 2012-08-16 17:27:30.563 2012-08-17 10:13:36.090 19040630 3637494 3670249 4 2008-04-22 09:00:30.627 2008-04-22 09:04:10.540 3637488 19040660 19073357 15 2012-08-16 17:27:30.563 2012-08-17 10:05:43.270 19040630 3637495 3670250 5 2008-04-22 09:00:30.627 2008-04-22 09:13:44.007 3637488 3637498 3670253 58 2008-03-21 17:04:00.783 2008-04-22 08:54:00.823 3114109 19040661 19073358 16 2012-08-16 17:27:30.563 2012-08-17 10:09:09.173 19040630 3637499 3670254 1 2008-04-22 09:19:34.593 2008-04-22 09:19:34.593 3637497 3637500 3670255 59 2008-03-21 17:04:00.783 2008-04-22 09:19:53.750 3114109 3637501 3670256 6 2008-04-22 09:00:30.627 2008-04-22 09:14:01.263 3637488 15794179 15761409 9371909 2011-01-06 19:19:34.560 2011-01-06 19:19:34.560 3637507 3670262 60 2008-03-21 17:04:00.783 2008-04-22 09:20:08.077 3114109 3637508 3670263 1 2008-04-22 09:42:57.407 2008-04-22 09:42:57.407 3637505 3637509 3670264 2 2008-04-22 09:42:57.407 2008-04-22 09:46:46.953 3637505 3637513 3670268 61 2008-03-21 17:04:00.783 2008-04-22 09:46:46.937 3114109 4849695 1 3114389 2008-06-03 13:28:15.020 2008-06-03 13:28:15.020 3309654 3114132 2008-03-22 16:36:18.017 2008-03-22 16:36:18.017 111309 1 3309657 3114238 2008-03-23 11:21:01.900 2008-03-23 11:21:01.900 27332 1 3309656 3114231 2008-03-23 11:18:54.037 2008-03-23 11:18:54.037 79655 1 3309659 3114242 2008-03-23 11:34:47.797 2008-03-23 11:34:47.797 59949 1 3309658 3114242 2008-03-23 11:24:40.350 2008-03-23 11:24:40.350 32967 1 3309661 3114128 2008-03-23 11:47:18.453 2008-03-23 11:47:18.453 319475 1 4849718 1 3637883 2008-06-03 16:17:15.037 2008-06-03 16:17:15.037 3309660 3114128 2008-03-23 11:40:04.400 2008-03-23 11:40:04.400 42597 1 4849719 1 3114325 2008-06-03 16:17:15.060 2008-06-03 16:17:15.060 3309649 3114136 2008-03-22 14:34:44.077 2008-03-22 14:34:44.077 15699 1 4849706 4 3637328 2008-06-03 14:02:15.060 2008-06-03 14:04:15.023 3309650 3114136 2008-03-22 14:36:36.843 2008-03-22 14:36:36.843 340513 1 3309653 3114132 2008-03-22 16:24:43.787 2008-03-22 16:24:43.787 98130 1 3707950 3637883 2008-05-07 13:44:44.367 2008-05-07 13:44:44.367 3707948 3637883 2008-05-07 13:44:44.367 2008-05-07 13:44:44.367 3707949 3637883 2008-05-07 13:44:44.367 2008-05-07 13:44:44.367 19160634 18252651 2012-08-09 13:16:14.530 2012-08-09 13:16:14.530 19160635 18252651 2012-08-09 13:16:14.530 2012-08-09 13:16:14.530 3309664 3114123 2008-03-23 12:49:09.597 2008-03-23 12:49:09.597 57960 1 3309665 3114123 2008-03-23 12:51:46.433 2008-03-23 12:51:46.433 56625 1 3309662 3114123 2008-03-23 12:23:50.297 2008-03-23 12:23:50.297 92342 1 19160636 18252651 2012-08-09 13:16:14.530 2012-08-09 13:16:14.530 3309663 3114123 2008-03-23 12:48:47.980 2008-03-23 12:48:47.980 60035 1 3309666 3114136 2008-03-23 13:11:01.953 2008-03-23 13:11:01.953 78214 1 4849748 1 3114123 2008-06-04 14:01:15.073 2008-06-04 14:01:15.073 4849743 4 3114109 2008-06-04 09:10:15.043 2008-06-09 08:39:15.093 5374690 5407421 76 2008-03-21 17:04:00.783 2008-05-31 11:46:50.627 3114109 19040506 19073207 19 2011-12-09 15:58:37.633 2012-08-02 13:30:06.593 18252651 7372807 7405575 9 2008-10-16 14:24:15.190 2008-11-05 11:15:40.113 6259359 7372805 7405573 14 2008-10-16 15:14:27.940 2008-10-16 16:57:39.947 6259368 3114452 3114238 3179924 1 2008-04-01 09:57:33.687 2008-04-01 09:57:33.687 7372803 7405571 8 2008-10-16 14:24:15.190 2008-11-05 11:15:01.507 6259359 7372802 7405570 7 2008-10-16 14:24:15.190 2008-10-16 15:28:30.540 6259359 19040510 19073211 22 2011-12-09 15:58:37.633 2012-08-09 13:13:00.983 18252651 19040509 19073210 21 2011-12-09 15:58:37.633 2012-08-09 13:11:30.180 18252651 19040507 19073208 20 2011-12-09 15:58:37.633 2012-08-09 13:10:40.593 18252651 4194305 4227073 30 2008-03-22 14:00:47.203 2008-04-18 15:27:04.753 3114132 19040566 19073267 4 2012-08-16 08:24:37.683 2012-08-16 08:50:46.927 19040558 3932191 3964958 22 2008-03-27 08:13:59.440 2008-05-23 16:18:05.960 3114389 19040564 19073265 3 2012-08-16 08:24:37.683 2012-08-16 08:37:52.550 19040558 19040570 19073271 6 2012-08-16 08:24:37.683 2012-08-16 08:59:06.083 19040558 19040568 19073269 5 2012-08-16 08:24:37.683 2012-08-16 08:55:42.273 19040558 3932189 3964956 21 2008-03-27 08:13:59.440 2008-05-06 16:32:46.740 3114389 7864486 7766069 2008-11-13 10:37:51.007 2008-11-13 10:37:51.007 19040562 19073263 2 2012-08-16 08:24:37.683 2012-08-16 08:28:05.810 19040558 7864484 7766069 2008-11-13 10:37:51.007 2008-11-13 10:37:51.007 3708051 3637905 2008-05-07 14:34:38.780 2008-05-07 14:34:38.780 19040560 19073261 1 2012-08-16 08:24:37.683 2012-08-16 08:24:37.683 19040558 7864485 7766069 2008-11-13 10:37:51.007 2008-11-13 10:37:51.007 3708050 3637905 2008-05-07 14:34:38.780 2008-05-07 14:34:38.780 19040582 19073283 12 2012-08-16 08:24:37.683 2012-08-16 10:31:45.983 19040558 8913245 6259359 8945998 1 2009-02-05 11:14:25.947 2009-02-05 11:14:25.947 19040580 19073281 11 2012-08-16 08:24:37.683 2012-08-16 10:07:45.727 19040558 19534262 19040630 2013-01-11 16:36:14.977 2013-01-11 16:36:14.977 19040585 19073286 14 2012-08-16 08:24:37.683 2012-08-16 10:43:08.337 19040558 19040584 19073285 13 2012-08-16 08:24:37.683 2012-08-16 10:38:36.163 19040558 19534260 19040630 2013-01-11 16:36:14.977 2013-01-11 16:36:14.977 19534261 19040630 2013-01-11 16:36:14.977 2013-01-11 16:36:14.977 19040574 19073275 8 2012-08-16 08:24:37.683 2012-08-16 09:34:39.903 19040558 19040572 19073273 7 2012-08-16 08:24:37.683 2012-08-16 09:26:13.427 19040558 19040578 19073279 10 2012-08-16 08:24:37.683 2012-08-16 10:03:03.847 19040558 3932180 3964947 6 2008-04-15 10:13:33.937 2008-05-21 09:23:21.157 3637328 11796739 11829496 30 2009-02-26 13:59:15.167 2009-05-07 10:12:48.567 9371938 19040576 19073277 9 2012-08-16 08:24:37.683 2012-08-16 09:43:48.917 19040558 19040595 19073294 2 2012-08-16 15:59:18.553 2012-08-16 16:01:51.983 19040591 6291599 6259368 2008-10-16 15:36:28.703 2008-10-16 15:36:28.703 53938 1 3708070 3637431 2008-05-07 15:02:22.370 2008-05-07 15:02:22.370 6291598 6259368 2008-10-16 15:30:58.887 2008-10-16 15:44:20.117 115121 2 19040596 19073295 15 2012-08-16 08:24:37.683 2012-08-16 15:54:13.337 19040558 3932161 3964929 5 2008-04-15 10:13:33.937 2008-04-18 16:19:32.820 3637328 3708069 3637431 2008-05-07 15:02:22.370 2008-05-07 15:02:22.370 6291601 6259368 2008-10-16 15:30:58.887 2008-10-16 15:30:58.887 115121 1 6291598 3708068 3637431 2008-05-07 15:02:22.370 2008-05-07 15:02:22.370 6291600 6259368 2008-10-16 15:43:29.953 2008-10-16 15:43:29.953 74485 1 19040599 19073297 1 2012-08-16 16:22:30.540 2012-08-16 16:22:30.540 19040598 6291603 6259368 2008-10-16 15:45:02.247 2008-10-16 15:45:02.247 101200 1 6291602 6259368 2008-10-16 15:44:36.257 2008-10-16 15:44:36.257 101297 1 19040600 19073298 16 2012-08-16 08:24:37.683 2012-08-16 16:20:13.693 19040558 6291605 6259368 2008-10-16 15:56:47.027 2008-10-16 15:56:47.027 29911 1 19040601 19073299 17 2012-08-16 08:24:37.683 2012-08-16 16:25:07.097 19040558 6291604 6259368 2008-10-16 15:45:45.363 2008-10-16 15:45:45.363 110162 1 6291607 6259368 2008-10-16 16:11:25.607 2008-10-16 16:11:25.607 23745 1 6291606 6259368 2008-10-16 16:06:43.303 2008-10-16 16:25:01.607 63065 3 3932169 3964937 3 2008-04-22 09:42:57.407 2008-04-22 09:46:58.630 3637505 6291609 6259368 2008-10-16 16:06:43.303 2008-10-16 16:21:17.717 42944 2 6291606 3932168 3964936 8 2008-04-22 09:00:30.627 2008-05-07 13:25:06.317 3637488 6291608 6259368 2008-10-16 16:06:43.303 2008-10-16 16:06:43.303 35593 1 6291606 3932166 3964934 2 2008-04-22 09:19:34.593 2008-04-22 09:19:53.760 3637497 3932165 3964933 2 2008-05-07 14:27:52.313 2008-05-07 14:35:19.007 3637901 19040593 19073292 1 2012-08-16 15:59:18.553 2012-08-16 15:59:18.553 19040591 3932164 3964932 2 2008-04-22 10:16:03.100 2008-05-21 13:06:17.930 3637523 3932163 3964931 1 2008-04-22 10:16:03.100 2008-04-22 10:16:03.100 3637523 3708055 3637913 2008-05-07 14:41:34.187 2008-05-07 14:41:34.187 19040614 19073312 2 2012-08-16 16:22:30.540 2012-08-16 16:24:44.727 19040598 3708052 3637905 2008-05-07 14:34:38.780 2008-05-07 14:34:38.780 3708058 3637915 2008-05-07 14:46:38.583 2008-05-07 14:46:38.583 19040615 19073313 3 2012-08-16 16:22:30.540 2012-08-16 16:48:01.943 19040598 3708059 3637917 2008-05-07 14:52:32.930 2008-05-07 14:52:32.930 3708056 3637913 2008-05-07 14:41:34.187 2008-05-07 14:41:34.187 3708057 3637915 2008-05-07 14:46:38.583 2008-05-07 14:46:38.583 19040604 19073302 3 2012-08-16 15:59:18.553 2012-08-16 16:18:48.417 19040591 19040603 19073301 18 2012-08-16 08:24:37.683 2012-08-16 16:25:40.970 19040558 19040606 19073304 4 2012-08-16 15:59:18.553 2012-08-16 16:34:08.593 19040591 3708060 3637917 2008-05-07 14:52:32.930 2008-05-07 14:52:32.930 3708066 3637433 2008-05-07 15:01:56.167 2008-05-07 15:01:56.167 3708067 3637433 2008-05-07 15:01:56.167 2008-05-07 15:01:56.167 19040610 19073308 5 2012-08-16 15:59:18.553 2012-08-16 16:36:19.463 19040591 3708065 3637433 2008-05-07 15:01:56.167 2008-05-07 15:01:56.167 6291597 6259359 2008-10-16 14:28:17.063 2008-10-16 14:28:17.063 25376 1 19040609 19073307 19 2012-08-16 08:24:37.683 2012-08-16 16:34:08.577 19040558 3604653 10 3637883 2008-05-07 13:25:15.027 2008-05-07 13:45:15.033 3604652 1 3637883 2008-05-07 13:24:15.027 2008-05-07 13:24:15.027 3604655 5 3637883 2008-05-07 13:32:15.027 2008-05-07 13:45:15.030 19040380 19073082 18 2011-12-09 15:58:37.633 2012-08-02 12:20:00.070 18252651 3604654 6 3114109 2008-05-07 13:25:15.057 2008-05-21 13:08:15.037 3604657 6 3114109 2008-05-07 14:28:15.037 2008-05-21 13:08:15.030 3604656 2 3637511 2008-05-07 13:35:15.027 2008-06-02 09:29:15.033 3604659 2 3637905 2008-05-07 14:29:15.020 2008-05-07 14:35:15.023 3604658 1 3637901 2008-05-07 14:28:15.040 2008-05-07 14:28:15.040 3604661 5 3637905 2008-05-07 14:30:15.027 2008-05-21 13:08:15.023 3604660 1 3637905 2008-05-07 14:29:15.023 2008-05-07 14:29:15.023 4456524 4489287 1 2008-04-22 09:55:17.747 2008-04-22 09:55:17.747 3637511 3604663 3 3637901 2008-05-07 14:35:15.017 2008-05-21 13:07:15.027 3604662 2 3114109 2008-05-07 14:30:15.030 2008-05-07 14:35:15.020 3604665 1 3637913 2008-05-07 14:42:15.027 2008-05-07 14:42:15.027 3604664 2 3637901 2008-05-07 14:36:15.023 2008-05-21 13:07:15.063 19040367 19073069 13 2011-12-09 15:58:37.633 2012-08-02 11:11:12.760 18252651 3604635 5 3637401 2008-05-02 08:18:15.027 2008-05-31 16:20:15.037 19040369 19073071 14 2011-12-09 15:58:37.633 2012-08-02 11:15:08.060 18252651 19040363 19073065 11 2011-12-09 15:58:37.633 2012-01-09 17:58:05.250 18252651 19040365 19073067 12 2011-12-09 15:58:37.633 2012-08-02 11:06:05.373 18252651 3604641 2 3114389 2008-05-05 11:32:15.087 2008-05-05 11:33:15.020 3604642 1 3637488 2008-05-05 11:34:15.037 2008-05-05 11:34:15.037 19040375 19073077 16 2011-12-09 15:58:37.633 2012-08-02 11:20:08.697 18252651 19040377 19073079 17 2011-12-09 15:58:37.633 2012-08-02 12:17:10.177 18252651 19040371 19073073 15 2011-12-09 15:58:37.633 2012-08-02 11:17:39.307 18252651 3604647 3 3114389 2008-05-06 16:30:15.037 2008-06-02 17:05:15.167 11796710 11829467 12 2008-10-16 14:24:15.190 2009-09-02 10:54:16.777 6259359 3604668 1 3637915 2008-05-07 14:47:15.023 2008-05-07 14:47:15.023 4456516 4489279 3 2008-04-22 10:16:03.100 2008-05-21 13:06:36.337 3637523 3604669 1 3637917 2008-05-07 14:53:15.017 2008-05-07 14:53:15.017 4456515 4489278 75 2008-03-21 17:04:00.783 2008-05-30 08:25:06.043 3114109 3604666 1 3114109 2008-05-07 14:42:15.030 2008-05-07 14:42:15.030 4456518 4489281 3 2008-04-22 09:19:34.593 2008-05-21 13:08:11.167 3637497 3604667 2 3114109 2008-05-07 14:47:15.020 2008-05-07 14:47:15.020 4456520 4489283 4 2008-04-22 09:42:57.407 2008-05-21 13:09:15.187 3637505 3604672 2 3637433 2008-05-07 15:00:15.027 2008-05-07 15:02:15.340 3604673 8 3637505 2008-05-08 08:41:15.043 2008-05-31 15:49:15.020 3604670 2 3114109 2008-05-07 14:53:15.020 2008-05-07 14:53:15.020 4456522 4489285 4 2008-04-22 10:16:03.100 2008-05-31 15:22:56.757 3637523 3604671 2 3637431 2008-05-07 14:58:15.053 2008-05-07 15:03:15.027 3604677 6 3637915 2008-05-14 09:58:15.023 2008-05-31 16:47:15.020 19073905 19041215 4456465 4489233 74 2008-03-21 17:04:00.783 2008-05-29 17:25:16.120 3114109 3637352 3670111 8 2008-03-23 11:17:30.410 2008-04-01 14:43:37.283 3114231 19073824 {noformat}\\ \\ \\]]> 19041133 4456464 4489232 73 2008-03-21 17:04:00.783 2008-05-29 13:57:30.280 3114109 4456459 4489227 71 2008-03-21 17:04:00.783 2008-05-19 16:45:40.787 3114109 4456460 4489228 72 2008-03-21 17:04:00.783 2008-05-29 13:57:05.183 3114109 3604702 1 3638124 2008-05-19 16:52:15.043 2008-05-19 16:52:15.043 3637327 3670089 31 2008-03-21 17:04:00.783 2008-03-25 11:41:40.477 3114109 3604703 6 3114109 2008-05-19 16:52:15.070 2008-05-21 09:18:15.150 3637330 3670092 1 2008-04-15 10:13:33.937 2008-04-15 10:13:33.937 3637328 3604701 7 3638124 2008-05-19 16:52:15.020 2008-05-31 16:42:15.017 4096011 5 3637913 2008-05-27 14:39:15.027 2008-05-31 16:46:15.020 9502768 9372007 2009-03-03 12:53:28.867 2009-03-03 13:49:25.380 15954 7 9502758 9502769 9372007 2009-03-03 12:53:28.867 2009-03-03 14:41:27.470 23859 8 9502758 9502766 9372007 2009-03-03 12:53:28.867 2009-03-03 13:44:12.467 15160 6 9502758 9502767 9372007 2009-03-03 14:32:30.223 2009-03-03 14:32:30.223 13680 1 4096001 4 3637523 2008-05-21 13:07:15.067 2008-06-02 09:19:15.047 4456456 4489224 13 2008-03-23 11:17:30.410 2008-04-18 14:38:26.283 3114231 9502765 9372007 2009-03-03 12:53:28.867 2009-03-03 13:44:06.867 15160 5 9502758 9502764 9372007 2009-03-03 12:53:28.867 2009-03-03 13:35:36.273 12658 4 9502758 9502763 9372007 2009-03-03 12:53:28.867 2009-03-03 13:29:27.653 11046 3 9502758 9502762 9372007 2009-03-03 12:53:28.867 2009-03-03 13:19:40.447 5073 2 9502758 9502761 9372007 2009-03-03 12:53:28.867 2009-03-03 12:53:28.867 133 1 9502758 9502760 9372007 2009-03-03 13:07:09.383 2009-03-03 13:07:09.383 173221 1 9502759 9372007 2009-03-03 13:06:07.773 2009-03-03 13:06:07.773 141111 1 9502758 9372007 2009-03-03 12:53:28.867 2009-03-03 15:07:06.793 31529 9 4096009 4 3637917 2008-05-24 15:13:15.043 2008-05-31 15:27:15.023 19073835 19041144 4096002 1 3637488 2008-05-21 13:43:15.040 2008-05-21 13:43:15.040 3604530 2 3114109 2008-04-18 15:29:15.060 2008-04-18 16:00:15.017 3637412 3670170 12 2008-03-23 11:21:57.880 2008-03-25 09:04:38.407 3114242 5374719 5407450 25 2008-03-27 08:13:59.440 2008-06-09 17:55:29.957 3114389 3604531 1 3637401 2008-04-18 16:00:15.027 2008-04-18 16:00:15.027 3637411 3670169 5 2008-04-18 15:59:48.483 2008-04-18 16:07:13.490 3637401 3637414 3670172 13 2008-03-23 11:21:57.880 2008-04-18 16:08:36.837 3114242 3604532 1 3637401 2008-04-18 16:03:15.043 2008-04-18 16:03:15.043 3604533 4 3637401 2008-04-18 16:05:15.027 2008-04-18 16:08:15.063 3604534 3 3114109 2008-04-18 16:08:15.080 2008-04-18 16:09:15.023 3637416 3670174 2 2008-04-15 10:13:33.937 2008-04-15 10:32:36.550 3637328 3604535 5 3114242 2008-04-18 16:09:15.020 2008-05-31 16:45:15.023 3637415 3670173 14 2008-03-23 11:21:57.880 2008-04-18 16:11:06.227 3114242 3604536 1 3114109 2008-04-18 16:12:15.027 2008-04-18 16:12:15.027 3637418 3670176 3 2008-04-15 10:13:33.937 2008-04-18 16:12:21.287 3637328 3604537 6 3114109 2008-04-18 16:20:15.020 2008-05-29 10:30:15.023 3637404 3670162 1 2008-04-18 15:59:48.483 2008-04-18 15:59:48.483 3637401 3637403 3670161 37 2008-03-21 17:04:00.783 2008-04-18 15:28:14.043 3114109 3637406 3670164 2 2008-04-18 15:59:48.483 2008-04-18 16:02:49.640 3637401 3637408 3670166 3 2008-04-18 15:59:48.483 2008-04-18 16:04:32.423 3637401 3604528 1 3114325 2008-04-18 14:28:15.033 2008-04-18 14:28:15.033 3604529 12 3114109 2008-04-18 14:59:15.030 2008-05-28 11:28:15.013 3637409 3670167 4 2008-04-18 15:59:48.483 2008-04-18 16:06:56.890 3637401 3637395 3670153 29 2008-03-22 14:00:47.203 2008-04-18 14:39:15.187 3114132 3637396 3670154 36 2008-03-21 17:04:00.783 2008-04-18 15:00:37.597 3114109 11338775 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3637397 3670155 4 2008-03-23 11:20:18.790 2008-03-25 09:04:37.837 3114238 11338774 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3637398 3670156 5 2008-03-23 11:20:18.790 2008-04-18 15:28:14.057 3114238 11338777 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 11338776 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3637400 3670158 6 2008-03-23 11:20:18.790 2008-04-18 15:29:04.787 3114238 11338779 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 11338778 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3637387 3670145 35 2008-03-21 17:04:00.783 2008-04-18 14:58:59.457 3114109 11338781 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3604507 20 3637328 2008-04-15 10:14:15.017 2008-05-31 16:21:15.027 3604506 9 3114109 2008-04-15 10:11:15.067 2008-06-02 15:44:15.060 11338780 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 11338783 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3604509 1 3637328 2008-04-15 10:14:15.027 2008-04-15 10:14:15.027 3637389 3670147 27 2008-03-22 14:02:36.787 2008-04-01 09:35:42.090 3114136 11338782 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3604508 3 3114325 2008-04-15 10:14:15.020 2008-04-23 09:13:15.067 3637390 3670148 28 2008-03-22 14:02:36.787 2008-04-18 15:01:32.787 3114136 3604511 1 3114109 2008-04-15 11:50:15.087 2008-04-15 11:50:15.087 11338785 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 11338784 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3604510 6 3637328 2008-04-15 10:33:15.917 2008-05-22 11:18:15.017 3637392 3670150 29 2008-03-22 14:02:36.787 2008-04-18 15:02:31.593 3114136 11338786 9371909 2010-02-03 10:21:11.847 2010-02-03 10:21:11.847 3637394 3670152 30 2008-03-22 14:02:36.787 2008-04-18 15:22:48.617 3114136 3604564 1 3637505 2008-04-22 09:43:15.030 2008-04-22 09:43:15.030 3637381 3670139 33 2008-03-21 17:04:00.783 2008-04-18 14:40:15.220 3114109 3604565 5 3114109 2008-04-22 09:47:15.020 2008-05-31 15:59:15.027 3637380 3670138 32 2008-03-21 17:04:00.783 2008-04-15 10:13:07.247 3114109 3604562 1 3637503 2008-04-22 09:25:15.027 2008-04-22 09:25:15.027 3604563 3 3114109 2008-04-22 09:25:15.030 2008-05-31 15:44:15.023 3637379 3670137 28 2008-03-22 14:00:47.203 2008-04-18 14:33:56.163 3114132 3604568 6 3114109 2008-04-22 09:56:15.030 2008-06-02 09:29:15.037 3637385 3670143 34 2008-03-21 17:04:00.783 2008-04-18 14:40:30.200 3114109 3604569 1 3637515 2008-04-22 09:58:15.027 2008-04-22 09:58:15.027 3604566 4 3637505 2008-04-22 09:47:15.023 2008-05-31 15:54:15.020 3604567 1 3637511 2008-04-22 09:56:15.027 2008-04-22 09:56:15.027 3637383 3670141 16 2008-03-22 13:50:46.927 2008-03-25 09:04:37.350 3114123 3604556 1 3114109 2008-04-22 09:14:15.027 2008-04-22 09:14:15.027 3637374 3670132 9 2008-03-23 11:17:30.410 2008-04-18 09:34:50.447 3114231 3604557 15 3637488 2008-04-22 09:20:15.020 2008-05-31 15:39:15.027 5374762 5407492 5 2008-07-11 10:37:50.190 2008-07-11 11:14:39.457 5374755 3604554 1 3637488 2008-04-22 09:01:15.023 2008-04-22 09:01:15.023 5374759 5407489 3 2008-07-11 10:37:50.190 2008-07-11 11:12:47.460 5374755 3637372 3670130 27 2008-03-22 14:00:47.203 2008-04-18 14:33:33.490 3114132 3604555 9 3637488 2008-04-22 09:04:15.027 2008-05-21 13:09:15.037 5374760 5407490 4 2008-07-11 10:37:50.190 2008-07-11 11:13:59.753 5374755 3637371 3670129 26 2008-03-22 14:00:47.203 2008-04-18 14:32:57.120 3114132 3604560 7 3114109 2008-04-22 09:20:15.027 2008-05-31 15:44:15.020 3637378 3670136 12 2008-03-23 11:17:30.410 2008-04-18 14:37:57.050 3114231 3604561 5 3114109 2008-04-22 09:21:15.027 2008-05-21 14:03:15.027 3637377 3670135 11 2008-03-23 11:17:30.410 2008-04-18 14:37:19.167 3114231 5374758 5407488 2 2008-07-11 10:37:50.190 2008-07-11 10:41:15.977 5374755 3637376 3670134 10 2008-03-23 11:17:30.410 2008-04-18 14:35:11.230 3114231 3604558 2 3637497 2008-04-22 09:20:15.023 2008-04-22 09:20:15.023 3604559 5 3637497 2008-04-22 09:20:15.023 2008-05-31 15:39:15.030 5374756 5407486 1 2008-07-11 10:37:50.190 2008-07-11 10:37:50.190 5374755 3637365 3670123 21 2008-03-22 14:00:47.203 2008-04-18 14:26:51.763 3114132 3604549 10 3637480 2008-04-22 08:53:15.023 2008-05-31 15:42:15.020 3637366 3670124 22 2008-03-22 14:00:47.203 2008-04-18 14:27:46.370 3114132 3604548 11 3637431 2008-04-22 08:33:15.027 2008-05-31 16:17:15.030 3604547 1 3114109 2008-04-22 08:25:15.043 2008-04-22 08:25:15.043 3637364 3670122 20 2008-03-22 14:00:47.203 2008-04-18 14:24:16.707 3114132 3604546 2 3637433 2008-04-21 09:30:15.023 2008-05-07 14:58:15.030 3604553 5 3114109 2008-04-22 08:59:15.017 2008-05-30 12:46:15.017 3637369 3670127 24 2008-03-22 14:00:47.203 2008-04-18 14:30:12.697 3114132 3637370 3670128 25 2008-03-22 14:00:47.203 2008-04-18 14:31:49.863 3114132 3604552 4 3637480 2008-04-22 08:53:15.050 2008-04-22 08:59:15.020 3637367 3670125 23 2008-03-22 14:00:47.203 2008-04-18 14:29:11.583 3114132 3604551 1 3637480 2008-04-22 08:53:15.047 2008-04-22 08:53:15.047 3604550 1 3114325 2008-04-22 08:53:15.047 2008-04-22 08:53:15.047 3604541 35 3114109 2008-04-18 16:48:15.027 2008-05-31 16:58:15.027 3604540 1 3637431 2008-04-18 16:48:15.023 2008-04-18 16:48:15.023 3604539 1 3637433 2008-04-18 16:48:15.020 2008-04-18 16:48:15.020 3604538 2 3114109 2008-04-18 16:48:15.017 2008-05-07 15:02:15.337 3637361 3670120 19 2008-03-22 14:00:47.203 2008-04-04 15:01:18.350 3114132 3637482 3670237 1 2008-04-22 08:52:21.083 2008-04-22 08:52:21.083 3637480 3637481 3670236 56 2008-03-21 17:04:00.783 2008-04-22 08:31:32.107 3114109 3637471 3670225 54 2008-03-21 17:04:00.783 2008-04-21 17:18:21.947 3114109 4063233 3637523 2008-05-21 13:06:09.987 2008-05-21 13:06:09.987 36143 1 3604592 2 3637515 2008-04-23 15:32:15.023 2008-05-30 09:31:15.077 3637473 3670227 55 2008-03-21 17:04:00.783 2008-04-21 17:19:39.640 3114109 3604593 2 3114389 2008-04-23 15:33:15.023 2008-04-23 15:33:15.023 3637469 3670223 53 2008-03-21 17:04:00.783 2008-04-21 09:47:56.167 3114109 3637463 3670218 51 2008-03-21 17:04:00.783 2008-04-21 09:41:44.463 3114109 5374764 5407494 6 2008-07-11 10:37:50.190 2008-07-11 11:26:13.820 5374755 3604582 18 3637515 2008-04-23 09:06:15.047 2008-05-31 15:26:15.023 3637466 3670220 52 2008-03-21 17:04:00.783 2008-04-21 09:42:28.320 3114109 3637459 3670214 49 2008-03-21 17:04:00.783 2008-04-21 09:36:55.110 3114109 3604581 2 3114109 2008-04-22 17:03:15.067 2008-04-22 17:04:15.017 3637462 3670217 50 2008-03-21 17:04:00.783 2008-04-21 09:37:40.250 3114109 3604575 1 3637523 2008-04-22 10:16:15.027 2008-04-22 10:16:15.027 3637456 3670211 47 2008-03-21 17:04:00.783 2008-04-18 16:54:56.547 3114109 3604574 9 3114109 2008-04-22 10:16:15.027 2008-06-02 09:19:15.037 3637458 3670213 48 2008-03-21 17:04:00.783 2008-04-21 09:32:26.437 3114109 3604576 6 3637523 2008-04-22 10:17:15.027 2008-06-02 09:16:15.077 3604571 5 3114109 2008-04-22 10:02:15.027 2008-05-30 09:31:15.077 3604570 7 3637497 2008-04-22 10:02:15.023 2008-05-31 15:40:15.027 3604573 12 3637511 2008-04-22 10:04:15.023 2008-06-02 09:29:15.023 3604572 2 3637515 2008-04-22 10:02:15.030 2008-05-07 13:17:15.027 5308446 property=value* Comments on the setProperty command: ** You must not have any space around the = sign ** *loc* is again short for localhost ** ** needs to be identified by the serial or analog port. For example, the external CTD is /dev/ttyS4. The single pH sensor can be identified just as '*pH*', but individual pH sensors must be identified as pH0, pH1, pH2, or pH3. h5. Properties common to all SIAM instruments * *sampleSchedule* \- period of sample loop, in seconds.  Actually, this parameter understands a complex syntax that allows all sorts of aperiodic sampling, but a simple integer works best * *powerPolicy* which can be "ALWAYS", "NEVER", or "WHEN_SAMPLING".  I believe all our instruments are set to "ALWAYS" * *powerOnDelaySec -* how long to wait, after the system starts up this service, to power on the instrument.  This allows for power sequencing to manage inrush currents. h5. Properties exclusive to FOCE instruments The FOCE instruments have their own properties. These include: * *motorControl* has *motor1RPM* and *motor2RPM*. These properties allow us to set the speed of each motor on the fly, in RPM * *pH* has *slopes, offsets,* and *correction0* through *correction7*. ** the pH drivers are written with the capability of serving multiple instruments (the original configuration); the default configuration now is one instrument per copy of the driver. **'slopes' and 'offsets' are arrays of doubles. They're set when the instrument software is built, and while they can be changed on the fly (see below), it's inconvenient, since you need to enter all of them at once. ** *correction0..correction7* were created individually to allow them to be easily changed, one at a time. ** The utility script *pH* displays the data from the pH sensors. ]]> 5275678 11863203 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 4620303 1 3637523 2008-05-31 15:17:15.087 2008-05-31 15:17:15.087 4620302 1 3114325 2008-05-31 11:44:15.117 2008-05-31 11:44:15.117 3637439 3670195 46 2008-03-21 17:04:00.783 2008-04-18 16:54:43.303 3114109 3637438 3670194 45 2008-03-21 17:04:00.783 2008-04-18 16:52:09.463 3114109 3637436 3670192 44 2008-03-21 17:04:00.783 2008-04-18 16:48:18.097 3114109 11863210 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 11863211 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 3637434 3670190 43 2008-03-21 17:04:00.783 2008-04-18 16:47:33.480 3114109 4620294 1 3637480 2008-05-30 12:30:15.110 2008-05-30 12:30:15.110 11863208 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 11863209 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 11863206 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 4620292 1 3637497 2008-05-30 09:55:15.027 2008-05-30 09:55:15.027 3637429 3670187 42 2008-03-21 17:04:00.783 2008-04-18 16:45:23.543 3114109 11863207 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 4620293 4 3637503 2008-05-30 09:58:15.027 2008-05-31 15:44:15.017 4620290 1 3114446 2008-05-29 14:29:15.017 2008-05-29 14:29:15.017 11863204 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 3637427 3670185 41 2008-03-21 17:04:00.783 2008-04-18 16:43:20.057 3114109 11863205 9371938 2010-04-14 09:36:40.327 2010-04-14 09:36:40.327 3637425 3670183 40 2008-03-21 17:04:00.783 2008-04-18 16:43:06.707 3114109 4620289 2 3114231 2008-05-29 09:52:15.017 2008-05-29 09:52:15.017 3637424 3670182 39 2008-03-21 17:04:00.783 2008-04-18 16:30:19.070 3114109 3637422 3670180 38 2008-03-21 17:04:00.783 2008-04-18 16:02:49.620 3114109 3637420 3670178 4 2008-04-15 10:13:33.937 2008-04-18 16:15:34.467 3637328 3704636 3114238 2008-04-18 15:59:13.457 2008-04-18 15:59:13.457 5407485 5374755 3704654 3114242 2008-04-18 16:11:29.117 2008-04-18 16:11:29.117 3704653 3114242 2008-04-18 16:11:29.117 2008-04-18 16:11:29.117 3704650 3637401 2008-04-18 16:07:53.163 2008-04-18 16:07:53.163 3704649 3637401 2008-04-18 16:07:53.163 2008-04-18 16:07:53.163 16416903 16449666 7 2008-03-24 11:31:02.937 2011-01-10 09:45:32.977 3114325 9439809 5275678 2009-03-17 14:47:36.160 2009-03-17 14:47:36.160 9439808 5275678 2009-03-17 14:47:36.160 2009-03-17 14:47:36.160 16416887 16449650 13 2008-10-16 14:24:15.190 2010-04-13 09:49:09.173 6259359 4554779 3114231 2008-05-29 09:54:04.157 2008-05-29 09:54:04.157 16416889 16449652 14 2008-10-16 14:24:15.190 2011-03-22 17:16:18.983 6259359 4554780 3114231 2008-05-29 09:54:04.157 2008-05-29 09:54:04.157 4554781 3114231 2008-05-29 09:54:04.157 2008-05-29 09:54:04.157 9896469 3114389 2009-04-22 10:00:10.610 2009-04-22 10:00:10.610 9896468 3114389 2009-04-22 10:00:10.610 2009-04-22 10:00:10.610 9797770 9830539 23 2009-02-26 13:59:15.167 2009-04-15 14:00:48.210 9371938 9797768 9830537 27 2008-03-27 08:13:59.440 2009-02-25 16:44:33.017 3114389 9896470 3114389 2009-04-22 10:00:10.610 2009-04-22 10:00:10.610 3670864 3638124 7766131 7798895 15 2008-10-16 15:14:27.940 2008-11-05 11:18:05.237 6259368 3704600 3114123 2008-04-18 14:57:50.253 2008-04-18 14:57:50.253 3704601 3114123 2008-04-18 14:57:50.253 2008-04-18 14:57:50.253 9404658 devel->main', and add: ** autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * 'Not Installed Packages->net->main, add ntp and ntpdate. Install. (Added 23may2008, rah) ** Update /etc/ntp.conf to point to MBARI time servers.  You can get it [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/ntp.conf] * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** apt-get install ethtool net-tools (Added 9jun2008, rah) h5. 4) Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. 5) Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11 (or S19 for two serial boards). * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: * /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. -6) NTP- -On the deployed system, NTP wasn't peering with the time servers, as evidenced by 'ntpq \-p'.  This time around, it seems to be working fine.  But if you have this problem, you need to install NTP later in the init cycle, as follows:- * - Run 'update-rc.d \-f ntp remove'- * -Add '/etc/init.d/ntp start' to /etc/rc.local- h5. 6) NTP and DataTurbine 3Feb2010, rah - I scrapped point 6 above and added the following to foce5 (recovered from Revelle deployment of Aug2009) * Run 'update-rc.d ntp defaults 97' * Run 'update-rc.d startDataTurbine defaults 98' startDataTurbine is a script I created in /etc/init.d that looks like: {code} #!/bin/sh -e # # Start DataTurbine # PATH=.:/sbin:/bin:/usr/sbin:/usr/bin export RBNB_HOME=/usr/local/RBNB/V3.2B2 export JAVA_HOME=/usr/java/jdk1.5.0_15 JARFILE=rbnb.jar test -f $RBNB_HOME/bin/$JARFILE || exit 5 cd $RBNB_HOME/apache-tomcat-5.5.12/bin startup.sh &> ../../apache.log sleep 3 cd $RBNB_HOME $JAVA_HOME/bin/java -jar bin/$JARFILE -a localhost:3333 -m 10,1000,200000 &> dat aTurbine.log & exit 0 {code} [|FOCE:Installing SIAM and FOCE on FOCE Stack] *[*You're now ready to install Java and SIAM.*|FOCE:Installing SIAM and FOCE on FOCE Stack]*[|FOCE:Installing SIAM and FOCE on FOCE Stack]]]> 9371909 3704598 3114123 2008-04-18 14:57:50.253 2008-04-18 14:57:50.253 3704599 3114123 2008-04-18 14:57:50.253 2008-04-18 14:57:50.253 3704624 3114136 2008-04-18 15:25:52.697 2008-04-18 15:25:52.697 3704621 3114136 2008-04-18 15:25:52.697 2008-04-18 15:25:52.697 3704623 3114136 2008-04-18 15:25:52.697 2008-04-18 15:25:52.697 3704622 3114136 2008-04-18 15:25:52.697 2008-04-18 15:25:52.697 9896466 3114389 2009-04-22 10:00:10.610 2009-04-22 10:00:10.610 9797772 9830541 25 2009-02-26 13:59:15.167 2009-04-22 10:23:44.443 9371938 9896467 3114389 2009-04-22 10:00:10.610 2009-04-22 10:00:10.610 9797771 9830540 24 2009-02-26 13:59:15.167 2009-04-22 10:22:24.940 9371938 9896465 3114389 2009-04-22 10:00:10.610 2009-04-22 10:00:10.610 3114113 3179595 2 2008-03-21 17:04:00.783 2008-03-21 17:10:16.420 3114109 3114111 3179593 1 2008-03-21 17:04:00.783 2008-03-21 17:04:00.783 3114109 3114118 3179600 5 2008-03-21 17:04:00.783 2008-03-21 17:28:11.747 3114109 3114117 3179599 4 2008-03-21 17:04:00.783 2008-03-21 17:23:11.563 3114109 3114115 3179597 3 2008-03-21 17:04:00.783 2008-03-21 17:11:16.160 3114109 3114121 3179602 6 2008-03-21 17:04:00.783 2008-03-21 17:28:38.457 3114109 5275680 5308448 1 2008-06-11 11:07:52.247 2008-06-11 11:07:52.247 5275678 3706479 3637480 2008-04-22 08:58:33.517 2008-04-22 08:58:33.517 3706482 3637480 2008-04-22 08:58:33.517 2008-04-22 08:58:33.517 3706480 3637480 2008-04-22 08:58:33.517 2008-04-22 08:58:33.517 3706481 3637480 2008-04-22 08:58:33.517 2008-04-22 08:58:33.517 3211518 3145737 2008-03-24 11:34:10.633 2008-03-24 11:34:10.633 3114140 3179621 9 2008-03-21 17:04:00.783 2008-03-22 13:57:03.677 3114109 3211517 3145737 2008-03-24 11:34:10.620 2008-03-24 11:34:10.620 3211520 3145737 2008-03-24 11:34:10.653 2008-03-24 11:34:10.653 3114142 3179623 11 2008-03-21 17:04:00.783 2008-03-22 14:05:11.930 3114109 3211519 3145737 2008-03-24 11:34:10.643 2008-03-24 11:34:10.643 9797729 9830498 22 2009-02-26 13:59:15.167 2009-04-14 16:38:12.063 9371938 3114141 3179622 10 2008-03-21 17:04:00.783 2008-03-22 14:04:32.503 3114109 3211522 3145737 2008-03-24 11:34:10.673 2008-03-24 11:34:10.673 3114144 3179625 13 2008-03-21 17:04:00.783 2008-03-22 14:06:09.737 3114109 5275655 5308422 2 2008-06-09 14:42:02.883 2008-06-09 14:46:57.207 4915268 3211521 3145737 2008-03-24 11:34:10.663 2008-03-24 11:34:10.663 3114143 3179624 12 2008-03-21 17:04:00.783 2008-03-22 14:05:39.917 3114109 3114145 3179626 14 2008-03-21 17:04:00.783 2008-03-22 14:06:36.177 3114109 3211510 3145737 2008-03-24 11:34:10.080 2008-03-24 11:34:10.080 3211509 3145737 2008-03-24 11:34:10.070 2008-03-24 11:34:10.070 3211512 3145737 2008-03-24 11:34:10.100 2008-03-24 11:34:10.100 3211511 3145737 2008-03-24 11:34:10.090 2008-03-24 11:34:10.090 3211514 3145737 2008-03-24 11:34:10.590 2008-03-24 11:34:10.590 3211513 3145737 2008-03-24 11:34:10.580 2008-03-24 11:34:10.580 3114154 3179634 1 2008-03-22 14:02:36.787 2008-03-22 14:02:36.787 3114136 3211516 3145737 2008-03-24 11:34:10.610 2008-03-24 11:34:10.610 3211515 3145737 2008-03-24 11:34:10.600 2008-03-24 11:34:10.600 3114126 3179606 7 2008-03-21 17:04:00.783 2008-03-22 13:49:36.057 3114109 3114127 3179607 8 2008-03-21 17:04:00.783 2008-03-22 13:56:23.343 3114109 3211492 3145737 2008-03-24 11:34:09.897 2008-03-24 11:34:09.897 3211491 3145737 2008-03-24 11:34:09.887 2008-03-24 11:34:09.887 3211490 3145737 2008-03-24 11:34:09.877 2008-03-24 11:34:09.877 3211489 3145737 2008-03-24 11:34:09.870 2008-03-24 11:34:09.870 3211488 3145737 2008-03-24 11:34:09.860 2008-03-24 11:34:09.860 3211487 3145737 2008-03-24 11:34:09.850 2008-03-24 11:34:09.850 3211486 3145737 2008-03-24 11:34:09.840 2008-03-24 11:34:09.840 3211485 3145737 2008-03-24 11:34:09.830 2008-03-24 11:34:09.830 3211484 3145737 2008-03-24 11:34:09.820 2008-03-24 11:34:09.820 3211483 3145737 2008-03-24 11:34:09.810 2008-03-24 11:34:09.810 3211482 3145737 2008-03-24 11:33:24.170 2008-03-24 11:33:24.170 3211481 3145737 2008-03-24 11:33:04.520 2008-03-24 11:33:04.520 3211480 3145737 2008-03-24 11:32:59.743 2008-03-24 11:32:59.743 10455685 10354905 2009-06-07 15:06:33.340 2009-06-07 15:06:33.340 5341190 4915268 2008-06-10 10:29:39.260 2008-06-10 10:29:39.260 10455684 10354905 2009-06-07 15:06:33.340 2009-06-07 15:06:33.340 3211477 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3114161 3179641 5 2008-03-22 14:02:36.787 2008-03-22 14:51:03.960 3114136 10455682 10354905 2009-06-07 15:06:33.340 2009-06-07 15:06:33.340 3211507 3145737 2008-03-24 11:34:10.050 2008-03-24 11:34:10.050 10455683 10354905 2009-06-07 15:06:33.340 2009-06-07 15:06:33.340 3211508 3145737 2008-03-24 11:34:10.060 2008-03-24 11:34:10.060 3114159 3179639 4 2008-03-22 14:02:36.787 2008-03-22 14:37:02.507 3114136 3211505 3145737 2008-03-24 11:34:10.030 2008-03-24 11:34:10.030 3211506 3145737 2008-03-24 11:34:10.040 2008-03-24 11:34:10.040 3114157 3179637 3 2008-03-22 14:02:36.787 2008-03-22 14:33:14.693 3114136 3211503 3145737 2008-03-24 11:34:10.010 2008-03-24 11:34:10.010 3211504 3145737 2008-03-24 11:34:10.020 2008-03-24 11:34:10.020 3114155 3179635 2 2008-03-22 14:02:36.787 2008-03-22 14:32:47.783 3114136 3211501 3145737 2008-03-24 11:34:09.987 2008-03-24 11:34:09.987 3211502 3145737 2008-03-24 11:34:09.997 2008-03-24 11:34:09.997 3211499 3145737 2008-03-24 11:34:09.967 2008-03-24 11:34:09.967 3211500 3145737 2008-03-24 11:34:09.977 2008-03-24 11:34:09.977 3114167 3179647 8 2008-03-22 14:02:36.787 2008-03-22 14:55:40.653 3114136 3211497 3145737 2008-03-24 11:34:09.947 2008-03-24 11:34:09.947 3114165 3179645 7 2008-03-22 14:02:36.787 2008-03-22 14:54:34.307 3114136 3211495 3145737 2008-03-24 11:34:09.927 2008-03-24 11:34:09.927 3211496 3145737 2008-03-24 11:34:09.937 2008-03-24 11:34:09.937 3114163 3179643 6 2008-03-22 14:02:36.787 2008-03-22 14:53:10.887 3114136 3211493 3145737 2008-03-24 11:34:09.907 2008-03-24 11:34:09.907 3211494 3145737 2008-03-24 11:34:09.917 2008-03-24 11:34:09.917 3114208 3179688 3 2008-03-22 14:00:47.203 2008-03-22 16:14:46.933 3114132 3114207 3179687 2 2008-03-22 14:00:47.203 2008-03-22 16:09:56.980 3114132 3114210 3179690 4 2008-03-22 14:00:47.203 2008-03-22 16:15:30.637 3114132 3114205 3179685 1 2008-03-22 14:00:47.203 2008-03-22 14:00:47.203 3114132 3114215 3179695 7 2008-03-22 14:00:47.203 2008-03-22 16:22:18.590 3114132 16416842 16449606 17 2008-10-16 15:14:27.940 2009-09-02 10:57:06.017 6259368 3114217 3179697 8 2008-03-22 14:00:47.203 2008-03-22 16:22:32.227 3114132 3114212 3179692 5 2008-03-22 14:00:47.203 2008-03-22 16:20:33.353 3114132 9797672 9830441 21 2009-02-26 13:59:15.167 2009-04-14 16:36:42.003 9371938 9797671 9830440 20 2009-02-26 13:59:15.167 2009-03-17 15:54:45.290 9371938 3114214 3179694 6 2008-03-22 14:00:47.203 2008-03-22 16:21:35.237 3114132 3211473 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211474 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211475 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211476 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211469 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211470 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211471 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211472 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211465 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211466 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211467 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211468 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3211464 3145737 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3114228 3179707 15 2008-03-21 17:04:00.783 2008-03-22 14:07:10.720 3114109 3114232 3179710 1 2008-03-23 11:17:30.410 2008-03-23 11:17:30.410 3114231 3114234 3179712 2 2008-03-23 11:17:30.410 2008-03-23 11:18:20.453 3114231 3114220 3179700 10 2008-03-22 14:00:47.203 2008-03-22 16:37:10.553 3114132 3114219 3179699 9 2008-03-22 14:00:47.203 2008-03-22 16:24:59.800 3114132 3114222 3179702 11 2008-03-22 14:00:47.203 2008-03-22 16:37:43.270 3114132 3114224 3179704 13 2008-03-22 14:00:47.203 2008-03-22 16:45:59.790 3114132 3114223 3179703 12 2008-03-22 14:00:47.203 2008-03-22 16:45:36.777 3114132 3114226 3179706 15 2008-03-22 14:00:47.203 2008-03-22 16:46:48.563 3114132 3114225 3179705 14 2008-03-22 14:00:47.203 2008-03-22 16:46:32.027 3114132 3114244 3179720 1 2008-03-23 11:21:57.880 2008-03-23 11:21:57.880 3114242 3114246 3179722 1 2008-03-22 13:57:49.963 2008-03-22 13:57:49.963 3114128 3114247 3179723 2 2008-03-22 13:57:49.963 2008-03-23 11:57:50.993 3114128 3114249 3179725 3 2008-03-22 13:57:49.963 2008-03-23 11:58:26.700 3114128 7798833 7766069 3114235 3179713 16 2008-03-21 17:04:00.783 2008-03-23 11:17:06.640 3114109 3114239 3179716 1 2008-03-23 11:20:18.790 2008-03-23 11:20:18.790 3114238 3114240 3179717 2 2008-03-23 11:20:18.790 2008-03-23 11:20:42.883 3114238 9372008 9404756 1 2009-03-03 12:53:06.193 2009-03-03 12:53:06.193 9372007 3114262 3179737 8 2008-03-23 11:21:57.880 2008-03-23 12:10:26.677 3114242 9371948 9404697 4 2009-02-26 13:59:15.167 2009-02-26 14:35:03.047 9371938 3114261 3179736 7 2008-03-23 11:21:57.880 2008-03-23 12:10:15.030 3114242 3114260 3179735 6 2008-03-23 11:21:57.880 2008-03-23 12:10:07.297 3114242 9371950 9404699 6 2009-02-26 13:59:15.167 2009-02-26 14:36:49.880 9371938 3114259 3179734 5 2008-03-23 11:21:57.880 2008-03-23 12:09:53.160 3114242 9371949 9404698 5 2009-02-26 13:59:15.167 2009-02-26 14:36:04.187 9371938 9371952 9404701 7 2009-02-26 13:59:15.167 2009-02-26 14:37:12.033 9371938 3114266 3179741 19 2008-03-21 17:04:00.783 2008-03-23 12:08:02.743 3114109 3114264 3179739 10 2008-03-23 11:21:57.880 2008-03-23 12:10:46.167 3114242 9371954 9404703 8 2009-02-26 13:59:15.167 2009-02-26 14:41:30.600 9371938 3114263 3179738 9 2008-03-23 11:21:57.880 2008-03-23 12:10:33.523 3114242 3114254 3179729 18 2008-03-21 17:04:00.783 2008-03-23 12:07:11.567 3114109 9371955 9404704 9 2009-02-26 13:59:15.167 2009-02-26 14:43:13.150 9371938 3114253 3179728 17 2008-03-21 17:04:00.783 2008-03-23 11:20:00.497 3114109 3114251 3179727 4 2008-03-22 13:57:49.963 2008-03-23 12:00:52.700 3114128 3114258 3179733 4 2008-03-23 11:21:57.880 2008-03-23 12:09:29.987 3114242 3114257 3179732 3 2008-03-23 11:21:57.880 2008-03-23 12:09:00.870 3114242 3114256 3179731 2 2008-03-23 11:21:57.880 2008-03-23 11:34:58.630 3114242 3114278 3179753 6 2008-03-22 13:50:46.927 2008-03-23 12:34:28.180 3114123 3114275 3179750 4 2008-03-22 13:50:46.927 2008-03-23 12:29:33.130 3114123 3114276 3179751 5 2008-03-22 13:50:46.927 2008-03-23 12:33:53.527 3114123 3114282 3179757 8 2008-03-22 13:50:46.927 2008-03-23 12:38:17.593 3114123 3114280 3179755 7 2008-03-22 13:50:46.927 2008-03-23 12:36:07.383 3114123 3114270 3179745 1 2008-03-22 13:50:46.927 2008-03-22 13:50:46.927 3114123 3114268 3179743 20 2008-03-21 17:04:00.783 2008-03-23 12:17:34.497 3114109 3114273 3179748 3 2008-03-22 13:50:46.927 2008-03-23 12:29:17.580 3114123 3114272 3179747 2 2008-03-22 13:50:46.927 2008-03-23 12:27:04.933 3114123 3114296 3179771 11 2008-03-22 14:02:36.787 2008-03-23 12:56:41.970 3114136 3114298 3179773 12 2008-03-22 14:02:36.787 2008-03-23 12:59:58.197 3114136 9371919 9404668 5 2009-02-25 16:45:05.063 2009-02-25 17:18:27.350 9371909 3114292 3179767 9 2008-03-22 14:02:36.787 2008-03-22 14:58:14.797 3114136 3114291 3179766 14 2008-03-22 13:50:46.927 2008-03-23 12:52:44.003 3114123 9371917 9404666 4 2009-02-25 16:45:05.063 2009-02-25 17:16:09.327 9371909 3114294 3179769 10 2008-03-22 14:02:36.787 2008-03-23 12:54:41.497 3114136 9371915 9404664 3 2009-02-25 16:45:05.063 2009-02-25 17:00:08.820 9371909 3114288 3179763 11 2008-03-22 13:50:46.927 2008-03-23 12:49:29.480 3114123 3114290 3179765 13 2008-03-22 13:50:46.927 2008-03-23 12:51:59.597 3114123 3114289 3179764 12 2008-03-22 13:50:46.927 2008-03-23 12:51:08.923 3114123 10388828 10356102 3114284 3179759 9 2008-03-22 13:50:46.927 2008-03-23 12:39:53.157 3114123 3114286 3179761 10 2008-03-22 13:50:46.927 2008-03-23 12:40:53.867 3114123 3114311 3179786 19 2008-03-22 14:02:36.787 2008-03-23 13:20:15.567 3114136 3114313 3179788 20 2008-03-22 14:02:36.787 2008-03-23 13:20:50.043 3114136 3114314 3179789 21 2008-03-22 14:02:36.787 2008-03-23 13:22:40.813 3114136 9371936 9404686 6 2009-02-25 16:45:05.063 2009-02-25 17:21:56.040 9371909 3114308 3179783 17 2008-03-22 14:02:36.787 2008-03-23 13:18:29.307 3114136 3114310 3179785 18 2008-03-22 14:02:36.787 2008-03-23 13:19:19.613 3114136 3114304 3179779 15 2008-03-22 14:02:36.787 2008-03-23 13:11:12.600 3114136 9371946 9404695 3 2009-02-26 13:59:15.167 2009-02-26 14:29:36.203 9371938 3114306 3179781 16 2008-03-22 14:02:36.787 2008-03-23 13:17:10.420 3114136 9371944 9404693 2 2009-02-26 13:59:15.167 2009-02-26 14:09:00.727 9371938 3114300 3179775 13 2008-03-22 14:02:36.787 2008-03-23 13:03:33.387 3114136 9371942 9404691 1 2009-02-26 13:59:15.167 2009-02-26 13:59:15.167 9371938 3114302 3179777 14 2008-03-22 14:02:36.787 2008-03-23 13:07:00.847 3114136 9371940 9404689 7 2009-02-25 16:45:05.063 2009-02-26 13:58:52.970 9371909 3114328 3179802 2 2008-03-24 11:31:02.937 2008-03-24 11:43:45.830 3114325 3114327 3179801 1 2008-03-24 11:31:02.937 2008-03-24 11:31:02.937 3114325 3670634 3637883 3114318 3179793 23 2008-03-22 14:02:36.787 2008-03-23 13:24:10.230 3114136 3114316 3179791 22 2008-03-22 14:02:36.787 2008-03-23 13:23:18.357 3114136 3670655 3637905 3708686 3638124 2008-05-19 16:51:44.483 2008-05-19 16:51:44.483 3670652 3637901 9371911 9404660 1 2009-02-25 16:45:05.063 2009-02-25 16:45:05.063 9371909 9371913 9404662 2 2009-02-25 16:45:05.063 2009-02-25 16:49:49.570 9371909 9371907 9404656 26 2008-03-27 08:13:59.440 2008-07-07 17:09:13.240 3114389 3670665 3637915 3670663 3637913 3670667 3637917 3114361 3179834 21 2008-03-21 17:04:00.783 2008-03-23 12:18:39.547 3114109 3114362 3179835 22 2008-03-21 17:04:00.783 2008-03-25 09:04:37.003 3114109 4030479 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 3114364 3179837 23 2008-03-21 17:04:00.783 2008-03-25 09:04:37.190 3114109 3114363 3179836 15 2008-03-22 13:50:46.927 2008-03-23 12:52:57.860 3114123 4030478 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 9404687 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. 6) Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. 7) Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. 8) Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml h5. Configure SIAM pieces * cp properties/siamPort.cfg.foce properties/siamPort.cfg (i) You may have to edit the siamPort.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, confirm the top-level Makefile points to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce * make siamjar * make siamif.jar (Note - this is used primarily by the GUI) * make install  (Note - this unjars siam.jar into $CODEBASE, which is necessary for the GUI) {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. 9) Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps \-ef \| grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & h2. For more information on running FOCE, see this [user documentation|FOCE:User Documentation].]]> 9371938 4030477 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 3114366 3179839 24 2008-03-21 17:04:00.783 2008-03-25 09:04:37.407 3114109 3114365 3179838 5 2008-03-22 13:57:49.963 2008-03-23 12:05:33.950 3114128 4030483 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 3114368 3179841 25 2008-03-21 17:04:00.783 2008-03-25 09:04:37.567 3114109 3114367 3179840 16 2008-03-22 14:00:47.203 2008-03-22 16:47:22.083 3114132 4030482 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 4030481 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 3114370 3179843 26 2008-03-21 17:04:00.783 2008-03-25 09:04:37.643 3114109 3114369 3179842 24 2008-03-22 14:02:36.787 2008-03-23 13:25:44.903 3114136 4030480 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 4030471 3637901 2008-05-21 13:07:05.913 2008-05-21 13:07:05.913 3114372 3179845 27 2008-03-21 17:04:00.783 2008-03-25 09:04:37.733 3114109 3114371 3179844 3 2008-03-23 11:17:30.410 2008-03-23 11:19:01.037 3114231 3114374 3179847 28 2008-03-21 17:04:00.783 2008-03-25 09:04:37.827 3114109 3114373 3179846 3 2008-03-23 11:20:18.790 2008-03-23 11:21:13.240 3114238 3114376 3179849 29 2008-03-21 17:04:00.783 2008-03-25 09:04:37.870 3114109 3114375 3179848 11 2008-03-23 11:21:57.880 2008-03-23 12:11:14.923 3114242 4030472 3637901 2008-05-21 13:07:05.913 2008-05-21 13:07:05.913 3114377 3179850 30 2008-03-21 17:04:00.783 2008-03-25 09:04:38.453 3114109 10354912 10387677 4 2009-06-06 11:55:49.357 2009-06-06 21:13:57.103 10354905 4030484 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 10354911 10387676 3 2009-06-06 11:55:49.357 2009-06-06 20:28:46.667 10354905 4030485 3637488 2008-05-21 13:08:56.773 2008-05-21 13:08:56.773 10354908 10387673 1 2009-06-06 11:55:49.357 2009-06-06 11:55:49.357 10354905 3114393 3179865 2 2008-03-27 08:13:59.440 2008-03-27 08:23:56.873 3114389 10354910 10387675 2 2009-06-06 11:55:49.357 2009-06-06 20:22:32.940 10354905 3114391 3179863 1 2008-03-27 08:13:59.440 2008-03-27 08:13:59.440 3114389 4030490 3637328 2008-05-22 11:17:22.240 2008-05-22 11:17:22.240 4030491 3637328 2008-05-22 11:17:22.240 2008-05-22 11:17:22.240 3114398 3179870 5 2008-03-27 08:13:59.440 2008-03-27 10:31:52.353 3114389 3114397 3179869 4 2008-03-27 08:13:59.440 2008-03-27 10:12:50.400 3114389 3114395 3179867 3 2008-03-27 08:13:59.440 2008-03-27 08:36:07.987 3114389 3114402 3179874 7 2008-03-27 08:13:59.440 2008-03-27 10:44:21.740 3114389 3114400 3179872 6 2008-03-27 08:13:59.440 2008-03-27 10:35:30.063 3114389 3114406 3179878 9 2008-03-27 08:13:59.440 2008-03-27 10:51:19.603 3114389 3114404 3179876 8 2008-03-27 08:13:59.440 2008-03-27 10:48:19.560 3114389 3114408 3179880 10 2008-03-27 08:13:59.440 2008-03-27 10:53:59.137 3114389 4292610 3114132 2008-05-28 13:03:21.227 2008-05-28 13:03:21.227 3114415 3179887 12 2008-03-27 08:13:59.440 2008-03-27 11:46:12.597 3114389 4292611 3114132 2008-05-28 13:03:21.227 2008-05-28 13:03:21.227 4292609 3114132 2008-05-28 13:03:21.223 2008-05-28 13:03:21.223 12615739 3145737 2010-05-21 10:30:14.043 2010-05-21 10:30:14.043 3114413 3179885 11 2008-03-27 08:13:59.440 2008-03-27 11:26:32.507 3114389 4685825 4653058 4653057 3114109 12615738 3145737 2010-05-21 10:30:00.540 2010-05-21 10:30:00.540 3114425 3179897 14 2008-03-27 08:13:59.440 2008-03-27 14:02:28.120 3114389 9404755 9372007 15630866 15663620 6 2008-03-24 11:31:02.937 2011-01-10 09:44:47.357 3114325 15630865 15663619 5 2008-03-24 11:31:02.937 2010-05-21 10:29:26.453 3114325 3114422 3179894 13 2008-03-27 08:13:59.440 2008-03-27 11:54:03.393 3114389 3114432 3179904 17 2008-03-27 08:13:59.440 2008-03-28 13:36:06.770 3114389 3706657 3637515 2008-04-22 10:01:55.177 2008-04-22 10:01:55.177 3706656 3637515 2008-04-22 10:01:55.177 2008-04-22 10:01:55.177 3706659 3637515 2008-04-22 10:01:55.177 2008-04-22 10:01:55.177 3706658 3637515 2008-04-22 10:01:55.177 2008-04-22 10:01:55.177 3114427 3179899 15 2008-03-27 08:13:59.440 2008-03-27 17:09:13.733 3114389 3114430 3179902 16 2008-03-27 08:13:59.440 2008-03-28 13:20:44.177 3114389 3706655 3637515 2008-04-22 10:01:55.177 2008-04-22 10:01:55.177 3114439 3179911 4 2008-03-23 11:17:30.410 2008-03-25 09:04:37.770 3114231 3114441 3179913 17 2008-03-22 14:00:47.203 2008-03-25 09:04:37.600 3114132 3114435 3179907 18 2008-03-27 08:13:59.440 2008-03-28 14:50:51.147 3114389 3114437 3179909 19 2008-03-27 08:13:59.440 2008-03-29 16:27:51.347 3114389 4555233 3637497 2008-05-31 15:36:40.837 2008-05-31 15:36:40.837 3114450 3179922 2 2008-04-01 09:42:41.390 2008-04-01 09:47:37.210 3114446 4555232 3637497 2008-05-31 15:36:40.837 2008-05-31 15:36:40.837 4555235 3637497 2008-05-31 15:36:40.837 2008-05-31 15:36:40.837 3114448 3179920 1 2008-04-01 09:42:41.390 2008-04-01 09:42:41.390 3114446 4555234 3637497 2008-05-31 15:36:40.837 2008-05-31 15:36:40.837 3114445 3179917 26 2008-03-22 14:02:36.787 2008-04-01 09:35:01.527 3114136 4555231 3637497 2008-05-31 15:36:40.837 2008-05-31 15:36:40.837 3114444 3179916 25 2008-03-22 14:02:36.787 2008-03-25 09:04:37.687 3114136 9372012 9404760 2 2009-03-03 12:53:06.193 2009-03-03 12:53:28.880 9372007 3114451 3179923 3 2008-04-01 09:42:41.390 2008-04-01 09:51:20.107 3114446 4555248 3637511 2008-06-02 09:28:15.960 2008-06-02 09:28:15.960 4555249 3637511 2008-06-02 09:28:15.960 2008-06-02 09:28:15.960 4555250 3637511 2008-06-02 09:28:15.960 2008-06-02 09:28:15.960 3114464 3179936 5 2008-03-23 11:17:30.410 2008-04-01 08:23:35.330 3114231 9372041 9404787 10 2009-02-26 13:59:15.167 2009-02-26 14:55:23.937 9371938 4555244 3637523 2008-06-02 09:18:21.040 2008-06-02 09:18:21.040 4555245 3637511 2008-06-02 09:28:15.960 2008-06-02 09:28:15.960 4555246 3637511 2008-06-02 09:28:15.960 2008-06-02 09:28:15.960 4555247 3637511 2008-06-02 09:28:15.960 2008-06-02 09:28:15.960 4555240 3637505 2008-05-31 15:53:20.940 2008-05-31 15:53:20.940 4555241 3637505 2008-05-31 15:53:20.940 2008-05-31 15:53:20.940 4555242 3637523 2008-06-02 09:18:21.040 2008-06-02 09:18:21.040 3114471 3179943 4 2008-04-01 09:42:41.390 2008-04-01 09:53:46.777 3114446 4555243 3637523 2008-06-02 09:18:21.040 2008-06-02 09:18:21.040 4555236 3637505 2008-05-31 15:53:20.940 2008-05-31 15:53:20.940 4555237 3637505 2008-05-31 15:53:20.940 2008-05-31 15:53:20.940 3114469 3179941 7 2008-03-23 11:17:30.410 2008-04-01 14:35:28.173 3114231 4555238 3637505 2008-05-31 15:53:20.940 2008-05-31 15:53:20.940 4555239 3637505 2008-05-31 15:53:20.940 2008-05-31 15:53:20.940 3114467 3179939 6 2008-03-23 11:17:30.410 2008-04-01 13:31:28.767 3114231 9372269 9405005 19 2009-02-26 13:59:15.167 2009-03-16 16:25:07.300 9371938 19041336 19074022 5 2012-11-14 18:40:38.063 2012-11-14 18:54:58.917 19041215 9306149 1 3114325 2009-03-16 14:46:15.080 2009-03-16 14:46:15.080 6226571 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.162 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.162.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node, set the IP address to 134.89.42.127.  For connection to the WNS (wet-node simulator), change it to 134.89.52.127. h6. Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)".  You can use that to associate the Windows COMx serial port names with the PortServer port numbers.  I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: * The first serial port (PortServer Port 1) is connected to the Insite Camera.  You can see from the Device Manager that this is mapped to COM2. * The second serial port (PortServer Port 2) is connected to the PC/104 stack.  In this example, this is COM15.  This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. * The third and fourth serial ports are unused (I think). h6.]]> 6259368 3114501 3179971 18 2008-03-22 14:00:47.203 2008-04-01 08:33:16.550 3114132 3670278 3637523 9798287 9831040 28 2009-02-26 13:59:15.167 2009-05-06 12:54:56.287 9371938 9798285 9831038 27 2009-02-26 13:59:15.167 2009-05-06 12:45:07.623 9371938 6226525 &1 \| tee focetar.out # Shut down the system.  Remove the new drive and remove the slave jumper.]]> 6259322 9798307 9831060 29 2009-02-26 13:59:15.167 2009-05-06 12:56:34.343 9371938 19234825 19202054 19040558 2012-08-16 15:51:50.770 2012-08-16 15:51:50.770 5013698 3637503 2008-06-06 06:48:58.163 2008-06-06 06:48:58.163 19234826 19202055 19040558 2012-08-16 15:51:50.777 2012-08-16 15:51:50.777 19234827 19202056 19040558 2012-08-16 15:51:50.777 2012-08-16 15:51:50.777 5013697 3637503 2008-06-06 06:48:58.163 2008-06-06 06:48:58.163 9798273 9831026 10 2009-02-25 16:45:05.063 2009-03-16 14:56:42.337 9371909 6226562 6259359 9798282 9831035 26 2009-02-26 13:59:15.167 2009-04-22 10:24:05.277 9371938 9798275 9831028 11 2009-02-25 16:45:05.063 2009-05-06 12:37:27.197 9371909 9372211 9404949 4 2008-06-11 11:07:52.247 2008-06-12 14:30:28.527 5275678 9372248 9404985 14 2009-02-26 13:59:15.167 2009-03-16 14:25:37.307 9371938 9372247 9404984 13 2009-02-26 13:59:15.167 2009-03-16 14:20:48.777 9371938 9372250 9404987 15 2009-02-26 13:59:15.167 2009-03-16 14:27:43.477 9371938 9372243 9404980 11 2009-02-26 13:59:15.167 2009-03-04 09:29:35.653 9371938 9372245 9404982 12 2009-02-26 13:59:15.167 2009-03-16 14:07:11.427 9371938 6226496 6259287 9372265 9405001 5 2008-06-11 11:07:52.247 2009-03-11 16:59:07.617 5275678 9372260 9404996 18 2009-02-26 13:59:15.167 2009-03-16 14:44:52.383 9371938 9372255 9404991 17 2009-02-26 13:59:15.167 2009-03-16 14:44:08.933 9371938 9372257 9404993 8 2009-02-25 16:45:05.063 2009-02-26 14:00:38.600 9371909 9372258 9404994 9 2009-02-25 16:45:05.063 2009-03-16 14:55:28.720 9371909 9372253 9404989 16 2009-02-26 13:59:15.167 2009-03-16 14:37:45.357 9371938 5507381 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507380 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 9798441 9831192 10 2008-10-16 14:24:15.190 2008-11-05 11:19:07.630 6259359 5507383 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507382 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507385 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507384 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507387 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507386 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507389 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507388 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507391 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507390 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507393 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507392 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507395 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507394 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507396 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507397 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507398 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507399 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 19300573 3145737 2012-06-18 17:10:47.490 2012-06-18 17:10:47.490 5507400 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507401 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507402 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507403 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507404 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 19041620 19074301 21 2012-08-16 17:27:30.563 2013-01-11 16:31:03.370 19040630 5507405 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 19041619 19074300 20 2012-08-16 17:27:30.563 2012-09-10 15:58:33.980 19040630 5507406 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 5507407 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 19041621 19074302 22 2012-08-16 17:27:30.563 2013-01-11 16:31:48.113 19040630 5507408 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 19041624 19074305 24 2012-08-16 17:27:30.563 2013-01-11 16:33:17.123 19040630 5507409 3114109 2008-07-01 13:50:12.377 2008-07-01 13:50:12.377 19041623 19074304 23 2012-08-16 17:27:30.563 2013-01-11 16:32:33.567 19040630 16515630 6259359 2011-03-22 17:25:55.840 2011-03-22 17:25:55.840 16515631 6259359 2011-03-22 17:25:55.840 2011-03-22 17:25:55.840 3670090 3637328 16515632 6259359 2011-03-22 17:25:55.840 2011-03-22 17:25:55.840 16515633 6259359 2011-03-22 17:25:55.840 2011-03-22 17:25:55.840 16515666 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515667 3114325 2011-03-23 11:46:24.247 2011-03-23 11:46:24.247 16515664 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515665 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515662 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515663 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515660 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515661 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515658 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515659 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515656 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515657 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515654 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515655 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515652 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 16515653 3114325 2011-03-23 11:46:24.243 2011-03-23 11:46:24.243 5507378 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507379 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507376 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 5507377 3114109 2008-07-01 13:50:12.373 2008-07-01 13:50:12.373 16515669 3114325 2011-03-23 11:46:24.247 2011-03-23 11:46:24.247 16515668 3114325 2011-03-23 11:46:24.247 2011-03-23 11:46:24.247 19163830 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163831 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 3670252 3637497 19163828 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163829 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163834 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163835 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163832 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163833 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 3670258 3637503 19163838 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 3670243 3637488 19163839 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163836 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163837 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 6259406 6226609 13 2008-10-16 15:14:27.940 2008-10-16 16:34:46.957 6259368 6259404 6226607 12 2008-10-16 15:14:27.940 2008-10-16 16:33:12.553 6259368 6259403 6226606 11 2008-10-16 15:14:27.940 2008-10-16 16:25:07.813 6259368 19163847 19040558 2012-09-11 17:47:48.210 2012-09-11 17:47:48.210 3670270 3637515 19163851 19040558 2012-09-11 17:47:48.210 2012-09-11 17:47:48.210 19163850 19040558 2012-09-11 17:47:48.210 2012-09-11 17:47:48.210 19163849 19040558 2012-09-11 17:47:48.210 2012-09-11 17:47:48.210 19163848 19040558 2012-09-11 17:47:48.210 2012-09-11 17:47:48.210 3670260 3637505 19163859 19040827 2012-09-11 19:02:42.767 2012-09-11 19:02:42.767 19163858 19040827 2012-09-11 19:02:42.767 2012-09-11 19:02:42.767 3670266 3637511 19163860 19040827 2012-09-11 19:02:42.767 2012-09-11 19:02:42.767 6259384 6226587 1 2008-10-16 15:14:27.940 2008-10-16 15:14:27.940 6259368 19163861 19040827 2012-09-11 19:02:42.767 2012-09-11 19:02:42.767 19163862 19040827 2012-09-11 19:02:42.767 2012-09-11 19:02:42.767 6259386 6226589 2 2008-10-16 15:14:27.940 2008-10-16 15:45:58.190 6259368 19163863 19040827 2012-09-11 19:02:42.767 2012-09-11 19:02:42.767 6259381 6226584 6 2008-10-16 14:24:15.190 2008-10-16 15:20:32.623 6259359 6259371 6226574 4 2008-10-16 14:24:15.190 2008-10-16 14:43:46.750 6259359 6259373 6226576 5 2008-10-16 14:24:15.190 2008-10-16 15:16:53.107 6259359 6259400 6226603 9 2008-10-16 15:14:27.940 2008-10-16 16:18:54.807 6259368 6259401 6226604 10 2008-10-16 15:14:27.940 2008-10-16 16:21:34.640 6259368 3670235 3637480 6259396 6226599 7 2008-10-16 15:14:27.940 2008-10-16 16:11:57.937 6259368 6259398 6226601 8 2008-10-16 15:14:27.940 2008-10-16 16:16:51.230 6259368 6259392 6226595 5 2008-10-16 15:14:27.940 2008-10-16 15:57:00.353 6259368 6259394 6226597 6 2008-10-16 15:14:27.940 2008-10-16 16:01:06.307 6259368 6259387 6226590 3 2008-10-16 15:14:27.940 2008-10-16 15:46:56.720 6259368 6259390 6226593 4 2008-10-16 15:14:27.940 2008-10-16 15:47:11.467 6259368 3670188 3637431 3670189 3637433 6259366 6226569 3 2008-10-16 14:24:15.190 2008-10-16 14:39:57.713 6259359 6259364 6226567 2 2008-10-16 14:24:15.190 2008-10-16 14:32:01.460 6259359 6259361 6226564 1 2008-10-16 14:24:15.190 2008-10-16 14:24:15.190 6259359 19163801 19040813 2012-09-10 16:01:22.610 2012-09-10 16:01:22.610 19163802 19040813 2012-09-10 16:01:22.610 2012-09-10 16:01:22.610 3670159 3637401 19163803 19040813 2012-09-10 16:01:22.610 2012-09-10 16:01:22.610 19163804 19040813 2012-09-10 16:01:22.610 2012-09-10 16:01:22.610 19163805 19040813 2012-09-10 16:01:22.610 2012-09-10 16:01:22.610 19163806 19040813 2012-09-10 16:01:22.610 2012-09-10 16:01:22.610 19163807 19040813 2012-09-10 16:01:22.610 2012-09-10 16:01:22.610 19163825 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 6259324 6226527 1 2008-10-03 16:14:13.217 2008-10-03 16:14:13.217 6259287 19163824 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163827 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19163826 19040811 2012-09-10 16:03:37.273 2012-09-10 16:03:37.273 19040815 19073509 2 2012-09-10 15:59:38.217 2012-09-10 16:02:56.210 19040811 3604484 1 3114109 2008-04-11 14:07:15.087 2008-04-11 14:07:15.087 3604485 3 3114325 2008-04-11 14:58:15.027 2008-04-18 14:39:15.040 19040814 19073508 1 2012-09-10 15:59:38.217 2012-09-10 15:59:38.217 19040811 10356098 10388824 11 2008-10-16 14:24:15.190 2009-05-12 14:12:23.473 6259359 10356100 10388826 16 2008-10-16 15:14:27.940 2008-11-25 11:12:17.340 6259368 19040825 19073519 20 2012-08-16 08:24:37.683 2012-08-16 16:41:38.157 19040558 10356103 10388829 1 2009-09-02 14:39:38.767 2009-09-02 14:39:38.767 10356102 10356105 10388831 2 2009-09-02 14:39:38.767 2009-09-02 15:22:57.553 10356102 19040831 19073524 2 2012-09-11 17:54:13.537 2012-09-11 17:56:32.300 19040827 19040833 19073526 3 2012-09-11 17:54:13.537 2012-09-11 18:47:53.297 19040827 19040828 19073521 1 2012-09-11 17:54:13.537 2012-09-11 17:54:13.537 19040827 19040835 19073528 4 2012-09-11 17:54:13.537 2012-09-11 18:52:42.463 19040827 19040837 19073530 5 2012-09-11 17:54:13.537 2012-09-11 19:00:07.890 19040827 3179709 3114231 5373996 5406759 3 2008-06-11 11:07:52.247 2008-06-12 13:14:43.510 5275678 6326276 6259322 2008-10-09 10:31:23.933 2008-10-09 10:31:23.933 5373988 5406751 2 2008-06-11 11:07:52.247 2008-06-11 11:09:41.940 5275678 12484683 12550219 4 2008-03-24 11:31:02.937 2010-05-21 10:24:10.200 3114325 3179715 3114238 3179718 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications \\ \\ | *Parameter* | *Values* | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations   !HE104_plus_dx_conn_loc.JPG|align=left!                       \\ h1. Links [Datasheet|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Docs/Data%20Sheets/he104_plus_dx_spec.pdf] \\ [User's Manual|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Docs/Manuals/he104_plus_dx_man.pdf] \\]]> 3114242 3638123 3670862 70 2008-03-21 17:04:00.783 2008-05-07 15:17:58.050 3114109 11239724 11272487 12 2009-02-25 16:45:05.063 2009-05-06 12:41:22.837 9371909 12484681 12550217 3 2008-03-24 11:31:02.937 2008-03-24 11:44:04.280 3114325 19040809 19073504 19 2012-08-16 17:27:30.563 2012-08-17 10:15:53.737 19040630 18579472 18645008 10 2011-12-09 15:58:37.633 2012-01-09 17:52:42.107 18252651 18579470 18645006 9 2011-12-09 15:58:37.633 2011-12-09 16:25:57.073 18252651 16515490 6259368 2011-03-16 13:33:33.390 2011-03-16 13:33:33.390 16515491 6259368 2011-03-16 13:33:33.390 2011-03-16 13:33:33.390 16515488 6259368 2011-03-16 13:33:33.390 2011-03-16 13:33:33.390 16515489 6259368 2011-03-16 13:33:33.390 2011-03-16 13:33:33.390 18285142 '.  Alternatively, use 'aptitude', which is a gui-ish front end to apt. Unfortunately, the Debian etch release, used in the deployed FOCE, is several versions out of date now.  The default configuration files for aptitude are configured to point at the current Debian release.  Thus 'apt-get' or 'aptitude' fails now. The solution is to update the configuration files and the database.   The configuration file is at /etc/apt/sources.list By default, it contains lines that look like: {code}  deb http://linux.csua.berkeley.edu/debian/ etch main deb-src http://linux.csua.berkeley.edu/debian/ etch main {code}  You must add references to the debian archive, as follows: {code}  deb http://archive.debian.org/debian/ etch main contrib deb-src http://archive.debian.org/debian/ etch main contrib {code}\\ When done, recompile the database with 'apt-get update'.\\]]> 18252384 10387670 [note: source siam-env; note the dot] - /home/ops/scripts/minimalCheckout [note: this takes a long time] - -mv /home/ops/build/siam2 /home/ops/build/siam2-\- Now done by minimalCheckout h2. Make - *.* /home/ops/scripts/siam-env /home/ops/build/ [note: source siam-env; note the dot] - cd /home/ops/build/ - mkdir classes if it doesn't exist - make \-s [note: this takes 20-30 min, you'll only see errors and warnings (there are many harmless warnings)] - make siamjar  - cd /native/foce - make foceio - make testSensoray - cd /home/ops/build/siam2- - cvs \-Q co puckxml - mkdir ports if it doesn't exist - make focepucks -(note: 1731.xml is missing; I've been copying junk.xml to 1731.xml)- - cp properties/siamPort.cfg.foce properties/siamPort.cfg h2. To install: - exitNode loc - cp /home/ops/siam2 /home/ops/siam2- - mv /home/ops/build/siam2- /home/ops/siam2]]> 10354905 16515493 6259368 2011-03-16 13:33:33.390 2011-03-16 13:33:33.390 16515492 6259368 2011-03-16 13:33:33.390 2011-03-16 13:33:33.390 3179613 3114132 3277078 4 3114136 2008-03-22 14:25:15.027 2008-03-22 14:43:15.013 3277079 28 3114136 2008-03-22 14:33:15.023 2008-04-18 15:26:15.027 3277074 3 3114109 2008-03-22 14:09:15.027 2008-03-22 14:10:15.027 3179617 3114136 3277073 1 3114109 2008-03-22 14:09:15.020 2008-03-22 14:09:15.020 3179604 3114123 3277071 19 3114128 2008-03-22 14:08:15.013 2008-03-23 12:54:15.027 3277069 1 3114136 2008-03-22 14:03:15.013 2008-03-22 14:03:15.013 3179609 3114128 3277066 1 3114128 2008-03-22 14:00:15.033 2008-03-22 14:00:15.033 3277067 1 3114132 2008-03-22 14:01:15.027 2008-03-22 14:01:15.027 19073259 19040558 3277065 1 3114128 2008-03-22 14:00:15.030 2008-03-22 14:00:15.030 3277064 1 3114128 2008-03-22 13:59:15.027 2008-03-22 13:59:15.027 3277062 1 3114128 2008-03-22 13:58:15.017 2008-03-22 13:58:15.017 3277061 4 3114123 2008-03-22 13:57:15.027 2008-03-23 12:53:15.023 3277060 1 3114123 2008-03-22 13:51:15.027 2008-03-22 13:51:15.027 3277059 3 3114109 2008-03-22 13:16:15.497 2008-03-27 08:21:15.017 3277057 79 3114109 2008-03-21 17:12:15.023 2008-05-31 11:47:15.053 3277056 4 3114109 2008-03-21 17:11:15.017 2008-03-22 13:57:15.030 3277054 17 3114109 2008-03-21 17:09:15.023 2008-03-22 14:07:15.017 3277052 1 3114109 2008-03-21 17:04:15.027 2008-03-21 17:04:15.027 3179591 3114109 3637933 3670682 69 2008-03-21 17:04:00.783 2008-05-07 14:29:37.537 3114109 3277114 3 3114136 2008-03-23 12:08:15.027 2008-03-23 12:08:15.027 3277115 8 3114242 2008-03-23 12:12:15.013 2008-03-23 12:30:15.023 3277116 15 3114123 2008-03-23 12:27:15.023 2008-04-18 14:58:15.017 3277119 80 3114325 2008-03-25 08:03:15.057 2008-05-31 15:18:15.070 3277120 1 3114325 2008-03-25 08:05:15.023 2008-03-25 08:05:15.023 3277121 2 3114325 2008-03-25 08:06:15.037 2008-03-25 08:07:15.020 3277124 44 3114132 2008-03-25 09:05:15.030 2008-05-30 14:33:15.027 3277125 5 3114109 2008-03-25 09:05:15.043 2008-03-25 11:43:15.077 3277126 6 3114128 2008-03-25 09:06:15.017 2008-04-14 15:20:15.027 3277127 119 3114109 2008-03-25 11:43:15.097 2008-06-02 17:05:15.160 3179918 3114446 3277128 23 3114136 2008-03-25 11:44:15.027 2008-06-02 09:19:15.017 3277131 1 3114389 2008-03-27 08:14:15.013 2008-03-27 08:14:15.013 3277130 2 3114325 2008-03-27 08:13:15.060 2008-04-01 09:33:15.050 3277133 1 3114109 2008-03-27 08:14:15.037 2008-03-27 08:14:15.037 3277132 2 3114325 2008-03-27 08:14:15.017 2008-04-23 15:33:15.020 19073327 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk. *Use dd to write SD card* *\[mac\]* * Insert SD card in slot or card reader * Use diskutil as root to find device: {code} $ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS mbari1633 499.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI 209.7 MB disk1s1 2: Apple_HFS SuperDuper 500.3 GB disk1s2 3: Apple_HFS TimeMachine 499.4 GB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *2.0 GB disk2 1: DOS_FAT_16 NO NAME 2.0 GB disk2s1 {code} * Unmount the SD card volume: {code} $ sudo diskutil unmountDisk /dev/disk2 Password: Unmount of all volumes on disk2 was successful {code} * Use dd to {code} $ sudo dd if=sdcard-ide2G.img of=/dev/disk2 {code} *\[linux\]* The process to do this under Linux is very similar except that it's not required to un-mount the drive before using the 'dd' command and the commands are a little different. For example, you would use "fdisk -l" instead of "diskutil list", your device node would be located at "/dev/sda" instead of "/dev/disk" and the un-mount command is "umount" instead of "diskutil unmountDisk".]]> 19040630 3277135 22 3114389 2008-03-27 08:15:15.013 2008-05-23 11:00:15.017 3277134 1 3114389 2008-03-27 08:14:15.037 2008-03-27 08:14:15.037 3277137 6 3114389 2008-03-27 08:40:15.027 2008-03-31 08:05:15.047 3277136 27 3114389 2008-03-27 08:24:15.020 2008-05-23 16:24:15.020 3277139 1 3114389 2008-03-27 08:41:15.033 2008-03-27 08:41:15.033 3277138 2 3114389 2008-03-27 08:41:15.030 2008-05-05 11:33:15.023 3277140 2 3114389 2008-03-27 10:02:15.043 2008-03-27 10:13:15.030 19073322 19040625 4882450 3145737 2008-06-03 12:42:07.233 2008-06-03 12:42:07.233 3277084 1 3114136 2008-03-22 14:57:15.027 2008-03-22 14:57:15.027 19073310 install LWP::UserAgent perl \-MCPAN \-e 'install LWP::UserAgent' \- install LTIB via CVS $ cvs \-z3 \-d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/ltib co \-P ltib $ cd ltib $ ./ltib]]> 19040612 4882449 3145737 2008-06-03 12:42:07.233 2008-06-03 12:42:07.233 4948031 4915268 4882451 3145737 2008-06-03 12:42:07.233 2008-06-03 12:42:07.233 3277083 1 3114136 2008-03-22 14:55:15.023 2008-03-22 14:55:15.023 3277088 1 3114132 2008-03-22 16:04:15.030 2008-03-22 16:04:15.030 19073314 &1 > ${OUTFILE} # Use the line below if you don't have pv!   # /bin/cat ${INFILE} > ${OUTFILE} cat << EOF   File transfer complete EOF sleep 1 {code} Now go over to minicom and go to the configuration menu (via ESC-O), then "File transfer protocols". You can add a section there called "binary", point it at your file, and specify:     •    Name: Binary     •    Program: /home/MYUSERNAME/bin/bin-xfer \-o %l     •    Name: Y     •    U/D:  U     •    FullScr: Y     •    IO-Red: N     •    Multi:N {code} Then leave the menu and save your options.  Next time you send a file (via ESC-S), you should see "Binary" listed as an option. [my alternative version] #!/bin/sh INFILE=/dev/null OUTFILE=/dev/null VERBOSE="TRUE"   while [ $# -gt 0 ]; do  case "$1" in  -i)  shift  INFILE="$1"  ;;  -o)  shift  OUTFILE="$1"  ;;  -q)  VERBOSE="FALSE"  ;;  -h|--help)  echo "$0 [-q] -i infile -o outfile"  ;;  *)  INFILE="$1"  esac  shift done if [ ${VERBOSE} == "TRUE" ] then  cat << EOF  binary-xfer utility for minicom  Sending file ${INFILE} to ${OUTFILE} EOF fi   #/usr/bin/pv --force -i 0.25 -B 128  ${INFILE}  2>&1 > ${OUTFILE} # Use the line below if you don't have pv!    /bin/cat ${INFILE} > ${OUTFILE} #cat << EOF   if [ ${VERBOSE} == "TRUE" ] then  File transfer complete  EOF fi sleep 1 {code}]]> 19040617 3277089 34 3114132 2008-03-22 16:10:15.023 2008-05-28 13:04:15.037 4882448 3145737 2008-06-03 12:42:07.233 2008-06-03 12:42:07.233 4882447 3145737 2008-06-03 12:41:56.420 2008-06-03 12:41:56.420 3277090 41 3114109 2008-03-22 16:48:15.027 2008-03-25 08:57:15.017 19073306 /arm-linux-gnu distclean $ make phy3250_config $ make ARCH=arm CROSS_COMPILE=/arm-linux-gnu- {code}     •    Once the build completes, the u-boot binary image for deployment can be found at {code} uboot/u-boot-2009.03/u-boot.bin {code} ======== A working u-boot config \[will need to change IP addresses, etc. - it is possible to use DHCP\] ======== To enter U-Boot, hit a key during the u-boot loader sequence. Useful commands: * printenv * setenv \\ {code} bootdelay=3 baudrate=115200 rootpath=/home/user/ltib/rootfs loadaddr=0x80100000 nfsboot=setenv bootargs console=ttyS0,115200n8 root=/dev/nfs3 rw nfsroot=${serverip}:${rootpath} ip=${ipad dr} ethaddr=${ethaddr} ramdiskboot=setenv bootargs console=ttyS0,115200n8 root=/dev/ram0 rw ip=${ipaddr} ethaddr=${ethaddr} tftpstatickernel=tftpboot ${loadaddr} ${serverip}:${bootfile} tftpdhcpkernel=dhcp mtdkernel=nboot.jffs2 ${loadaddr} 0 0x00204000 mtdkernelburn=nand erase 0x00204000 0x00400000;nand write.jffs2 ${loadaddr} 0x00204000 0x00400000 rootfile=rootfs.jffs2 rootloadaddr=0x82000000 tftpstaticloadroot=tftpboot ${rootloadaddr} ${serverip}:${rootfile} tftpdhcploadroot=dhcp ${rootloadaddr} ${serverip}:${rootfile} ramdiskload=nand read.jffs2 ${rootloadaddr} 0x00604000 ${rootloadsize} bootargs=console=ttyS0,115200n8 root=/dev/nfs3 rw nfsroot=192.168.1.41:/home/user/ltib/rootfs ip=192.168.1 .101 ethaddr=00:50:C2:A5:BB:A8 autoload=no bootfile=uImage bootcmd=run mtdboot; run mtdkernel; bootm $(loadaddr) mtdboot=setenv bootargs console=ttyS0,115200n8 root=/dev/mtdblock4 rw rootfstype=jffs2 ip=134.89.11.120 in it=/sbin/init ethaddr=00:50:C2:A5:BB:A8 mtdrootburn=nand erase 0x00604000 0x039FC000; nand write.jffs2 ${rootloadaddr} 0x00604000 ${rootloadsize} filesize=640000 fileaddr=82000000 gatewayip=134.89.10.1 netmask=255.255.254.0 ipaddr=134.89.11.120 serverip=134.89.11.121 rootloadsize=0x640000 stdin=serial stdout=serial stderr=serial ethaddr=00:50:C2:A5:BB:A8 {code}]]> 19040608 3277097 2 3114109 2008-03-23 11:12:15.023 2008-03-23 11:13:15.017 3277094 2 3114109 2008-03-22 16:55:15.023 2008-03-23 11:17:15.020 18252663 18285408 7 2011-12-09 15:58:37.633 2011-12-09 16:22:34.650 18252651 18252664 18285409 8 2011-12-09 15:58:37.633 2011-12-09 16:23:18.150 18252651 3277099 1 3114109 2008-03-23 11:14:15.017 2008-03-23 11:14:15.017 3277098 1 3114109 2008-03-23 11:13:15.017 2008-03-23 11:13:15.017 3277105 5 3114238 2008-03-23 11:21:15.017 2008-04-18 15:59:15.037 18252659 18285404 4 2011-12-09 15:58:37.633 2011-12-09 16:03:16.843 18252651 18252660 18285405 5 2011-12-09 15:58:37.633 2011-12-09 16:21:05.477 18252651 3277103 13 3114231 2008-03-23 11:19:15.020 2008-05-29 09:54:15.017 18252661 18285406 6 2011-12-09 15:58:37.633 2011-12-09 16:21:58.987 18252651 3277102 1 3114231 2008-03-23 11:18:15.017 2008-03-23 11:18:15.017 19073296 19040598 3277109 1 3114242 2008-03-23 11:22:15.030 2008-03-23 11:22:15.030 18252657 18285402 3 2011-12-09 15:58:37.633 2011-12-09 15:59:51.007 18252651 3277106 1 3114238 2008-03-23 11:21:15.023 2008-03-23 11:21:15.023 3277113 3 3114231 2008-03-23 12:07:15.027 2008-03-24 09:11:15.053 3277112 4 3114242 2008-03-23 12:06:15.017 2008-03-23 12:06:15.017 18252652 18285399 1 2011-12-09 15:58:37.633 2011-12-09 15:58:37.633 18252651 19073290 New... ** continue w/o disc ** create custom virtual machine ** Insert CD ** Use operating system installation disc or image ** choose CD drive ** Choose operating system (should show Linux, Ubuntu) ** Select "Use Easy Install" ** enter account name and password ** Select "Make home folder accessible to virtual machine" ** Select read/write permissions ** Download VMWare tools for Linux guest if prompted ** Select finish or customize settings ** Default 1 GB RAM, 20 GB HDD ** shows Ubuntu VMWare guest window; select Play symbol icon ** Automatically installs Ubuntu from CD...(Control-Command to release mouse) ** Reboots to desktop login screen ** Allow update manager to update ** /mnt/hgfs mounts shared Mac User home directory * Packages ** autoconf ** libtool (for autoreconf)]]> 19040591 18252653 18285400 2 2011-12-09 15:58:37.633 2011-12-09 15:59:13.893 18252651 3277111 4 3114128 2008-03-23 11:58:15.027 2008-03-23 12:06:15.023 3277110 13 3114242 2008-03-23 11:35:15.030 2008-04-18 16:12:15.027 3277190 3 3114132 2008-04-04 14:58:15.027 2008-04-23 09:09:15.040 3277189 4 3114325 2008-04-04 14:57:15.033 2008-05-28 13:04:15.027 3637889 3670640 4 2008-05-07 13:24:08.253 2008-05-07 13:32:18.400 3637883 3637888 3670639 3 2008-05-07 13:24:08.253 2008-05-07 13:24:42.383 3637883 3637886 3670637 7 2008-04-22 09:00:30.627 2008-04-22 09:20:08.087 3637488 3637885 3670636 2 2008-05-07 13:24:08.253 2008-05-07 13:24:29.530 3637883 3637884 3670635 1 2008-05-07 13:24:08.253 2008-05-07 13:24:08.253 3637883 3637897 3670648 10 2008-05-07 13:24:08.253 2008-05-07 13:41:16.987 3637883 3637895 3670646 9 2008-05-07 13:24:08.253 2008-05-07 13:37:16.337 3637883 3637894 3670645 8 2008-05-07 13:24:08.253 2008-05-07 13:35:55.000 3637883 3637893 3670644 7 2008-05-07 13:24:08.253 2008-05-07 13:33:54.447 3637883 3637892 3670643 6 2008-05-07 13:24:08.253 2008-05-07 13:33:15.187 3637883 3637891 3670642 5 2008-05-07 13:24:08.253 2008-05-07 13:32:30.837 3637883 3637903 3670654 66 2008-03-21 17:04:00.783 2008-04-22 10:16:33.897 3114109 3277153 6 3114109 2008-04-01 08:25:15.030 2008-05-29 09:55:15.023 3277150 4 3114242 2008-03-27 13:51:15.020 2008-03-31 09:12:15.057 3637906 3670656 67 2008-03-21 17:04:00.783 2008-05-07 14:28:37.550 3114109 3277149 36 3114231 2008-03-27 12:40:15.027 2008-06-02 17:05:15.153 3637911 3670661 1 2008-05-07 14:27:52.313 2008-05-07 14:27:52.313 3637901 3277160 7 3114325 2008-04-01 09:43:15.030 2008-05-29 14:29:15.037 3277161 5 3114446 2008-04-01 09:48:15.037 2008-04-01 16:54:15.053 3277158 20 3114446 2008-04-01 09:43:15.027 2008-05-22 14:19:15.030 3277159 1 3114446 2008-04-01 09:43:15.030 2008-04-01 09:43:15.030 3277156 5 3114109 2008-04-01 09:33:15.047 2008-05-30 08:29:15.050 3637907 3670657 1 2008-05-07 14:29:02.983 2008-05-07 14:29:02.983 3637905 3637908 3670658 68 2008-03-21 17:04:00.783 2008-05-07 14:29:13.257 3114109 3277157 3 3114325 2008-04-01 09:33:15.050 2008-06-02 17:05:15.170 3277154 1 3114325 2008-04-01 08:34:15.033 2008-04-01 08:34:15.033 3277155 11 3114109 2008-04-01 09:33:15.033 2008-05-30 08:25:15.023 3637910 3670660 2 2008-05-07 14:29:02.983 2008-05-07 14:29:13.263 3637905 3277169 1 3114325 2008-04-01 09:58:15.023 2008-04-01 09:58:15.023 3277168 5 3114109 2008-04-01 09:57:15.017 2008-06-02 09:19:15.040 3637919 3670669 1 2008-04-18 16:47:42.230 2008-04-18 16:47:42.230 3637431 3277167 3 3114238 2008-04-01 09:56:15.017 2008-04-01 13:32:15.050 3277166 18 3114238 2008-04-01 09:56:15.017 2008-06-02 15:30:15.097 3277165 14 3114123 2008-04-01 09:55:15.020 2008-05-31 16:41:15.017 3277164 11 3114325 2008-04-01 09:54:15.023 2008-05-28 12:55:15.037 3277163 3 3114446 2008-04-01 09:53:15.027 2008-04-01 11:31:15.070 3277162 5 3114231 2008-04-01 09:52:15.020 2008-04-02 08:39:15.060 3277177 10 3114109 2008-04-01 13:33:15.023 2008-04-22 17:07:15.020 3277176 2 3114109 2008-04-01 13:32:15.027 2008-04-01 13:32:15.027 3277173 2 3114238 2008-04-01 10:46:15.050 2008-04-01 10:46:15.050 3637924 3670674 2 2008-04-18 16:47:51.197 2008-05-07 14:59:56.053 3637433 3277172 1 3114238 2008-04-01 10:00:15.040 2008-04-01 10:00:15.040 3637923 3670673 1 2008-04-18 16:47:51.197 2008-04-18 16:47:51.197 3637433 3277171 1 3114325 2008-04-01 10:00:15.033 2008-04-01 10:00:15.033 12025858 3407887 3114325 2010-04-28 08:59:20.267 2010-04-28 08:59:20.267 3277170 1 3114238 2008-04-01 09:58:15.047 2008-04-01 09:58:15.047 3637925 3670675 2 2008-04-18 16:47:42.230 2008-05-07 14:57:55.010 3637431 19161410 19040608 2012-08-16 17:14:45.007 2012-08-16 17:14:45.007 19161411 19040608 2012-08-16 17:14:45.010 2012-08-16 17:14:45.010 4915265 4948028 1 2008-04-22 09:24:39.360 2008-04-22 09:24:39.360 3637503 19041221 19073911 4 2012-11-14 18:40:38.063 2012-11-14 18:53:51.047 19041215 19161405 19040598 2012-08-16 16:48:36.367 2012-08-16 16:48:36.367 19041220 19073910 3 2012-11-14 18:40:38.063 2012-11-14 18:51:05.697 19041215 19161406 19040598 2012-08-16 16:48:36.367 2012-08-16 16:48:36.367 19161407 19040617 2012-08-16 16:57:11.597 2012-08-16 16:57:11.597 10459153 10356102 2009-09-02 15:34:00.350 2009-09-02 15:34:00.350 4915270 4948033 1 2008-06-09 14:42:02.883 2008-06-09 14:42:02.883 4915268 19041218 19073908 2 2012-11-14 18:40:38.063 2012-11-14 18:50:47.840 19041215 19041217 19073907 1 2012-11-14 18:40:38.063 2012-11-14 18:40:38.063 19041215 10459154 10356102 2009-09-02 15:34:00.350 2009-09-02 15:34:00.350 3735599 3637915 2008-05-07 14:45:23.950 2008-05-07 14:46:38.597 1270 1 3735598 3637915 2008-05-07 14:45:14.390 2008-05-07 14:46:38.600 547971 1 4915272 4948035 23 2008-03-27 08:13:59.440 2008-05-23 16:24:11.733 3114389 3735601 3637433 2008-05-07 14:58:56.640 2008-05-07 14:58:56.640 22214 1 3735600 3637431 2008-05-07 14:56:45.420 2008-05-07 14:56:45.420 50447 1 3735594 3637901 2008-05-07 14:23:55.650 2008-05-07 14:27:52.370 124898 1 3735595 3637901 2008-05-07 14:27:00.270 2008-05-07 14:27:52.367 14575 1 3735596 3637905 2008-05-07 14:32:54.480 2008-05-07 14:32:54.480 15742 1 3735597 3637913 2008-05-07 14:40:37.507 2008-05-07 14:41:34.207 17113 1 19161421 19040625 2012-08-16 17:20:07.890 2012-08-16 17:20:07.890 19161420 19040625 2012-08-16 17:20:07.890 2012-08-16 17:20:07.890 3735592 3637883 2008-05-07 13:23:44.473 2008-05-07 13:24:08.363 8186 1 3735593 3637883 2008-05-07 13:23:58.107 2008-05-07 13:24:08.357 8296 1 3179799 3114325 19161419 19040625 2012-08-16 17:20:07.890 2012-08-16 17:20:07.890 18285398 18252651 3735580 3637515 2008-04-22 09:58:03.463 2008-04-22 09:58:11.337 36398 1 3735579 3637511 2008-04-22 09:50:31.350 2008-04-22 09:55:17.810 46683 1 3735578 3637505 2008-04-22 09:44:40.220 2008-04-22 09:44:40.220 33445 1 3735577 3637503 2008-04-22 09:23:24.220 2008-04-22 09:24:39.387 52709 1 3735576 3637497 2008-04-22 09:16:33.653 2008-04-22 09:19:34.623 20329 1 3735575 3735575 3637497 2008-04-22 09:16:33.653 2008-04-22 09:19:34.623 20329 2 3735574 3637488 2008-04-22 09:00:22.010 2008-04-22 09:03:09.850 4126 2 3735572 3735573 3637488 2008-04-22 09:00:22.010 2008-04-22 09:00:30.733 4126 1 3735572 3735572 3637488 2008-04-22 09:00:22.010 2008-04-22 09:03:38.353 4126 3 3735571 3637480 2008-04-22 08:52:08.667 2008-04-22 08:52:21.140 19363 1 3735568 3114109 2008-04-18 16:31:21.713 2008-04-18 16:31:21.713 19259 1 3735567 3637401 2008-04-18 16:04:05.180 2008-04-18 16:04:05.180 27563 1 3114324 3145737 3179798 1 2008-03-24 11:31:02.913 2008-03-24 11:31:02.913 4915281 4948044 24 2008-03-27 08:13:59.440 2008-06-09 16:24:01.030 3114389 3637856 3670605 20 2008-03-27 08:13:59.440 2008-03-29 17:00:57.407 3114389 4849683 10 3114325 2008-06-03 13:12:15.053 2008-06-06 11:09:15.073 4849682 18 3114109 2008-06-03 13:12:15.040 2008-06-06 11:23:15.020 19041142 19073833 6 2012-08-16 15:59:18.553 2012-08-16 16:41:38.173 19040591 19041139 19073830 3 2012-11-07 16:36:06.830 2012-11-07 16:56:49.617 19041133 19041140 19073831 4 2012-11-07 16:36:06.830 2012-11-07 17:28:22.450 19041133 19073507 [must do each time you run x11] ssh user@beagleboneHost on beaglebone: export DISPLAY=macHost:0.0 lcm-spy [have not yet gotten X forwarding to work to Ubuntu VM. One post said xhost is not secure, and to use - ssh w/ -X option, - to install xbase-clients package on the ubuntu host. - to edit /etc/ssh/sshd_config), and set the line X11Forwarding yes this didn't work for me. ] ]]> 19040813 19073520 19040827 3179861 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. \\]]> 3114389 19041137 19073828 2 2012-11-07 16:36:06.830 2012-11-07 16:42:33.607 19041133 19041135 19073826 1 2012-11-07 16:36:06.830 2012-11-07 16:36:06.830 19041133 19073506 ./oebb.sh update ./oebb.sh tag [tagname] ./oebb.sh changelog ./oebb.sh checkout ./oebb.sh clean Not recommended, but also possible: ./oebb.sh bitbake It is recommended to do '. /home/headley/.oe/environment-angstromv2012.05' and run 'bitbake something' inside /home/user/projects/oe/setup-scripts without using oebb.sh as wrapper You must invoke "./oebb.sh config " and then "./oebb.sh update" prior to your first bitbake command Note: may be beaglebone Example: [assumes running as user, OE_HOME=~/projects/oe] cd $OE_HOME source ~/.oe/environment-angstromv2012.05 MACHINE="beaglebone" ./oebb.sh config beaglebone MACHINE="beaglebone" ./oebb.sh update =========================== Building Pre-Defined Images =========================== Images defined in bitbake recipe (.bb) files; there are many in oe/setup-scripts/sources/. There are generic Angstrom targets oe/setup-scripts/sources/meta-angstrom/recipes-images/angstrom There are platform-specific directories like oe/setup-scripts/sources/meta-ti/recipes-misc/images To find all the image names, use: oe/setup-scripts$ find ./sources/ -name "*image*"|grep bb Generic Angstrom oe/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/ xfce-nm-image systemd-image hardware-bringup-image systemd-gnome-image console-base-image efl-nodm-image console-image TI Beaglebone oe/setup-scripts/sources/meta-ti/recipes-misc/images/ cloud9-image.bb ti-hw-bringup-image.bb cloud9-gfx-image.bb cloud9-gnome-image.bb Common commands/pattern for recompiling if bitbake doesn't work, may try: bitbake -c clean -f bitbake -c compile -f bitbake -c deploy [binaries updated in $OE_HOME/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/deploy/images/beaglebone/ ] bitbake x-load [MLO bootstrap loader] bitbake u-boot [linux loader] bitbake virtual/kernel [linux kernel] =========================== Customize Pre-Defined Images =========================== =========================== Build Default Kernel =========================== For a default build, just run: bitbake virtual/kernel After done, you can collect the built image from under the deploy folder, for example: build/tmp-angstrom_v2012_05-eglibc/deploy/images/beaglebone/ =========================== Configure Kernel(XWindows) =========================== Configure If you need to customize the kernel configuration, you may run the menuconfig task by: bitbake -c menuconfig virtual/kernel Compile bitbake -f -c compile virtual/kernel Fine Control If you need more control over the configuration and compile process, add this somewhere into your local.conf: INHERIT += "devshell" and then you can go to the shell by: bitbake -c devshell virtual/kernel The build environment will be well setup for you; you can run regular make commands like make bzImage ...etc Please note, that the INHERIT step depends on the distribution you're using, some of the distributions already include the INHERIT in their configuration, so it might work already. You can check that easily using listtask task. Preserve Custom Config Changes are lost if you remove the tmpdir or do a "bitbake -c clean virtual/kernel", so you may consider replacing the defconfig with it. =========================== Configure Kernel (non-XWindows) =========================== Note: by default these commands require you to run in X Windows. Q: By default, some bitbake tasks, like devshell and menuconfig, require to run in X Windows, but I have a slow link to the build host. How can I change that requirement? A: Edit the bitbake config file openembedded/conf/bitbake.conf. Under the UI/Interaction Configuration section, set: TERMCMD ?= "${SCREEN_TERMCMD}" # = screen -D -m -t "$TERMWINDOWTITLE" TERMCMDRUN ?= "${SCREEN_TERMCMDRUN}" That will start a screen session to run the task. To attach to the session, open another terminal session and run: screen -r Please read the man page of the screen utility to customize TERMCMD for your requirement. ]]> 19040811 3735623 3638124 2008-05-19 16:51:05.320 2008-05-19 16:51:44.507 7434 1 9831192 9798441 9831060 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. 6) Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. 7) Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. 8) Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml h5. Configure SIAM pieces * cp properties/siamPort.cfg.foce properties/siamPort.cfg (i) You may have to edit the siamPort.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, confirm the top-level Makefile points to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce (i) It isn't clear whether the foce Makefile is complete. If there is any doubt, it is always a good idea to run 'make clean', to make sure you really have a clean build. {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. 9) Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps -ef | grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & Look at these [user notes|FOCE:User Documentation] on running FOCE.]]> 9798307 19073908 19041218 19073907 | \\ | Java | C+\+ | C | Analysis | | Determinism/RT performance | ? | ? | ??? | Java and C had similar performance in the timer test, but it was more straightforward to write simple working demonstration and tune performance in C than Java.\\ In full system, concern is that Java would  not perform as well, and be more susceptible to third party code not optimized for embedded use.\\ The nominal real time requirement is to support sampling (~16 services) at 5 Hz; the precise requirements aren't known, and new requirements may emerge to sample at high rates for predicitive/feed-forward elements that we can't anticipate today. \\ The real time requirements aren't thought to be high, but they are not well defined. \\ We should leave some performance head room for this, and C has an edge over Java, both in benchmarks and being geared towards efficient embedded performance  | | Strong data typing | ??? | ?? | ? | All (three) languages are strongly typed, but (void) pointers present pitfalls for the uninitiated.\\ Java has better compile time enforcement of data typing, which is a plus for the developer. | | Memory Management | ??? | ? | ?? | Java is garbage collected, though there is a performance cost. On an embedded system, care must be taken to avoid object creation, and it isn't always clear to users which practices will lead to heavy GC use.\\ \\ The GC mechanism is not exposed well. Though there are some tuning parameters, it is not straightforward to use them, especially for an inexperienced user. \\ \\ C/C+\+ must me explicitly managed, requiring skill and effort, but maybe ultimately more reliable.\\ \\ Rather than provide a false sense of security, it may be better for users to assume responsibility for memory managment. A framework can provide mechanisms to make this easier and more reliable. | | Anticipated codebase size | ? | ? | ? | We should keep the codebase as small as possible, but maintainable. It would probably be larger than OASIS, since it adds features and requirements (coordination of services, real time data access, user interface clients, metadata handling, etc.). \\ Larger codebases with multiple developers would lead to using OO; generally OO also enables software reuse. On the other hand, the Linux kernel and many other projects are primarily C and have many developers.\\ xFOCE implementers will likely have few developers, and the codebase is intended to be kept small enough for one developer to manage. \\ \\ Any of these languages would be OK from this perspective. | | Easier to understand | ? | ? | ? | Very subjective, very important but difficult to evaluate as a selection criteria | | Easier to debug | ?? | ? | ??? | OO initialization and execution paths can be hard to trace because of inheritance and polymorphism. C execution  is more linear, and is easier to trace.\\ \\ There are pretty good tools available for all of these languages, including IDEs, debuggers, profilers. The tools may be a little easier to assemble and use for Java, though they are somewhat less geared towards embedded systems. | | Productivity | ??? | ? | ?? | There are good productivity tools for any of the languages.\\ Java compiler is much slower on the host platform for a given application, so the edit/compile/debug cycle is long on the host.\\ There are cross compilation environments for any of these languages, though Java may be easier to install.  \\ There are some nice profiling tools for both C and Java. | | Requires users to understand language internals | ?? | ? | ??? | Java exposes less of the language internals and has a lot of opaque libraries, so it isn't always clear where to turn when tackling performance problems. On the other hand, C/C+\+ can be pretty technical and require better understanding of the hardware, but provide more (and more explicit) knobs for adjusting performance. | | Direct control of hardware | ? | ?? | ??? | C is especially well suited to programming for embedded hardware (e.g. memory mapped IO, precision timers, interrupt handling) | | Portability | ?? | ? | ??? | C/C+\+ compilers more ubiquitous and of more consistent quality than JVMs for small embedded platforms.\\ \\ Java is intended to be cross platform (and is), but less so in the embedded space. There are many embedded platforms that don't support Java, especially in the low-power end of the processor ecosystem. There are however many ARM variants that can run Java thanks to the mobile device industry. But if users really have a need to port to a lower power processor, there are many more options with C language support, making it an easier technology pattern to follow. | | Extensibility | ??? | ? | ?? | The risk with OO languages are that we will build a framework that is too large and abstract, and that our users will probably do cut and paste extension anyway. \\ A risk with C is that it can be more difficult to propagate changes affecting multiple modules in C if the codebase is not well designed.  \\ OO languages have an extensibility advantage for disciplined software engineers and teams, but our users may benefit less from that, and our codebase may become bloated and abstract as a result. | | Existing user base | ? | ? | ? | The existing user base (population 2) is not statistially significant. They favor procedural (eFOCE) and graphical (cpFOCE) approaches; science users use a lot of Matlab, where they tend to use procedural methods(?)\\ Will hopefully get some more data on this as time goes by. | | Licensing | ? | ? | ? | No large advantage for any choice. Java is somewhat harder to integrated into a rootfs image using the openembedded tools. Because it can't be automatically downloaded by bitbake, I think it introduces some manual steps in the rootfs  build process. | | Exportability exemplars | ?? | ? | ??? | SIAM, OASIS, PUCK, FOCE; OASIS has more successful exports, and is of similar scope and scale to FOCE. \\ cpFOCE used LabView, eFOCE uses Arduino Processing/Wiring language (not C+\+ bindings)\\ Cawthron (OASIS) users expressed preference for C over Java | | Verbosity/readability | ??? | ?? | ? | Overall, It may take more lines of code to get the same job done in C than Java, though it depends on the job. | | Application Domain | ? | ?? | ??? | Some would assert that C is better for system and hardware code, Java/C+\+ better for application code.\\ xFOCE is evenly distributed across the stack, but leans a little to the hardware side. The shore side is in the application domain (and can be decoupled through message passing architecture). | | xFOCE code developers' preference | ?? | ? | ??? | We are divided on this: one with a strong preference for an OO language (preferably Java), one for Java, three for C. | | Likely implementer background | ? | ? | ? | Electro-mechanical person w/ some software experience in a high level language (C, Java or similar) - we think. \\ \\ This is a difficult criteria to apply, because it is unknown and we have little past data to make inferences from. | | Likely operator background | ?? | ? | ??? | Familiar with Matlab, maybe Fortran, C.\\ This is a difficult criteria to apply, yada yada... | | Most taught In schools | ? | ? | ? | for which curriculum (CS, ME, EE, Robotics)? Based on what data? Hard to measure and understand importance, so not a good criteria | | Currency of language | ?? | ? | ??? | Procedural programming and OO are both valid, contemporary approaches. Several sources say that that C is still more popular than Java. It is possible to write well organized, extensible code using either; we should select the approach that is most likely to make xfoce users successful based on business and technical criteria, even if it is different from what we are most familiar with.\\ There is not consensus about this: one developer expressed that Using C and not taking advantage of modern (OO) approaches and tools would be setting us back 20 years and we would be less productive.\\ It is difficult to determine what the most used language is. It is easy to find surveys based on search results; these indicate that C, Java and C+\+ would be the top three contenders. It is easy to find articles and blog posts with any answer you'd care to find. \\ All could be appropriate choices for FOCE. | | It is more likely that Java programmers would be familiar with C than vice versa | ? | ? | ? | Many Java programmers learned C or another procedural language as their first programming language. | | Other embedded applications at MBARI | ?? | ? | ??? | Many embedded data collection systems us primarily e C/C++: Tiburon, OASIS, Dorado, PUCK, LRAUV, Autonomy, DataManager, Benthic Respirometer\\ Many of the data systems use Java: SSDS, VARS, ODSS, FOCE GUI\\ SIAM uses Java (a notable exception among embedded data collection system)\\ ESP uses C/C+\+ and Ruby\\ There are several projects that use LabView: MiniROV, Benthic ecology aquaria(?)\\ \\ It may be useful to use Java clients and components for swFOCE on the shore to interface with xFOCE; a message passing architecture will decouple the gateway language choice from the data system. |]]> 19041217 19073910 19041220 19073911 19041221 19073826 19041135 19073831 {noformat}\\ \\]]> 19041140 19073833 New... ** continue w/o disc ** create custom virtual machine ** Insert CD ** Use operating system installation disc or image ** choose CD drive ** Choose operating system (should show Linux, Ubuntu) ** Select "Use Easy Install" ** enter account name and password ** Select "Make home folder accessible to virtual machine" ** Select read/write permissions ** Download VMWare tools for Linux guest if prompted ** Select finish or customize settings ** Default 1 GB RAM, 20 GB HDD ** shows Ubuntu VMWare guest window; select Play symbol icon ** Automatically installs Ubuntu from CD...(Control-Command to release mouse) ** Reboots to desktop login screen ** Allow update manager to update ** /mnt/hgfs mounts shared Mac User home directory]]> 19041142 19073828 19041137 19073830 19041139 4489281 4456518 4489279 4456516 4489278 4456515 4489224 4456456 4489232 4456464 4489233 4456465 4489227 4456459 4489228 4456460 19074022 19041336 3964929 3932161 4489283 4456520 4489285 4456522 4489287 4456524 5308448 property=value* Comments on the command: **  ]]> 5275680 9831026 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Update /etc/ntp.conf to point to MBARI time servers.  You can get it [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/ntp.conf] * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11 (or S19 for two serial boards). * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: *  /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. NTP On the deployed system, NTP wasn't peering with the time servers, as evidenced by 'ntpq \-p'.  This time around, it seems to be working fine.  But if you have this problem, you need to install NTP later in the init cycle, as follows: *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local h5. [You're now ready to install Java and SIAM.|https://oceana.mbari.org/confluence/display/FOCE/Installing+SIAM+and+FOCE+on+FOCE+Stack]]]> 9798273 9831035 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml (?) This checkout command should expand keywords with the -kko option -- John needs to look this up though. h5. Configure SIAM pieces * cp properties/siamPorts.cfg.foce properties/siamPorts.cfg (i) You may have to edit the siamPorts.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, edit the top-level Makefile to point to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce (i) It isn't clear that the foce Makefile is complete. If there is any doubt, it is always a good idea to run 'make clean', to make sure you really have a clean build. {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps -ef | grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & Look at these [user notes|https://oceana.mbari.org/confluence/display/FOCE/User+Documentation] on running FOCE.]]> 9798282 9831038 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml (?) This checkout command should expand keywords with the -kko option -- John needs to look this up though. h5. Configure SIAM pieces * cp properties/siamPorts.cfg.foce properties/siamPorts.cfg (i) You may have to edit the siamPorts.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, edit the top-level Makefile to point to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce (i) It isn't clear whether the foce Makefile is complete. If there is any doubt, it is always a good idea to run 'make clean', to make sure you really have a clean build. {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps -ef | grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & Look at these [user notes|FOCE:User Documentation] on running FOCE.]]> 9798285 9831040 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml h5. Configure SIAM pieces * cp properties/siamPort.cfg.foce properties/siamPort.cfg (i) You may have to edit the siamPort.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, confirm the top-level Makefile points to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce (i) It isn't clear whether the foce Makefile is complete. If there is any doubt, it is always a good idea to run 'make clean', to make sure you really have a clean build. {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps -ef | grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & Look at these [user notes|FOCE:User Documentation] on running FOCE.]]> 9798287 5308422 5275655 9831028 devel->main', and add: ** autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * 'Not Installed Packages->net->main, add ntp and ntpdate. Install. (Added 23may2008, rah) ** Update /etc/ntp.conf to point to MBARI time servers.  You can get it [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/ntp.conf] * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. 4) Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. 5) Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11 (or S19 for two serial boards). * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: *  /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. 6) NTP On the deployed system, NTP wasn't peering with the time servers, as evidenced by 'ntpq \-p'.  This time around, it seems to be working fine.  But if you have this problem, you need to install NTP later in the init cycle, as follows: *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local h5. [You're now ready to install Java and SIAM.|https://oceana.mbari.org/confluence/display/FOCE/Installing+SIAM+and+FOCE+on+FOCE+Stack]]]> 9798275 3964956 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port.]]> 3932189 3964958 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port.]]> 3932191 5407490 5374760 3964947 3932180 5407489 5374759 5407488 5374758 5407486 5374756 3964931 3932163 3964932 3932164 3964933 3932165 3964934 3932166 3964936 3932168 3964937 3932169 5407450 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking)]]> 5374719 4227073 4194305 5407421 5374690 3670862 3638123 9404656 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready.\\]]> 9371907 9404662 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. \\]]> 9371913 9404660 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. \\]]> 9371911 9404666 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. /boot/config-$KERNEL * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. \\]]> 9371917 9404664 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. \\]]> 9371915 9404668 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: *  /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules /boot/config-$KERNEL * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. \\]]> 9371919 16449606 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.162 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.162.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node, set the IP address to 134.89.42.127.  For connection to the WNS (wet-node simulator), change it to 134.89.52.127. h6. Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)".  You can use that to associate the Windows COMx serial port names with the PortServer port numbers.  I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: * The first serial port (PortServer Port 1) is connected to the Insite Camera.  You can see from the Device Manager that this is mapped to COM2. * The second serial port (PortServer Port 2) is connected to the PC/104 stack.  In this example, this is COM15.  This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. * The third and fourth serial ports are unused (I think). h6.]]> 16416842 19074305 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk. *Use dd to write SD card* *\[mac\]* * Insert SD card in slot or card reader * Use diskutil as root to find device: {code} $ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS mbari1633 499.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI 209.7 MB disk1s1 2: Apple_HFS SuperDuper 500.3 GB disk1s2 3: Apple_HFS TimeMachine 499.4 GB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *2.0 GB disk2 1: DOS_FAT_16 NO NAME 2.0 GB disk2s1 {code} * Unmount the SD card volume: {code} $ sudo diskutil unmountDisk /dev/disk2 Password: Unmount of all volumes on disk2 was successful {code} * Use dd to {code} $ sudo dd if=sdcard-ide2G.img of=/dev/disk2 {code} *\[linux\]* ]]> 19041624 19074304 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk. *Use dd to write SD card* *\[mac\]* * Insert SD card in slot or card reader * Use diskutil as root to find device: {code} $ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS mbari1633 499.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI 209.7 MB disk1s1 2: Apple_HFS SuperDuper 500.3 GB disk1s2 3: Apple_HFS TimeMachine 499.4 GB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *2.0 GB disk2 1: DOS_FAT_16 NO NAME 2.0 GB disk2s1 {code} * Unmount the SD card volume: {code} $ sudo diskutil unmountDisk /dev/disk2 Password: Unmount of all volumes on disk2 was successful {code} * Use dd to {code} $ sudo dd if=sdcard-ide2G.img of=/dev/disk2 {code} * that's it ]]> 19041623 19074301 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk. Use dd to write SD card [mac] * Insert SD card in slot or card reader * Use diskutil as root to find device: {code} $ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS mbari1633 499.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI 209.7 MB disk1s1 2: Apple_HFS SuperDuper 500.3 GB disk1s2 3: Apple_HFS TimeMachine 499.4 GB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *2.0 GB disk2 1: DOS_FAT_16 NO NAME 2.0 GB disk2s1 {code} * Unmount the SD card volume: {code} $ sudo diskutil unmountDisk /dev/disk2 Password: Unmount of all volumes on disk2 was successful {code} * Use dd to {code} $ sudo dd if=sdcard-ide2G.img of=/dev/disk2 {code} * that's it ]]> 19041620 19074302 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk. *Use dd to write SD card* [mac] * Insert SD card in slot or card reader * Use diskutil as root to find device: {code} $ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS mbari1633 499.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI 209.7 MB disk1s1 2: Apple_HFS SuperDuper 500.3 GB disk1s2 3: Apple_HFS TimeMachine 499.4 GB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *2.0 GB disk2 1: DOS_FAT_16 NO NAME 2.0 GB disk2s1 {code} * Unmount the SD card volume: {code} $ sudo diskutil unmountDisk /dev/disk2 Password: Unmount of all volumes on disk2 was successful {code} * Use dd to {code} $ sudo dd if=sdcard-ide2G.img of=/dev/disk2 {code} * that's it ]]> 19041621 19074300 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk.]]> 19041619 16449652 16416889 16449666 16416903 16449650 16416887 4653057 4685825 2008-05-30 08:25:05.573 2008-05-30 08:25:05.573 4653058 4685825 2008-05-30 08:25:06.017 2008-05-30 08:25:06.017 3407887 2008-03-18 09:16:34.097 2010-04-28 08:59:20.267 10388826 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.162.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node or wet-node simulator, set the IP address to 134.89.42.117. h6. Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)".  You can use that to associate the Windows COMx serial port names with the PortServer port numbers.  I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: * The first serial port (PortServer Port 1) is connected to the Insite Camera.  You can see from the Device Manager that this is mapped to COM2. * The second serial port (PortServer Port 2) is connected to the PC/104 stack.  In this example, this is COM15.  This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. * The third and fourth serial ports are unused (I think). h6.]]> 10356100 3670605 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port.]]> 3637856 10388824 10356098 10388829 10356103 10388831 10356105 7798895 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node or wet-node simulator, set the IP address to 134.89.42.117. h6. Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)".  You can use that to associate the Windows COMx serial port names with the PortServer port numbers.  I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: * The first serial port (PortServer Port 1) is connected to the Insite Camera.  You can see from the Device Manager that this is mapped to COM2. * The second serial port (PortServer Port 2) is connected to the PC/104 stack.  In this example, this is COM15.  This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. * The third and fourth serial ports are unused (I think). h6.]]> 7766131 3670640 3637889 3670639 3637888 3670642 3637891 3670636 3637885 3670635 3637884 3670637 3637886 3670656 3637906 3670657 3637907 3670658 3637908 3670654 3637903 3670648 3637897 3670643 3637892 3670644 3637893 3670645 3637894 3670646 3637895 3670661 3637911 9404704 9371955 9404703 9371954 3670660 3637910 9404701 9371952 9404699 9371950 9404698 9371949 3670669 3637919 9404697 9371948 9404695 9371946 3670673 3637923 9404693 9371944 3670674 3637924 9404691 9371942 9404689 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Update /etc/ntp.conf to point to MBARI time servers.  You can get it [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/ntp.conf] * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11 (or S19 for two serial boards). * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: *  /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. NTP On the deployed system, NTP wasn't peering with the time servers, as evidenced by 'ntpq \-p'.  This time around, it seems to be working fine.  But if you have this problem, you need to install NTP later in the init cycle, as follows: *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local You're now ready to install Java and SIAM. \\ h5.  ]]> 9371940 3670675 3637925 3670682 3637933 9404686 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: *  /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. h5. h5. *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. You're now ready to install Java and SIAM.\\ h5.  ]]> 9371936 11829496 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. 6) Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. 7) Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. 8) Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml h5. Configure SIAM pieces * cp properties/siamPort.cfg.foce properties/siamPort.cfg (i) You may have to edit the siamPort.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, confirm the top-level Makefile points to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce (i) It isn't clear whether the foce Makefile is complete. If there is any doubt, it is always a good idea to run 'make clean', to make sure you really have a clean build. {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. 9) Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps -ef | grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & h2. For more information on running FOCE, see this [user documentation|FOCE:User Documentation].]]> 11796739 9404756 9372008 9404760 9372012 5407494 5374764 9404787 9372041 5407492 5374762 11829467 11796710 6226567 6259364 6226569 6259366 6226564 6259361 6226576 6259373 6226574 6259371 6226584 6259381 7405570 7372802 6226593 6259390 6226587 6259384 6226589 6259386 6226590 6259387 6226601 Camera Settings, and set it up like this: !AxisCamera.PNG|thumbnail! * We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. * To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this: !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail!    ]]> 6259398 6226599 Camera Settings, and set it up like this: !AxisCamera.PNG|thumbnail! * We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. * To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this: !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail!    ]]> 6259396 6226597 Camera Settings, and set it up like this: !AxisCamera.PNG|thumbnail! * We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. *  ]]> 6259394 6226595 Camera Settings, and set it up like this: !AxisCamera.PNG|thumbnail!  ]]> 6259392 6226609 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node or wet-node simulator, set the IP address to 134.89.42.117. h6. Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)".  You can use that to associate the Windows COMx serial port names with the PortServer port numbers.  I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: * The first serial port (PortServer Port 1) is connected to the Insite Camera.  You can see from the Device Manager that this is mapped to COM2. * The second serial port (PortServer Port 2) is connected to the PC/104 stack.  In this example, this is COM15.  This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. * The third and fourth serial ports are unused (I think). h6.]]> 6259406 6226607 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node or wet-node simulator, set the IP address to 134.89.42.117. h6. Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)".  You can use that to associate the Windows COMx serial port names with the PortServer port numbers.  I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: * The first serial port (PortServer Port 1) is connected to the Insite Camera.  You can see from the Device Manager that this is mapped to COM2. * The second serial port (PortServer Port 2) is connected to the PC/104 stack.  In this example, this is COM15.  This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. * The third and fourth serial ports are unused (I think).   h6.  ]]> 6259404 6226606 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail!For connection to the MARS node or wet-node simulator, set the IP address to 134.89.42.7 \\]]> 6259403 6226604 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node or wet-node simulator, set the IP address to 134.89.42.7\\]]> 6259401 6226603 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this: !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail!    ]]> 6259400 3670279 3637524 3670276 3637521 3670275 3637520 15663619 15630865 15663620 15630866 8945998 8913245 5406751 property=value* Comments on the command: **  You must not have any space around the = sign ** *loc* is again short for localhost ** ** needs to be identified by the serial or analog port.  E.g., the external CTD is /dev/ttyS4.  The pH sensor can be identified just as '*pH*']]> 5373988 6226527 6259324 9405001 property=value* Comments on the command: ** You must not have any space around the = sign ** *loc* is again short for localhost ** ** needs to be identified by the serial or analog port. For example, the external CTD is /dev/ttyS4. The single pH sensor can be identified just as '*pH*', but individual pH sensors must be identified as pH0, pH1, pH2, or pH3. * To learn what instruments are registered, you can use the command *showRegistry loc* ]]> 9372265 9404996 9372260 11272487 devel->main', and add: ** autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * 'Not Installed Packages->net->main, add ntp and ntpdate. Install. (Added 23may2008, rah) ** Update /etc/ntp.conf to point to MBARI time servers.  You can get it [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/ntp.conf] * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** apt-get install ethtool net-tools (Added 9jun2008, rah) h5. 4) Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. 5) Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11 (or S19 for two serial boards). * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: * /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. 6) NTP On the deployed system, NTP wasn't peering with the time servers, as evidenced by 'ntpq \-p'.  This time around, it seems to be working fine.  But if you have this problem, you need to install NTP later in the init cycle, as follows: *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local h5. [You're now ready to install Java and SIAM.|FOCE:Installing SIAM and FOCE on FOCE Stack]]]> 11239724 9405005 9372269 5406759 property=value* Comments on the command: **  You must not have any space around the = sign ** *loc* is again short for localhost ** ** needs to be identified by the serial or analog port.  E.g., the external CTD is /dev/ttyS4.  The pH sensor can be identified just as '*pH*']]> 5373996 9404982 9372245 9404980 9372243 9404985 9372248 9404984 9372247 9404989 9372253 9404987 9372250 9404994 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Update /etc/ntp.conf to point to MBARI time servers.  You can get it [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/ntp.conf] * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11 (or S19 for two serial boards). * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: *  /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. NTP On the deployed system, NTP wasn't peering with the time servers, as evidenced by 'ntpq \-p'.  This time around, it seems to be working fine.  But if you have this problem, you need to install NTP later in the init cycle, as follows: *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local h5. [You're now ready to install Java and SIAM.|https://oceana.mbari.org/confluence/display/FOCE/Installing+SIAM+on+FOCE+Stack]]]> 9372258 9404993 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Update /etc/ntp.conf to point to MBARI time servers.  You can get it [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/ntp.conf] * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Prepare Linux Sources We need to prepare the Linux sources to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 24, and "Number of serial ports to register at run time" to 20 (to support two octal serial boards). h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy the Linux2.6 drivers (bhtnpciu-2.6.18v2.tar.gz) from the ConnectTech Xtreme/104-Plus CD to /usr/src/xtreme104.  You can get this file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/bhtnpciu-2.6.18v2.tar.gz]. * Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Make backup copies of directories drivers/serial and include/linux, so you can undo the patching in the next step, if necessary. ** cd drivers; cp \-r serial serial.save ** cd ../include; cp \-r linux linux.save ** cd .. * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch \| tee patch.out * Look at the patch.out file generated above to verify that the patch succeeded. * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** Note that the second "foce.1.1" is preceded by a minus sign. * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11 (or S19 for two serial boards). * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. The intent is that if you need to build additional kernels for any reason, you'll follow the 'make-kpkg' and 'dpkg' commands above, replacing "foce.1.1" with "foce.1.2", "foce.1.3", etc, for subsequent builds.  For each kernel you build (denoted here as $KERNEL), this process generates: *  /boot/config-$KERNEL * /boot/initrd-$KERNEL * /boot/System.map-$KERNEL * /boot/vmlinuz-$KERNEL * A directory named /lib/modules/$KERNEL * /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. NTP On the deployed system, NTP wasn't peering with the time servers, as evidenced by 'ntpq \-p'.  This time around, it seems to be working fine.  But if you have this problem, you need to install NTP later in the init cycle, as follows: *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local h5. [You're now ready to install Java and SIAM.|https://oceana.mbari.org/confluence/display/FOCE/Installing+SIAM+on+FOCE+Stack]]]> 9372257 9404991 9372255 9404949 property=value* Comments on the command: **  You must not have any space around the = sign ** *loc* is again short for localhost ** ** needs to be identified by the serial or analog port.  E.g., the external CTD is /dev/ttyS4.  The pH sensor can be identified just as '*pH*']]> 9372211 3670120 3637361 3670122 3637364 3670124 3637366 3670123 3637365 3670125 3637367 3670128 3637370 3670127 3637369 3670130 3637372 3670129 3637371 3670132 3637374 3670134 3637376 3670135 3637377 3670136 3637378 3670137 3637379 3670138 3637380 3670139 3637381 3670141 3637383 3670143 3637385 3670145 3637387 3670089 3637327 3670092 3637330 3670111 3637352 3670253 3637498 3670254 3637499 3670255 3637500 3670256 3637501 3670245 3637490 3670246 3637491 3670247 3637492 3670249 3637494 3670250 3637495 3670268 3637513 3670272 3637517 3670274 3637519 3670262 3637507 3670264 3637509 3670263 3637508 3670220 3637466 3670225 3637471 3670223 3637469 3670213 3637458 3670214 3637459 3670211 3637456 3670217 3637462 3670218 3637463 3670238 3637483 3670237 3637482 3670236 3637481 3670241 3637486 3670240 3637485 3670227 3637473 3670192 3637436 3670194 3637438 3670187 3637429 3670190 3637434 3670183 3637425 3670185 3637427 3670180 3637422 3670182 3637424 18645006 18579470 18645008 18579472 3670195 3637439 3670161 3637403 3670162 3637404 3670158 3637400 3670155 3637397 3670156 3637398 3670153 3637395 3670154 3637396 3670152 3637394 3670150 3637392 3670147 3637389 3670148 3637390 3670178 3637420 3670176 3637418 3670174 3637416 3670173 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications \\ \\ | *Parameter* | *Values* | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations   !HE104_plus_dx_conn_loc.JPG|align=left!                      \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ h1. Links [Datasheet|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Docs/Data%20Sheets/he104_plus_dx_spec.pdf] \\ [User's Manual|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Docs/Manuals/he104_plus_dx_man.pdf] \\ ]]> 3637415 3670172 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications \\ \\ | *Parameter* | *Values* | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3637414 3670170 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ---- \\ \\ | *Parameter*| *Values*| | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3637412 3670169 3637411 3670167 3637409 3670166 3637408 3670164 3637406 19073069 19040367 19073067 19040365 19073073 19040371 19073071 19040369 19073065 19040363 19073077 19040375 19073082 19040380 19073079 19040377 3179706 3114226 3179705 3114225 3179704 3114224 3179703 3114223 3179702 3114222 3179700 3114220 3179699 3114219 3179713 3114235 3179712 3114234 3179710 3114232 3179707 3114228 3179690 3114210 3179687 3114207 3179688 3114208 3179685 3114205 12550219 12484683 3179697 3114217 12550217 12484681 3179695 3114215 3179694 3114214 3179692 3114212 3179732 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ---- * *\|\ | Parameter | Values | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\  \\  \\  \\ | h1. Connector Locations ----     !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114257 3179731 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ---- * *|| Parameter || Values || | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H |          h1. Connector Locations ----       !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114256 3179734 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ----\\ | *Parameter* | *Values* | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114259 3179733 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ---- * * | Parameter | Values | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H |   \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114258 3179736 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ---- \---\- \\ | *Parameter* | *Values* | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114261 3179735 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications \---\- \\ | *Parameter* | *Values* | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114260 3179738 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications \---\- \\ \| *Parameter* \| *Values* \| | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114263 3179737 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ----\\ | *Parameter* | *Values* | | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114262 3179739 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ---- \---\- \\ \| *Parameter* \| *Values* \| | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114264 3179741 3114266 3179743 3114268 3179745 3114270 3179716 3114239 3179717 3114240 3179720 3114244 3179722 3114246 3179723 3114247 3179725 3114249 3179727 3114251 3179728 3114253 3179729 3114254 3179766 3114291 3179765 3114290 3179764 3114289 3179763 3114288 3179769 3114294 3179767 3114292 3179773 3114298 3179771 3114296 3179777 3114302 3179775 3114300 3179750 3114275 3179747 3114272 3179748 3114273 3179753 3114278 3179751 3114276 3179757 3114282 3179755 3114280 3179761 3114286 3179759 3114284 19073210 19040509 19073207 19040506 19073208 19040507 10387673 @moonjelly:/home/cvs - /home/ops/scripts/minimalCheckout [note: this takes a long time] - mv /home/ops/build/siam2 /home/ops/build/siam2- h2. Make - . /home/ops/scripts/siam-env /home/ops/build/ [note: source siam-env; note the dot] - cd /home/ops/build/ - mkdir classes - make -s [note: this takes 20-30 min, you'll only see errors and warnings (there are many harmless warnings)] - cd /native/foce - make foceio - make testSensoray - cd /home/ops/build/siam2- - cvs -Q co puckxml - make focepucks (note: 1731.xml is missing; I've been copying junk.xml to 1731.xml) - cp properties/siamPort.cfg.foce properties/siamPort.cfg h2. To install: - exitNode loc - cp /home/ops/siam2 /home/ops/siam2- - mv /home/ops/build/siam2- /home/ops/siam2]]> 10354908 10387676 [note: source siam-env; note the dot] - /home/ops/scripts/minimalCheckout [note: this takes a long time] - -mv /home/ops/build/siam2 /home/ops/build/siam2-\- Now done by minimalCheckout h2. Make - *.* /home/ops/scripts/siam-env /home/ops/build/ [note: source siam-env; note the dot] - cd /home/ops/build/ - mkdir classes if it doesn't exist - make \-s [note: this takes 20-30 min, you'll only see errors and warnings (there are many harmless warnings)] - cd /native/foce - make foceio - make testSensoray - cd /home/ops/build/siam2- - cvs \-Q co puckxml - make focepucks -(note: 1731.xml is missing; I've been copying junk.xml to 1731.xml)- - cp properties/siamPort.cfg.foce properties/siamPort.cfg h2. To install: - exitNode loc - cp /home/ops/siam2 /home/ops/siam2- - mv /home/ops/build/siam2- /home/ops/siam2]]> 10354911 10387675 [note: source siam-env; note the dot] - /home/ops/scripts/minimalCheckout [note: this takes a long time] - -mv /home/ops/build/siam2 /home/ops/build/siam2-- Now done by minimalCheckout h2. Make - *.* /home/ops/scripts/siam-env /home/ops/build/ [note: source siam-env; note the dot] - cd /home/ops/build/ - mkdir classes - make \-s [note: this takes 20-30 min, you'll only see errors and warnings (there are many harmless warnings)] - cd /native/foce - make foceio - make testSensoray - cd /home/ops/build/siam2- - cvs \-Q co puckxml - make focepucks (note: 1731.xml is missing; I've been copying junk.xml to 1731.xml) - cp properties/siamPort.cfg.foce properties/siamPort.cfg h2. To install: - exitNode loc - cp /home/ops/siam2 /home/ops/siam2- - mv /home/ops/build/siam2- /home/ops/siam2]]> 10354910 19073211 19040510 10387677 [note: source siam-env; note the dot] - /home/ops/scripts/minimalCheckout [note: this takes a long time] - -mv /home/ops/build/siam2 /home/ops/build/siam2-\- Now done by minimalCheckout h2. Make - *.* /home/ops/scripts/siam-env /home/ops/build/ [note: source siam-env; note the dot] - cd /home/ops/build/ - mkdir classes if it doesn't exist - make \-s [note: this takes 20-30 min, you'll only see errors and warnings (there are many harmless warnings)] - cd /native/foce - make foceio - make testSensoray - cd /home/ops/build/siam2- - cvs \-Q co puckxml - mkdir ports if it doesn't exist - make focepucks -(note: 1731.xml is missing; I've been copying junk.xml to 1731.xml)- - cp properties/siamPort.cfg.foce properties/siamPort.cfg h2. To install: - exitNode loc - cp /home/ops/siam2 /home/ops/siam2- - mv /home/ops/build/siam2- /home/ops/siam2]]> 10354912 19073265 19040564 19073263 19040562 3179606 3114126 3179607 3114127 19073261 19040560 19073273 19040572 3179595 3114113 19073271 19040570 3179597 3114115 19073269 19040568 3179600 3114118 3179599 3114117 19073267 19040566 3179602 3114121 19073281 19040580 19073279 19040578 19073277 19040576 19073275 19040574 3179593 3114111 3179645 3114165 3179643 3114163 3179647 3114167 3179637 3114157 3179635 3114155 3179641 3114161 3179639 3114159 3179634 3114154 3179622 3114141 3179621 3114140 3179626 3114145 3179625 3114144 3179624 3114143 3179623 3114142 3179913 3114441 19073339 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM ** The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window ** A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any current mounts are NOT the new virtual disk. Be careful not to accidentally partition or format the volume used by the Linux VM instead *Partition and format virtual disk as SD card* The resulting *  ]]> 19040642 19073342 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume the virtual disk is /dev/sda. As root, do the following: {code} # umount /dev/sda # fdisk /dev/sda {code}]]> 19040645 3179911 3114439 19073341 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions: * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data]]> 19040644 3179909 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!]]> 3114437 19073343 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume the virtual disk is /dev/sda. As root, do the following: {code} # fdisk /dev/sda {code}]]> 19040646 3179907 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.\\]]> 3114435 19073345 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume the virtual disk is /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda   {code}]]> 19040648 3179922 3114450 19073334 Hard Disk > Add Device...  * Set Disk Size ** May use same size as targeted device (SD Card, USB stick), e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity Advanced *  ]]> 19040637 3179920 3114448 3179917 3114445 19073335 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file]]> 19040638 19073337 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file]]> 19040640 3179916 3114444 19073324 19040627 19073325 19040628 19073329 Hard Disk > Add Device... \\]]> 19040632 3179924 3114452 3179923 3114451 19073316 19040619 3179936 3114464 19073318 /arm-linux-gnu distclean $ make phy3250_config $ make ARCH=arm CROSS_COMPILE=/arm-linux-gnu\-     •    Once the build completes, the u-boot binary image for deployment can be found at uboot/u-boot-2009.03/u-boot.bin]]> 19040621 19073320 /arm-linux-gnu distclean $ make phy3250_config $ make ARCH=arm CROSS_COMPILE=/arm-linux-gnu\-     •    Once the build completes, the u-boot binary image for deployment can be found at uboot/u-boot-2009.03/u-boot.bin\\ ======== A working u-boot config \[will need to change IP addresses, etc. - it is possible to use DHCP\] ======== To enter U-Boot, hit a key during the u-boot loader sequence. Useful commands: * printenv * setenv\\ uboot> printenv bootdelay=3 baudrate=115200 rootpath=/home/user/ltib/rootfs loadaddr=0x80100000 nfsboot=setenv bootargs console=ttyS0,115200n8 root=/dev/nfs3 rw nfsroot=${serverip}:${rootpath} ip=${ipad dr} ethaddr=${ethaddr} ramdiskboot=setenv bootargs console=ttyS0,115200n8 root=/dev/ram0 rw ip=${ipaddr} ethaddr=${ethaddr} tftpstatickernel=tftpboot ${loadaddr} ${serverip}:${bootfile} tftpdhcpkernel=dhcp mtdkernel=nboot.jffs2 ${loadaddr} 0 0x00204000 mtdkernelburn=nand erase 0x00204000 0x00400000;nand write.jffs2 ${loadaddr} 0x00204000 0x00400000 rootfile=rootfs.jffs2 rootloadaddr=0x82000000 tftpstaticloadroot=tftpboot ${rootloadaddr} ${serverip}:${rootfile} tftpdhcploadroot=dhcp ${rootloadaddr} ${serverip}:${rootfile} ramdiskload=nand read.jffs2 ${rootloadaddr} 0x00604000 ${rootloadsize} bootargs=console=ttyS0,115200n8 root=/dev/nfs3 rw nfsroot=192.168.1.41:/home/user/ltib/rootfs ip=192.168.1 .101 ethaddr=00:50:C2:A5:BB:A8 autoload=no bootfile=uImage bootcmd=run mtdboot; run mtdkernel; bootm $(loadaddr) mtdboot=setenv bootargs console=ttyS0,115200n8 root=/dev/mtdblock4 rw rootfstype=jffs2 ip=134.89.11.120 in it=/sbin/init ethaddr=00:50:C2:A5:BB:A8 mtdrootburn=nand erase 0x00604000 0x039FC000; nand write.jffs2 ${rootloadaddr} 0x00604000 ${rootloadsize} filesize=640000 fileaddr=82000000 gatewayip=134.89.10.1 netmask=255.255.254.0 ipaddr=134.89.11.120 serverip=134.89.11.121 rootloadsize=0x640000 stdin=serial stdout=serial stderr=serial ethaddr=00:50:C2:A5:BB:A8 Environment size: 1466/65532 bytes  ]]> 19040623 3179943 3114471 19073308 New... ** continue w/o disc ** create custom virtual machine ** Insert CD ** Use operating system installation disc or image ** choose CD drive ** Choose operating system (should show Linux, Ubuntu) ** Select "Use Easy Install" ** enter account name and password ** Select "Make home folder accessible to virtual machine" ** Select read/write permissions ** Download VMWare tools for Linux guest if prompted ** Select finish or customize settings ** Default 1 GB RAM, 20 GB HDD ** shows Ubuntu VMWare guest window; select Play symbol icon ** Automatically installs Ubuntu from CD...(Control-Command to release mouse) ** Reboots to desktop login screen ** Allow update manager to update ** /mnt/hgfs mounts shared Mac User home directory]]> 19040610 19073307 19040609 4948033 4915270 3179939 3114467 4948028 4915265 19073313 19040615 19073312 19040614 3179941 3114469 19073302 New... ** continue w/o disc ** create custom virtual machine ** Insert CD ** Use operating system installation disc or image ** choose CD drive ** Choose operating system (should show Linux, Ubuntu) ** Select "Use Easy Install" ** enter account name and password ** Select "Make home folder accessible to virtual machine" ** Select read/write permissions ** Download VMWare tools for Linux guest if prompted ** Select finish or customize settings ** Default 1 GB RAM, 20 GB HDD ** shows Ubuntu VMWare guest window; select Play symbol icon ** Automatically installs Ubuntu from CD...(Control-Command to release mouse) ** Reboots to desktop login screen ** Allow update manager to update ** /mnt/hgfs mounts shared Mac User home directory]]> 19040604 19073301 19040603 19073299 19040601 19073304 New... ** continue w/o disc ** create custom virtual machine ** Insert CD ** Use operating system installation disc or image ** choose CD drive ** Choose operating system (should show Linux, Ubuntu) ** Select "Use Easy Install" ** enter account name and password ** Select "Make home folder accessible to virtual machine" ** Select read/write permissions ** Download VMWare tools for Linux guest if prompted ** Select finish or customize settings ** Default 1 GB RAM, 20 GB HDD ** shows Ubuntu VMWare guest window; select Play symbol icon ** Automatically installs Ubuntu from CD...(Control-Command to release mouse) ** Reboots to desktop login screen ** Allow update manager to update ** /mnt/hgfs mounts shared Mac User home directory]]> 19040606 19073294 New...     \- continue w/o disc     \- create custom virtual machine     \- Insert CD     \- Use operating system installation disc or image         \- choose CD drive     \- Choose operating system (should show Linux, Ubuntu)     \- Select "Use Easy Install"     \- enter account name and password     \- Select "Make home folder accessible to virtual machine"     \- Select read/write permissions     \- Download VMWare tools for Linux guest if prompted     \- Select finish or customize settings         \- default 1 GB RAM, 20 GB HDD     \- shows Ubuntu VMWare guest window; select Play symbol icon     \- Automatically installs Ubuntu from CD...(Control-Command to release mouse)     \- Reboots to desktop login screen     \- Allow update manager to update     \- /mnt/hgfs mounts shared Mac User home directory]]> 19040595 19073292 19040593 19073297 19040599 19073298 19040600 19073295 19040596 19073285 19040584 19073286 19040585 19073283 19040582 3179971 3114501 4948044 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port.]]> 4915281 19202054 2012-08-16 15:51:50.770 2012-08-16 15:51:50.770 19202055 2012-08-16 15:51:50.777 2012-08-16 15:51:50.777 19202056 2012-08-16 15:51:50.777 2012-08-16 15:51:50.777 4948035 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port.]]> 4915272 9830541 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml (?) This checkout command should expand keywords with the -kko option -- John needs to look this up though. h5. Configure SIAM pieces * cp properties/siamPorts.cfg.foce properties/siamPorts.cfg (i) You may have to edit the siamPorts.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, edit the top-level Makefile to point to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce (i) It isn't clear that the foce Makefile is complete. If there is any doubt, it is always a good idea to run 'make clean', to make sure you really have a clean build. {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps -ef | grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & Look at these [user notes|https://oceana.mbari.org/confluence/display/FOCE/User+Documentation] on running FOCE.]]> 9797772 9830540 /rxtx-2.1-7r2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `//rxtx-2.1-7r2' libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory Try `libtool --help --mode=install' for more information. make: *** [install] Error 1 {noformat} To fix this, you must edit the configure script and extend the line: {noformat} 1.2*|1.3*|1.4*|1.5* {noformat} to: {noformat} 1.2*|1.3*|1.4*|1.5*|1.6* {noformat} {note} h4. Install Library for Diamond A/D card (*BASE*) The A/D board is used to read various engineering sensors on FOCE. Get the library, header files, and examples in a tar file [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/dscud-5.92-Linux.tar.gz]. The only thing you need is the library (the header file is already checked into siam2). * tar xzf dscud-5.92-Linux.tar.gz  * cd dscud5 * su root * cp libdscud5.a /usr/local/lib h4. Install /etc/sudoers (*BASE*) This is needed so that some commands in the Makefile can execute. * If /etc/sudoers file does not exist, get a copy [here|https://alfresco.mbari.org/alfresco/webdav/Projects/900719_F_O_C_E/Software/Drivers/sudoers] and... * Copy it to /etc: ** cd /etc; cp [file] /etc/sudoers; chown root sudoers; chgrp root sudoers; chmod 440 sudoers * {color:navy}Add yourself to sudoers if you plan to run make from your own account.{color} {color:gray}You probably won't need this on the Mac, if you have admin privileges.{color} ** {color:navy}Log in as root.{color} ** {color:navy}Run visudo. Add the following line to the end of the sudoers file, replacing acctname with your account name:{color} {color:navy}acctname ALL=/bin/chown,/bin/chmod{color} ** {color:navy}If you can't stand the default editor, do 'export VISUAL=/usr/bin/vi', or your preferred editor. Then redo the visudo command.{color} h4. Install SIAM h5. Obtain code * Log in as ops. Go to ops home directory ** {color:navy}For installing to your own account, log in as yourself and go to the directory where the CVS repository for SIAM will be installed.{color} * cvs checkout siam2 * ln \-s siam2 siam * cd siam * cvs checkout puckxml (?) This checkout command should expand keywords with the -kko option -- John needs to look this up though. h5. Configure SIAM pieces * cp properties/siamPorts.cfg.foce properties/siamPorts.cfg (i) You may have to edit the siamPorts.cfg file after you have copied it, to reflect the components installed on this system. (!) _We need a place to document the components currently installed on the system._ * In the make directory, edit the top-level Makefile to point to make/Makefile.FOCE2009 instead of make/Makefile.FOCE2008. h5. Make the software * make * make focepucks * make foce (i) It isn't clear that the foce Makefile is complete. If there is any doubt, it is always a good idea to run 'make clean', to make sure you really have a clean build. {color:gray}As noted above, you won't be able to 'make foce' successfully on a Mac, since the IO utilities aren't present.{color} h4. Run FOCE h5. Verify FOCE isn't already running You should make sure FOCE isn't running already (if it is, your execution will abort with an error). To check this, enter 'ps -ef | grep FOCEnode' to search for the FOCE process. h5. Start up FOCE You can run FOCE with or without publishing to SSDS. For testing, use the first method without publishing the data to SSDS.  For deployment, use the second method * Method 1: not publishing ** gosiam _(this goes to the SIAM home directory)_ ** foce & *OR* * Method 2: publishing (usually done only when publishing is being tested) ** gosiam ** foce \-publish & Look at these [user notes|https://oceana.mbari.org/confluence/display/FOCE/User+Documentation] on running FOCE.]]> 9797771 9830539 9797770 9830537 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * (Added 23may2008, rah) 'Not Installed Packages->net->main, add ntp and ntpdate. Install. ** Get an appropriate /etc/ntp.conf from IS.  I have one in my NIS directory, bobh * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) ** (Added 9jun2008, rah) apt-get install ethtool net-tools h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc. h5. Add Support for ConnectTech Xtreme/104-Plus Octal UART Board * mkdir /usr/src/xtreme104 * Copy contents from the ConnectTech Xtreme/104-Plus CD to a NFS-mounted drive.Go to Drivers/Linux26, and copy the driver (bhtnpciu-2.6.18.tar.gz) to /usr/src/xtreme104.  Untar the file there. * Follow the instructions in the README file there, including the following steps: * cd /usr/src/linux-source.2.6.18 * Save the drivers/serial directory to drivers/serial.save  (Note \-\- apparently the patch touches more than this.  Fortunately, I also have a copy of the entire /usr/src/linux-source.2.6.18 in an NFS directory). * patch \-p1 < ../xtreme104/bhtnpciu-2.6.18/bhtnpciu-2.6.18.patch * Per the README, 'make menuconfig' and verify the options they list are set.  This was done above, and checked to be OK. * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.2 \--append-to-version=-foce.1.2 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.2_foce.1.2_i386.deb * Reboot * I thought this didn't work.  But that's because I moronically forgot to install the board.  So I went back to the README, and changed both "Maximum number of 8250/16550 serial ports" and "Number of serial ports to register at run time" to 128, per README, and rebuilt as foce.1.3 * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.3_foce.1.3_i386.deb * Reboot * Verify that we have serial support via 'dmesg \| grep tty'.  It should show ttyS4 through ttyS11. * Use minicom to test each serial port.  They work\!  But you need to exit & reenter minicom when you change the serial port. h5. Force 10baseT operation on Ventana (not needed for MARS?) * As root, copy my init script to /etc/init.d/force10baseT * Run ' update-rc.d force10baseT defaults 18' * (Note - level 18 ensures it's run early enough to take effect before other scripts that rely on networking) *The network is not ready (still initializing?) by the time the NTP script executes.  So you now need to:* *  Run 'update-rc.d \-f ntp remove' * Add '/etc/init.d/ntp start' to /etc/rc.local This causes ntp to start later in the initialization cycle, when the network is ready. \\]]> 9797768 19073361 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk.]]> 19040664 19073360 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk.]]> 19040663 19073357 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code}\\ \\ *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code}\\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk. To exit without modifying the partition table, press 'q'. ]]> 19040660 19073358 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code}\\ \\ \\ *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk.]]> 19040661 19073355 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this:\\ \\ {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code}\\ *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code} Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code}]]> 19040658 19073353 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) /dev/sda2 133120 657407 262144 83 Linux]]> 19040656 19073351 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] * - Accept default start sector * '+64M' - Specify partition size Now if you print the partition table, it should look something like this: {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * 'c' - Type '83' \[Linux\] * - Accept default start sector * '+256M' - Specify partition size \\]]> 19040654 19073349 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume the virtual disk is /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. Create a 64 MB boot partition * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * 'c' - Type 'c' \[FAT32\] * - Accept default start sector * '+64M' - Specify partition size\\ \\]]> 19040652 19073347 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume the virtual disk is /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code}\\ If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk]]> 19040650 3179793 3114318 3179791 3114316 3179789 3114314 3179788 3114313 3179786 3114311 3179785 3114310 3179783 3114308 3179781 3114306 3179779 3114304 18285409 18252664 7405571 7372803 7405573 Camera Settings, and set it up like this: *   !AxisCamera.PNG|thumbnail! h6. h6. Anywhere USB We don't have the AnywhereUSB working quite yet.  It should work as follows. Bring up the AnywhereUSB Configuration Utility.  Choose Command->ConfigurationList.  Add 134.89.12.108 to the list.  It should find the USB server and allow you to connect to it. h6. Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC.  This installs as a Windows driver.  To configure RealPort for this configuration, go to Start->Settings->ControlPanel.  Double-click System.  Choose the Hardware tab, and choose Device Manager.  Open up the list item labelled "Multi-port serial adapters".  It should look something like this:  !DeviceManager.PNG|thumbnail! Now look for the "PortServer TS 4", right-click, and open "Properties".  Click the "Advanced" tab, and click on "Properties".  Click on the "Network" tab.  Under "IP address", insert 134.89.12.108.  It should look like this: !PortServerNetwork.PNG|thumbnail! For connection to the MARS node or wet-node simulator, set the IP address to 134.89.42.117. h6. Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)".  You can use that to associate the Windows COMx serial port names with the PortServer port numbers.  I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: * The first serial port (PortServer Port 1) is connected to the Insite Camera.  You can see from the Device Manager that this is mapped to COM2. * The second serial port (PortServer Port 2) is connected to the PC/104 stack.  In this example, this is COM15.  This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. * The third and fourth serial ports are unused (I think). h6.]]> 7372805 18285408 18252663 18285405 18252660 7405575 7372807 18285406 18252661 18285404 18252659 3179801 3114327 3179802 3114328 18285402 18252657 18285399 18252652 18285400 18252653 3179798 3114324 3179839 3114366 3179840 3114367 15761409 2011-01-04 13:13:56.807 2011-09-20 11:35:09.630 3179841 3114368 3179842 3114369 3179835 3114362 3179836 3114363 3179837 3114364 3179838 3114365 9830498 9797729 3179834 3114361 19073528 19040835 19073530 19040837 9830440 9797671 19073524 19040831 9830441 9797672 19073526 19040833 3179846 3114373 3179845 3114372 3179844 3114371 3179843 3114370 3179850 3114377 3179849 3114376 3179848 6:1) and is ideal for battery or unregulated input applications. The HE104+DX is specifically designed for vehicular applications and has heavy-duty transient suppressors (9000W on both main and secondary inputs) that clamp the input voltage to safe levels, while maintaining normal power supply operation. The HE104+DX is a state-of-the-art Mosfet based design that provides outstanding line and load regulation with efficiencies up to 90 percent. Organic Semiconductor Capacitors provide filtering that reduces ripple noises below 20mV. The low noise design makes the HE104+DX ideal for use aboard aircraft or military applications or wherever EMI or RFI must be minimized. The \+5VDC and \+12VDC outputs are controlled by a constant frequency architecture regulator that provides excellent line and load transient response. The HE104+DX has an opto-coupled on/off input (SD) to control the outputs of the HE104+DX. To enable the HE104+DX outputs, a 6 to 40V signal must be connected to the SD input. If remote control is not required, the SD input can be connected to the main power input. The common for the remote 6 to 40V signal must be connected to the HE104+DX common. If the SD input is connected directly to the main input power connector, the common for the SD input is already done. !he104_plus_dx.gif|align=right!\\ h1. Specifications ---- \\ \\ | *Parameter*| *Values*| | 5V Output | 15A | | 12V Output | 3A | | 3.3V Output | 10A | | \-12V Output | 0.5A | | Input Voltage Range | 6 to 40V | | Load Regulation (5V) | <60mV | | Line Regulation | 40mV | | Output Temp. Drift (5V) | <40mV | | Switching Freq. | 75kHz | | Max. Input Transient | 125V for 100msec | | Output Ripple (5V) | <20mV | | Conducted Susceptibility (5V) | >57dB | | Efficiency (5V) | Up to 90% | | Temperature Range | \-40 to \+85C | | Size | 3.55"W x 3.75"L x 0.6"H | \\   \\   \\ h1. Connector Locations ----   !HE104_plus_dx_conn_loc.JPG|align=left!                      ]]> 3114375 3179847 3114374 3179869 3114397 3179870 3114398 3179867 3114395 19073508 19040814 3179874 3114402 3179872 3114400 19073509 ./oebb.sh update ./oebb.sh tag [tagname] ./oebb.sh changelog ./oebb.sh checkout ./oebb.sh clean Not recommended, but also possible: ./oebb.sh bitbake It is recommended to do '. /home/headley/.oe/environment-angstromv2012.05' and run 'bitbake something' inside /home/user/projects/oe/setup-scripts without using oebb.sh as wrapper You must invoke "./oebb.sh config " and then "./oebb.sh update" prior to your first bitbake command Note: may be beaglebone Example: [assumes running as user, OE_HOME=~/projects/oe] cd $OE_HOME source ~/.oe/environment-angstromv2012.05 MACHINE="beaglebone" ./oebb.sh config beaglebone MACHINE="beaglebone" ./oebb.sh update =========================== Building Pre-Defined Images =========================== Images defined in bitbake recipe (.bb) files; there are many in oe/setup-scripts/sources/. There are generic Angstrom targets oe/setup-scripts/sources/meta-angstrom/recipes-images/angstrom There are platform-specific directories like oe/setup-scripts/sources/meta-ti/recipes-misc/images To find all the image names, use: oe/setup-scripts$ find ./sources/ -name "*image*"|grep bb Generic Angstrom oe/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/ xfce-nm-image systemd-image hardware-bringup-image systemd-gnome-image console-base-image efl-nodm-image console-image TI Beaglebone oe/setup-scripts/sources/meta-ti/recipes-misc/images/ cloud9-image.bb ti-hw-bringup-image.bb cloud9-gfx-image.bb cloud9-gnome-image.bb Common commands/pattern for recompiling if bitbake doesn't work, may try: bitbake -c clean -f bitbake -c compile -f bitbake -c deploy [binaries updated in $OE_HOME/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/deploy/images/beaglebone/ ] bitbake x-load [MLO bootstrap loader] bitbake u-boot [linux loader] bitbake virtual/kernel [linux kernel] =========================== Customize Pre-Defined Images =========================== =========================== Build Default Kernel =========================== For a default build, just run: bitbake virtual/kernel After done, you can collect the built image from under the deploy folder, for example: build/tmp-angstrom_v2012_05-eglibc/deploy/images/beaglebone/ =========================== Configure Kernel(XWindows) =========================== Configure If you need to customize the kernel configuration, you may run the menuconfig task by: bitbake -c menuconfig virtual/kernel Compile bitbake -f -c compile virtual/kernel Fine Control If you need more control over the configuration and compile process, add this somewhere into your local.conf: INHERIT += "devshell" and then you can go to the shell by: bitbake -c devshell virtual/kernel The build environment will be well setup for you; you can run regular make commands like make bzImage ...etc Please note, that the INHERIT step depends on the distribution you're using, some of the distributions already include the INHERIT in their configuration, so it might work already. You can check that easily using listtask task. Preserve Custom Config Changes are lost if you remove the tmpdir or do a "bitbake -c clean virtual/kernel", so you may consider replacing the defconfig with it. =========================== Configure Kernel (non-XWindows) =========================== Note: by default these commands require you to run in X Windows. Q: By default, some bitbake tasks, like devshell and menuconfig, require to run in X Windows, but I have a slow link to the build host. How can I change that requirement? A: Edit the bitbake config file openembedded/conf/bitbake.conf. Under the UI/Interaction Configuration section, set: TERMCMD ?= "${SCREEN_TERMCMD}" # = screen -D -m -t "$TERMWINDOWTITLE" TERMCMDRUN ?= "${SCREEN_TERMCMDRUN}" That will start a screen session to run the task. To attach to the session, open another terminal session and run: screen -r Please read the man page of the screen utility to customize TERMCMD for your requirement. ]]> 19040815 19073519 19040825 19073521 19040828 3179865 3114393 3179863 3114391 3179885 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * Run aptitude, choose 'Not Installed Packages->editors, add]]> 3114413 3179887 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install minicom]]> 3114415 3179876 3114404 3179878 3114406 19073504 Hard Disk > Add Device...  * Set Disk Size ** To use the entire target device (SD Card, USB stick), use same capacity as targeted device , e.g. 4.0 GB, 8.0 GB, 16.0 etc. ** For testing, may use smaller capacity (will take up less host disk space and less time to transfer image to device) * Configure Advanced options ** select IDE or SCSI (either OK) ** select Pre-allocate disk space ** de-select Split into 2 GB files * Click Apply * Choose name and path for virtual disk file * Restart the Linux guest VM {panel} The new disk icon should appear among the devices as a hard disk in the VM devices toolbar at the top of the VM window A device node will automatically created (e.g. /dev/sda) in the Linux VM, but will not be mounted automatically. It will have a name like /dev/sd, where is a,b, etc, but will not have any partitions listed (e.g. /dev/sda1). Use the mount command (no arguments) to determine which volumes are currently mounted; any _current mounts are_ *{_}NOT{_}* _the new virtual disk_. _Be careful not to partition or format the volume used by the Linux VM._ {panel} *Partition and format virtual disk as SD card* Before installing files, the virtual disk must be partitioned and formatted. This may vary depending on what Linux distribution is being installed. In this example, we'll create three partitions and format them as : * A FAT32 boot partition (beagleboot) that will contain the bootloaders (MLO and u-boot) and kernel image (uImage.bin) * An ext4 partition (beagleroot) to contain the linux root file system (rootfs) * An ext4 partition (beagledata) for application data For this example, we'll assume a 2 GB virtual disk on /dev/sda. As root (or use sudo), do the following: {code} $ sudo fdisk /dev/sda {code} Print the partition table : {code} Command (m for help): p Disk /dev/sda: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x9006ae65 Device Boot Start End Blocks Id System {code} If the disk size is correct and there is no partition table, proceed. Otherwise press 'q' to quit fdisk. *Create a 64 MB boot partition* * 'n' - Create a new partition * 'p' - Type primary * '1' - Partition 1 * - Accept default start sector * '+64M' - Specify partition size * 't' - set partition type * '1' - Partition 1 * 'c' - Type 'c' \[WFAT32 LBA\] Now the partition table should include the new partition: {code} Device Boot Start End Blocks Id System /dev/sda1 * 2048 133119 65536 c W95 FAT32 (LBA) {code} *Create a 256 MB (or suitable size) rootfs partition* * 'n' - Create a new partition * 'p' - Type primary * '2' - Partition 2 * - Accept default start sector * '+256M' - Specify partition size \\ Now if you print the partition table, it should look something like this: \\ \\ {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux {code} *Use the remainder of the disk for application data on a Linux partition* * 'n' - Create a new partition * 'p' - Type primary * '3' - Partition 3 * - Accept default start sector * - Accept default end sector Now if you print the partition table, it should look something like this: {code}    Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      133119       65536    c  W95 FAT32 (LBA) /dev/sda2          133120      657407      262144   83  Linux /dev/sda3          657408     4194303     1768448   83  Linux {code} To exit without modifying the partition table, press 'q', otherwise... \\ *Note: the next step will (for practical purposes) delete all of the data on the disk.* Press 'w' to write the changes to the partition table and exit fdisk.]]> 19040809 3179880 3114408 3179899 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * make-kpkg clean * make-kpkg \--revision=foce.1.0 kernel-image (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image *  ]]> 3114427 3179902 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 ** -make-kpkg clean- ** -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try ** make-kpkg clean ** make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image ** cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb **  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: *** 2.6.18-6-486.  This is the original kernel from the Debian installer. *** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. *** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) ** For each of the above kernels (denoted here as $KERNEL), you will find: *** /boot/config-$KERNEL *** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) *** /boot/System.map-$KERNEL *** /boot/vmlinuz-$KERNEL *** A directory named /lib/modules/$KERNEL *** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. ** Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. ** Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc.]]> 3114430 3179904 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * -make-kpkg clean- * -make-kpkg \--revision=foce.1.0 kernel-image- (*NOTE* \- this one didn't work after installing with dpkg \-i), so let's try * make-kpkg clean * make-kpkg \--initrd \--revision=foce.1.1 \--append-to-version=-foce.1.1 kernel-image * cd /usr/src; dpkg \-i linux-image-2.6.18-foce.1.1_foce.1.1_i386.deb *  OK, that worked.  Now there are 3 kernels supported (2 which work and can boot).  They are: ** 2.6.18-6-486.  This is the original kernel from the Debian installer. ** 2.6.18.  This is a non-working version from the 'make-kpkg \--revision=foce.1.0 kernel-image' line above. ** 2.6.18-foce.1.1.  This is the working version from the 2nd make-kpkg line above (with \--initrd, which apparently is necessary) * For each of the above kernels (denoted here as $KERNEL), you will find: ** /boot/config-$KERNEL ** /boot/initrd-$KERNEL  (except for foce.1.0, which is why it didn't work) ** /boot/System.map-$KERNEL ** /boot/vmlinuz-$KERNEL ** A directory named /lib/modules/$KERNEL ** /usr/src/linux-image-$KERNEL_i386.deb.  This is the Debian package to install the kernel and modules. * Note that the dpkg installer modifies /boot/grub/menu.lst to insert the new kernel as a boot option.  But when it does so, it removes the 'console=tty0 console=ttyS0,38400n8' from *all* the kernel lines.  These have to be manually reinserted on each kernel line if you want that kernel to send 'console' messages to the serial port as well as the LCD screen. * Future kernels will be built with sequential numbering \-\- foce.1.2, foce.1.3, etc.]]> 3114432 3179894 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev]]> 3114422 3179897 devel->main', and add: **  autoconf ** autogen ** automake ** binutils ** bison ** cccc ** curves ** cvs ** g+\+ (pulls in gcc 4.1) ** gdb ** indent ** libtool ** linux-source-2.6.18 ** make ** oprofile ** subversion * While in aptitude, choose 'Not Installed Packages->editors, add emacs.  Install * Install the following with apt-get: ** apt-get install openssl ** apt-get install ssh ** apt-get install setserial ** apt-get install minicom ** apt-get install kernel-package libncurses5-dev fakeroot wget build-essential (kernel build and debian package create) ** apt-get install xutils-dev ** apt-get install linux-doc-2.6.18 ** apt-get install linux-manual-2.6.18 ** apt-get install manpages-dev ** apt-get install bin86 binutils gawk shellutils (/usr/share/doc/kernel-package/README.gz says we need these for a kernel build) ** apt-get install sudo (more common alternative to fakeroot above) h5. Rebuild Linux from Source We need to rebuild the Linux kernel from source in order to support the ConnectTech Xtreme-104 octal serial board. This board came with a CD that has patches for the 8250/16550 serial driver, and the instructions are to patch and rebuild the kernel.  In preparation for this, we first just build the existing kernel from source to make sure it will build correctly. * cp serial.conf /etc  (this is the example serial.conf I got from Thom Maughan). * cd /usr/src * tar jxf linux-src-2.6.18.tar.bz2 * cd linux-src-2.6.18 * make clean; make mrproper * cp /boot/config-2.6.18-6-486 .config * make menuconfig ** Processor type and features \-> Processor family \-> Geode GX/LX  (Why wasn't this already selected?) ** Device Drivers->Character devices ** deselect "Non-standard serial port support (CONFIG_SERIAL_NONSTANDARD) ** These should already be selected; just make sure; in Serial drivers: *** 8250/16550 and compatible serial support (CONFIG_SERIAL_8250) *** Console on 8250/16550 serial port (CONFIG_SERIAL_8250_CONSOLE) *** Extended 8250/16550 serial driver options (CONFIG_SERIAL_8250_EXTENDED) *** Support for more than 4 legacy serial ports (CONFIG_SERIAL_8250_MANY_PORTS) *** Support for sharing serial interrupts (CONFIG_SERIAL_8250_SHARE_IRQ) ** Also set "Maximum number of8250/16550 serial ports" to 16, and "Number of serial ports to register at run time" to 12 * make-kpkg clean * make-kpkg \--revision=foce.1.0 kernel-image *  ]]> 3114425 6259368 6 false 0.0 0 0 19040827 6 false 0.0 0 0 3114132 5 false 0.0 0 0 9371909 6 false 0.0 0 0 3114136 5 false 0.0 0 0 6259359 6 false 0.0 0 0 3114123 5 false 0.0 0 0 3114128 5 false 0.0 0 0 19040811 6 false 0.0 0 0 3637480 6 false 0.0 0 0 3114109 5 false 0.0 0 0 3637488 6 false 0.0 0 0 19040630 5 false 0.0 0 0 19040558 6 false 0.0 0 0 3637905 5 false 0.0 0 0 19040625 5 false 0.0 0 0 5374755 5 false 0.0 0 0 19040617 5 false 0.0 0 0 3637901 5 false 0.0 0 0 3637503 6 false 0.0 0 0 3114389 5 false 0.0 0 0 6259368 5 false 0.0 0 0 3637497 6 false 0.0 0 0 19040608 5 false 0.0 0 0 10356102 6 false 0.0 0 0 3637511 6 false 0.0 0 0 3637883 5 false 0.0 0 0 3637505 6 false 0.0 0 0 6259359 5 false 0.0 0 0 3114325 6 false 0.0 0 0 19041133 6 false 0.0 0 0 19040591 6 false 0.0 0 0 4915268 6 false 0.0 0 0 19040598 6 false 0.0 0 0 3637401 6 false 0.0 0 0 19040608 6 false 0.0 0 0 3637433 5 false 0.0 0 0 3637901 6 false 0.0 0 0 19040617 6 false 0.0 0 0 3637431 5 false 0.0 0 0 3114109 6 false 0.0 0 0 19040625 6 false 0.0 0 0 3637431 6 false 0.0 0 0 3637905 6 false 0.0 0 0 5275678 5 false 0.0 0 0 19040630 6 false 0.0 0 0 9372007 5 false 0.0 0 0 3637433 6 false 0.0 0 0 3637401 5 false 0.0 0 0 3114446 5 false 0.0 0 0 3637515 5 false 0.0 0 0 5275678 6 false 0.0 0 0 3637328 6 false 0.0 0 0 3637523 5 false 0.0 0 0 18252651 5 false 0.0 0 0 3114389 6 false 0.0 0 0 3114123 6 false 0.0 0 0 3637503 5 false 0.0 0 0 9371938 5 false 0.0 0 0 3114128 6 false 0.0 0 0 3114238 5 false 0.0 0 0 3637497 5 false 0.0 0 0 3114132 6 false 0.0 0 0 3114242 5 false 0.0 0 0 3637511 5 false 0.0 0 0 3637883 6 false 0.0 0 0 19041215 6 false 0.0 0 0 3114136 6 false 0.0 0 0 10356102 5 false 0.0 0 0 3637505 5 false 0.0 0 0 6259287 5 false 0.0 0 0 19041215 5 false 0.0 0 0 3637488 5 false 0.0 0 0 4915268 5 false 0.0 0 0 5374755 6 false 0.0 0 0 3114231 5 false 0.0 0 0 10354905 5 false 0.0 0 0 3637480 5 false 0.0 0 0 9372007 6 false 0.0 0 0 3114446 6 false 0.0 0 0 10354905 6 false 0.0 0 0 3114325 5 false 0.0 0 0 19040558 5 false 0.0 0 0 3637523 6 false 0.0 0 0 19040827 5 false 0.0 0 0 19041133 5 false 0.0 0 0 3637328 5 false 0.0 0 0 3637515 6 false 0.0 0 0 6259287 6 false 0.0 0 0 19040811 5 false 0.0 0 0 3114238 6 false 0.0 0 0 3114242 6 false 0.0 0 0 9371909 5 false 0.0 0 0 19040591 5 false 0.0 0 0 19040598 5 false 0.0 0 0 3114231 6 false 0.0 0 0 18252651 6 false 0.0 0 0 9371938 6 false 0.0 0 0