further exploration

I continued in checking and find my way in the configuration files in the /etc directory. I saw some lines in the smb.conf that I found interesting to uncomment because they had NetBIOS in there name and could be useful when you work with samba server. Doing that had some serious influence on the OS behavior. The NGW went to almost 100% cpu load and the inetd deamon was printing error messages into the /var/log every second. This was certainly not a good thing to do. So I changed these back to original comment. I still not know exactly what causes the inetd daemon to run weird like that, but I was happy to saw the CPU load falling back again to 98% idle.

I also checked the possibility of accessing the web server of the NGW from the outside Internet. Therefore I had the setup the NAT of my router and rout the port 80 to the fixed IP of the NGW. This went smoothly. DMZ is also a solution but far less secure. Maybe I wont use this feature in the future because I have a dynamic IP address given by ISP that changes every 36h. I spoke to some friend of mine and maybe he has a solution for this with some DNS registry you can do in that case. I'll talk more on the subject when I have tried it.

I rewrote the led program, as it should be. Now all combinations of button presses/released are possible even at the same time. I just improved the state checking in the callback routine and introduced some enumerations for clearness and proper code styling. The avr32studio is my development platform I use on my laptop. A pity is that in that environment, based on eclipse, the "code assistant" feature doesn't work properly. Only if I declare includes with full path and not using the short form

this seems to work. Yesterday I tried to manage a remote debug session because the NGW also have a gdbserver installed. The connection seems to work, but in entering the elf executable avrstudio tries to read at address 0 and apparently there are no symbols loaded for that address. I even tried with static linking same result. This feature could be useful as development will progress of the new domotic program and difficulty degree will rise. For now a printf will do.

As you can see there’s plenty new tooling and stuff to explore.

This story continues next month...