Comparing revisions for MiniCarComputer
- [1869] 2013-05-21 09:11:07 by KarlMW (unregistered user) [mostly hostap notes]
- [1870] 2013-05-25 16:03:51 by KarlMW (unregistered user) [mostly power management notes]
Additions:
====__Notes__====
- /opt/bootsync.sh is executed first, before console prompt appears
- this is the place to put anything that tweaks the user home
- /opt/bootlocal.sh is executed after console prompt appears
- this iterates over /opt/bootlocal.d
====__KMW a10Core setup notes__====
- /opt/bootlocal.d
- scripts are executed in lexical order
- they need to be executable, as per normal...
- filenames are constrained to alphanum/underscore/dash
- filenames containing dots are ignored!
- usual way to disable a script is to rename it something.DISABLED
====__HostAP__====
- potentially useful links
- /opt/bootsync.sh is executed first, before console prompt appears
- this is the place to put anything that tweaks the user home
- /opt/bootlocal.sh is executed after console prompt appears
- this iterates over /opt/bootlocal.d
====__KMW a10Core setup notes__====
- /opt/bootlocal.d
- scripts are executed in lexical order
- they need to be executable, as per normal...
- filenames are constrained to alphanum/underscore/dash
- filenames containing dots are ignored!
- usual way to disable a script is to rename it something.DISABLED
====__HostAP__====
- potentially useful links
Deletions:
====__Misc Notes__====
- boot scripts:
- standard TinyCore scripts:
- /opt/bootsync.sh is executed first, before console prompt appears
- this is the place to put anything that tweaks the user home
- /opt/bootlocal.sh is executed after console prompt appears
- this iterates over /opt/bootlocal.d
- KMW additions - /opt/bootlocal.d:
- scripts are executed in lexical order
- they need to be executable, as per normal...
- filenames are constrained to alphanum/underscore/dash
- filenames containing dots are ignored!
- usual way to disable a script is to rename it something.DISABLED
====__Wifi Notes__====
- HostAP would be useful for phone to connect to, but ad-hoc wifi would be sufficient (needs rooted phone)
- potentially useful HostAP links
====__Power Management Notes__====
- may need some handling for instances where power is lost briefly or car restarts just after mini-x shuts down
- just before mini-x starts shutdown sequence, assert a signal to power management which indicates that power should be restored *after* it is cut, if car power resumes
- possible power controller approaches
- minimum requirement:
- I/O:
- car power status signal to mini-x so it knows that power is about to die
- functionality:
- sustain power for 10s (or some other time) after car is turned off
- enough time to close logs cleanly and shutdown mini-x
- mini-x has no control and therefore has no risk of draining car battery
- better approach (could be achieved with a couple of relays and no real smarts):
- I/O:
- signal to mini-x so it knows that power is about to die
- signal from mini-x to shutdown power
- functionality:
- sustain power to mini-x until signal from mini-x says to shut down
- risk of draining car battery if mini-x loses its marbles
- even better approach:
- I/O:
- signal to mini-x so it knows that power is about to die
- signal from mini-x to shutdown power
- functionality:
- sustain power to mini-x until signal from mini-x says to shut down
- limit max duration of power sustaining (eg. to 15min)
- time limit ensures that mini-x can never exhaust car battery
CategoryKMWDiscussions