first of all, thanks for all the great work spent on both the RPi board an the camera module. Both items are phenomenal!
Working with the camera, I encountered a problem:
If the raspistill command is called in a high frequency, chances are good that the whole RPi board freezes after a while (some hours). In this state, it cannot be reached through the network, plus it seems that it doesn't execute any user code, anymore.
If I try to login through the local (HDMI out) console, I can enter the user name but nothing happens after this.
I have created a small script which reproducable triggers the problem after some hours:
Code: Select all
#!/bin/sh sudo umount /stress_ramdisk >/dev/null 2>&1 sudo rm -rf /stress_ramdisk >/dev/null 2>&1 sudo mkdir -p /stress_ramdisk sudo mount -t tmpfs -o size=50m tmpfs /stress_ramdisk sudo chmod 0777 /stress_ramdisk while [ True ] do raspistill -w 1296 -h 972 -q 65 -t 0 -o "/stress_ramdisk/test.jpg" done
I am almost 100% sure that you will run into the same trouble as described above.
I have tested this script on both a 256 MB RPi and a 512 MB RPi - same results.
I have ensured that the power supply provides a "rock solid" supply, too.
I would be very thankful if someone could try the above script e.g. overnight and check if the RPi is still "alive".
Please note that there is no damage caused to the board; a simple power cycle brings everything up again, fine!
Does have anyone an idea what causes the described problem?
Many thanks in advance!