Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
<piey>
I'm not connecting over ethernet (wireless), does that matter?
<C-Keen>
piey: does your nanonotes network interface get an IP adress?
<C-Keen>
can you ping it?
<piey>
Yep.
<piey>
I can ping it.
<C-Keen>
and scp'ing from your host to the nanonote does not work?
<piey>
yeah
<C-Keen>
how far does it get when you add a -v to the scp call?
<whitequark>
GNUtoo-desktop: object code ?
<piey>
it stops at ssh
<piey>
debug1: Connecting to 192.168.1.100 port 22
<piey>
debug1: Connecting to address 192.168.1.100 port 22: connection refused
<C-Keen>
piey: does an sshd run on the nanonote?
<GNUtoo-desktop>
whitequark, like compiled C or C++ code
<GNUtoo-desktop>
for instance for arm
<piey>
C-Keen: I don't think so
<C-Keen>
piey: that would explain why it does not work
<piey>
ps doesn't list sshd
<C-Keen>
does it list dropbear?
<piey>
uuh, I don't think I'm using ps correctlu, I see 3 processes
<C-Keen>
ps ax
<GNUtoo-desktop>
ps -w
<GNUtoo-desktop>
if using busybox
<piey>
Sorry that I'm such a noob, but ps ax lists more than the screen
<C-Keen>
ps ax | grep drop
<piey>
drop is running
<piey>
dropbear*
<C-Keen>
hm
<piey>
sshd does not seem to be running
<piey>
720 tty1 S+ 0:00 grep sshd
<piey>
is the response I get
<C-Keen>
dropbear is an ssh daemon implementation
<C-Keen>
ah and the reason it does not work I think is because your root user does not have a password set. You could try using telnet to connect to your nanonote before you do so
<piey>
nope, I don't think that's the problem
<piey>
I just changed the password, still can't scp
<piey>
And I can't telnet to my ben either :/
<GNUtoo-desktop>
did you try the right user?
<C-Keen>
piey: what's your scp call look like?
<piey>
scp -v -r sdlquake root@192.168.1.100:~/
<C-Keen>
can you telnet to the nanonote?
<piey>
telnet 192.168.1.100
<piey>
Unable to connect to remote host: Connection refused
<C-Keen>
and is that the right ip address? :)
<piey>
ifconfig lists usb0 as
<piey>
inet addr: 192.168.1.100
<C-Keen>
hm, ok
<piey>
bcast 192.168.1.255
<piey>
bcast doesn't work either :|
<piey>
I suspect this is something to do with my ubuntu network configuration
<piey>
When I plug in my ben, ubuntu tries to connect to a wired network, without success
<piey>
(I was able to upgrade the firmware on the ben through)
<C-Keen>
piey: see the issue section at the bottom of the wiki page, maybe you need to tell your network manager to leave usb0 alone
<lindi->
or you could configure the ip address using network manager?
<piey>
my interfaces looks like this
<piey>
iface lo inet loopback
<piey>
lindi-: network-manager-gnome doesn't have anything I could configure
<xiangfu>
wpwrak, hmm.. so you are use 'root' in your PC system?
<xiangfu>
wpwrak, I just add root@
<wpwrak>
ah yes, i do everything as root
<wpwrak>
you'll probably need a few sudos then, too. for ifconfig and such
<wpwrak>
though if you run the whole thing under sudo, i think it should work
<xiangfu>
wpwrak, yes.
<kristianpaul>
"i do everything as root" 0_o -> xD
<kristianpaul>
about scripts i tought was one that is "fired" from udev
<kristianpaul>
also for a voiding network-manager (in some systems) to mess with ben add auto usb0 to /etc/network/interfaces
Openfree` has joined #qi-hardware
jirkab has joined #qi-hardware
urandom__ has joined #qi-hardware
<whitequark>
GNUtoo-desktop: so you want IDA
<GNUtoo-desktop>
yes but a free software version
<GNUtoo-desktop>
are the free ones that are already there usable?
<GNUtoo-desktop>
like for instance RADARE
<GNUtoo-desktop>
or stuff like that
<GNUtoo-desktop>
or frida
<whitequark>
radare has only trivial code analysis
<whitequark>
and, er
<whitequark>
frida is really hard to google
<whitequark>
at least I'm unable to find the reverse engineering related one
<GNUtoo-desktop>
ok
wolfspraul has joined #qi-hardware
B_Lizzard has joined #qi-hardware
pabs3 has joined #qi-hardware
jluis has joined #qi-hardware
fossrox has joined #qi-hardware
emeb has joined #qi-hardware
wolfspraul has joined #qi-hardware
kilae has joined #qi-hardware
jluis has joined #qi-hardware
antgreen has joined #qi-hardware
wolfspraul has joined #qi-hardware
GNUtoo-desktop has joined #qi-hardware
jekhor has joined #qi-hardware
jekhor has joined #qi-hardware
<qi-bot>
[commit] Werner Almesberger: m1nor: search fjmem.bit also in /usr{/local,}/share/milkymist/fjmem.bit (master) http://qi-hw.com/p/wernermisc/b05481f
jluis has joined #qi-hardware
Ayla has joined #qi-hardware
jluis has joined #qi-hardware
jluis has joined #qi-hardware
jluis has joined #qi-hardware
Artyom has joined #qi-hardware
<Artyom>
kristianpaul: hi
jluis has joined #qi-hardware
Jay7 has joined #qi-hardware
mstevens has joined #qi-hardware
<whitequark>
!seen tuxbrain
<qi-bot>
whitequark, I found 6 matches to your query. These are the 5 most recent ones: tuxbrain_HxxHhzo, tuxbrain, tuxbrain_zzzzzz, tuxbrain_PASS, tuxbrain_WPAN. tuxbrain_HxxHhzo (~tuxbrain@95.61.34.233) was last seen quitting #milkymist 17 weeks 3 days 22 minutes ago (18.10. 19:27) stating "Ping timeout: 256 seconds" after spending 23 hours there.
jluis has joined #qi-hardware
jekhor has joined #qi-hardware
<kristianpaul>
Artyom: hi
<kristianpaul>
btw did you buyed that book "Fundamentals of GPS Receivers: A Hardware Approach" ? :-)
<kristianpaul>
looks really interesting to get one ;)
<Artyom>
No, I haven't bought it. Rather expensive for me...
<kristianpaul>
expensive for me same..
<Artyom>
I wanted to tell that I published my Softosgps port (only acquisition and tracking is done).
<Artyom>
There are some updates comparing to the original code
<kristianpaul>
yup just did svn up today and noticd it :)
<kristianpaul>
havent done a full diff yet
<Artyom>
For example: IQ and only-I signal processing can be chosen
jluis has joined #qi-hardware
<kristianpaul>
oh
<Artyom>
Most "magic numbers" are calculated during initialization
<Artyom>
And I tried to put all global variables in one header
<Artyom>
To make the code more readable
<kristianpaul>
I tought osgps was using globar variables already?
<kristianpaul>
global*
<Artyom>
And also some steps towards glonass implementation are done
<Artyom>
yes, osgps use global variables. But they are spread among several files. I think it's better to keep them in one place
<kristianpaul>
damn that book is pretty nice
<whitequark>
Artyom: hi
<whitequark>
about milkymist
<whitequark>
I've been quite busy at work, so I didn't even unpacked it (yet), but it has definitely arrived
<whitequark>
the customs definitely weren't a problem
<kristianpaul>
*g*
<kristianpaul>
whitequark: how much you paid to customs?
<Artyom>
yeah, that is definitly a good news. MM price is relatively low to have troubles with customs :)
<whitequark>
kristianpaul: nothing
<kristianpaul>
oh cool !
<kristianpaul>
fedex?
<whitequark>
yes
<kristianpaul>
wow
<kristianpaul>
bbl
<whitequark>
I've got more than 15 parcels of different size, weight, originating country and contents in the last year
<whitequark>
all have arrived in less than 25 days, relatively unharmed
<Artyom>
As I understand goods with price below 1000 euro should pass through customs without any problems
<whitequark>
the declared sum was something like $75
<whitequark>
of course that means no insurance
<Artyom>
According to rules of customs union (Russia, Kazakhstan, Belarus)
<Artyom>
whitequark: It would be interesting to hear about your experience with MM1 ;)
<whitequark>
what particularly?
<kristianpaul>
back
* kristianpaul
tempted to buy the book
<kristianpaul>
at least i can find other way to get it of course :)
<Artyom>
starting from the beginning: one thing is to see something in the internet and absolutely another to touch something with your hands :) BTW Are you going to use it as a vj-tool? Or you have some projects that you want to check with MM1?
<Artyom>
Some parts of the book are available through google-book
<Artyom>
At home I could read chapter 1
<Artyom>
at wotk chapter 8
<Artyom>
Which chapter can you read? ;)
<whitequark>
Artyom: nah, I don't even know who VJs are (except for Wikipedia article obviously)
<whitequark>
but it's better than most FPGA devboards around here
<kristianpaul>
Artyom: yeap
<kristianpaul>
i got appendix A B C D E in pdf..
<Artyom>
whitequark: what benefits do you consider important?
<kristianpaul>
tought shipping is just 9usd nice
<whitequark>
Artyom: being designed by people whose goal is to make a piece of good HW and not to sell a ton of accessories (I'm looking at you, Digilent)
<kristianpaul>
chapter 6 here
<Artyom>
kristianpaul: another 10 persons and we will be able to read all the book :)
<kristianpaul>
lol
<kristianpaul>
I'm interested on chapter 9
<kristianpaul>
btw i think i messed a wire here, either your soc is not working on my board
<kristianpaul>
i guess the gps clock is not working good...
<kristianpaul>
debuging right now with scope.. :|
<kristianpaul>
make that cable longer was not a good idea after all..
* kristianpaul
at 34°C and goes for lemonade
<wpwrak>
only 26 C here:) but 83% humidity ...
* whitequark
has read that as "83% humanity"
<Artyom>
whitequark: I personaly appreciate the SoC. It's the only open-source analogue to microblaze in my understanding. (BTW I bought my Digilent board long before MM 1 was developed).
<whitequark>
Artyom: M1 SoC can run on most FPGAs powerful enough at the market
<Artyom>
I know it. And I play with it on one of them...
<Artyom>
kristianpaul: what cables are you talking about?
<kristianpaul>
Artyom: some that goes from the sige EVB to M1
<Artyom>
and how long is your cable? Mine is about 15-20 cm
<kristianpaul>
10cm
<kristianpaul>
wow quite long, do you use some shielding?
<Artyom>
no
<Artyom>
distance doesn't seem to long for 16Mhz...
<kristianpaul>
indeed
<whitequark>
a "wiggler" programmer for atmegas (1MHz maybe) is known not to work with cable lengths over 30-50cm
<whitequark>
and it did fail for me on some occasions
<kristianpaul>
whitequark: btw what your plans with M1?
<kristianpaul>
are you interesting on the gps system on chip implementation Artyom is working on for glonass?
<whitequark>
kristianpaul: hmm. I'm going to do something with it
<kristianpaul>
or gps on my side :)
<whitequark>
gps sounds interesting
<whitequark>
do I need any special hardware?
<kristianpaul>
it is
<kristianpaul>
you need a receiver
<kristianpaul>
you already have a M1 :D
<kristianpaul>
Artyom: your website is down?
<whitequark>
kristianpaul: ahem
<whitequark>
I thought your GPS work involved parsing raw signals
<Artyom>
whitequark: simple rf front-end to receive, amplify and digitize gps signal
<kristianpaul>
whitequark: yes
<kristianpaul>
using milkymist :)
<whitequark>
ok, isn't the RF frontend "special hardware"?
<kristianpaul>
nope at all
<Artyom>
kristianpaul: it worked an hour ago... But now there are some problems...
<Artyom>
yeah, I gues I should change hosting provider once...
<Artyom>
now it works :)
<Artyom>
time to sleep. gn
Aylax has joined #qi-hardware
antgreen has joined #qi-hardware
Aylax has joined #qi-hardware
<qi-bot>
Jon Phillips: Via @qihardware qihardware: @jptmoore Awesome! Great work. - qihardware: @jptmoore Awesome! Great work. http://t.co/OtTUmpqU ( 170650573815812097@rejon - 40s ago via Ping.fm )