<neil_>
Hello, I just got my NanoNote this morning and I'm well happy.  About the red LED on the right-hand side.  The manual says it's a power LED but it seems to indicate that it's charging instead.  Is that what it's doing?
<wolfspraul>
charging
<neil_>
so when it goes off even though it's still plugged in, it means it's fully charged?
<urandom_>
yeah
<neil_>
great. thanks
<neil_>
how can I tell roughly how much charge remains in the battery from the command line?
<qi-commits>
Xiangfu Liu: [usbboot] copy the jz4760.h file from u-boot, fix the jz4760 nand addr, cmd, data, port define http://qi-hw.com/p/xburst-tools/eb23820
<tuxbrain>
wolfgang: so you finally have flashed your the HK stock, any tips so I can do the same at little scale here?
<kyak>
wolfspraul: can i please be added to downloads.qi-hardware.com/people/ ? i would like to have a place at qi to conveniently store and update my ports :)
<kyak>
My build of jfbterm.. It requires some configuration to display UTF-8 properly, and I havent figured out yet how to do it :)
<kyak>
and it's MUCH faster displaying, than the default terminal; and unifont looks more slim
<kyak>
by the way, there is also an fbterm build in people/kyak/tmp/fbterm.. but i suppose there is more chance for displaying of UTF-8 in console with jfbterm than fbterm
<wolfspraul>
what is the difference between jfbterm and fbterm?
<wolfspraul>
I only heard some Japanese like fbterm.
<wolfspraul>
in general I would like an easier way to increase/decrease console font sizes
<kyak>
jfbterm stands for Japanese fbterm :)
<kyak>
i hope it has a better support for utf-8
<kyak>
currently i don't have any luck with both of them
<wolfspraul>
ah there you go
<wolfspraul>
maybe it's just the bfbterm (better fbterm)
<wolfspraul>
it seems to be quite commonly used in Japan, or so I heard
<kyak>
i'ld like to find a jwfbterm (Just a Working fbterm )
<kyak>
:)
<kyak>
lol.. this is amazing what just happened :) i've launched jfbterm from a ssh session, and it started in Ben
<kyak>
not i'm typing in ssh screen, and everything goes to Ben's screen :)
<kyak>
i wonder if this is a bug or a feature
<kyak>
it feels like connecting external keyboard to Ben
<kyak>
i think jfbterm has attached my ssh virtual terminal to a real tty
<zear>
kyak, i don't know about the nanonote, but if you launch programs on dingux via telnet, they render on dingoo's screen
<kyak>
zear: that's interesting.. i thought for X programs this should depend on DISPLAY variable, and for SDL they just don't launch
<kyak>
zear: yes, the same for Ben.. at least gmu is rendered on Ben's screen
<zear>
via telnet, or via ssh?
<kyak>
via ssh
<kyak>
should be the same
<kyak>
is building openwrt with utf-8 and locales support
<kyak>
rafa: it has support for bitmap fonts and supposedly supports i18n better. At least, when it comes to utf-8 support in console, there are many references to jfbterm
<kyak>
theoretically, fbterm is also capable of text encoding, but anyway I didn't succeed with any of them yet
<rafa>
kyak: I ask because it looks like jfbterm is old (last version is 2003 no?).. and fbterm is current, but I do not know which is better, that is why I ask you :)
<kyak>
last version of jfbterm is 2005
<kyak>
but it doesn't matter as long as both don't do what i want :)
<kyak>
i'm just trying to play with both
<nebajoth>
sup
<lekernel>
where can I buy a RS232/3.3V shifter in Europe?
<lekernel>
France preferably
<lekernel>
pre-assembled
<prpplague>
lekernel: virtually any electronics outlet is going to carry uart level shifters
<lekernel>
prpplague, you overestimate the french electronics shops
<lekernel>
in my city they don't even have standard 2.54mm connector pins
<lekernel>
he10 etc.
<lekernel>
plus everything is expensive as hell
<lekernel>
like 10x the digikey prices
<prpplague>
lekernel: yea but you can afford to buy it since you have such good health care
<lekernel>
ok, let's say farnell or radiospares prices then - both companies have French divisions
<Textmode>
Morning all
<nebajoth>
SUP
<dptech>
hello where can i found the best tuto for flash to debian ?
<dptech>
nebajoth: thanks, I must to see before to go... so I want to be sure to make very good!
<dptech>
I see first part for debian, perfect!
<xdpirate>
What do you call an LCD screen like the one the NN has? (In regards to every even row of pixels lines up, and every odd row of pixels lines up, but the odds and evens differ by half a pixel)
<prpplague>
xdpirate: the lcd in the NN is an passive matrix display with an 8-bit data interface
<xdpirate>
prpplague, thanks
<prpplague>
xdpirate: it is a pretty decent display and fairly easy to interface to
<xdpirate>
it's hard to read small fonts when the pixel matrix is lined up like that tbh
<xdpirate>
but i'm guessing the displays are cheaper to manufacture so
<prpplague>
yea, they are mainly manufacturer for dedicated devices that use small graphics
<prpplague>
i.e. game handhelds and control devices like a programmable thermostat
<prpplague>
i have the display from the NN working with some OMAP3 and OMAP4 devices
<calamarz>
sdschulze: did you succeeded in rebuilding debian kernel for the nn with the openwrt toolchain?
<calamarz>
sdschulze: i was trying to follow your notes but got no luck booting it :(
<neil_>
Hi.  I've read http://en.qi-hardware.com/wiki/How_to_reflash over and over but I'm still not confident of how to re-flash -just- the rootfs.  Do I still need to use nerase if I don't want to erase the whole NAND?  If I do, would nerase 2048 4096 0 0 be the right thing to do ( followed by nprog for the rootfs)?
<larsc>
`nerase 16 4080 0 0` earases the rootfs
<emeb>
why not just use the flash script and let it do u-boot, kernel and rootfs?
<neil_>
larsc: do you mean "4096" rather than "4080"?
<neil_>
or do you really mean 4080
<neil_>
emeb: I've got the reflash-ben.sh, thanks.  I'm trying to understand it.  The page on the wiki does say to avoid re-flashing u-boot unless necessary
<larsc>
neil_: the second parameter is the number of blocks to erase
<larsc>
since there are 4096 and you start at 16 you want to erase 4080 blocks
<neil_>
larsc: the wiki page says it's the block length.  ah.  does that mean "the number of blocks" and not "the block size", which is how I interpreted it?
<emeb>
neil_: larsc: careful! using 4080 will erase everything from 16 on to the end, not just the rootfs.
<emeb>
if you look at the reflash_ben.sh script you can see the parameter they use is 512, not 4080. The rootfs of the OpenWRT build doesn't take the whole rest of NAND
<emeb>
in the OpenWRT build they reserve the last portion of NAND for the data partition of ~ 1.7GB.
<neil_>
emeb: I read exactly what you say somewhere on the wiki but "df" shows 1.8GB free on my rootfs.  is this the ubifs compression?
<emeb>
neil_: no. when I do a df on mine I only see about 200M in the rootfs partion.
<larsc>
it depends in your image version
<emeb>
Where did you get this image?
<neil_>
mine's 2010-10-??  It came with the device
<neil_>
sorry
<neil_>
2010-01-??
<emeb>
OK - that's the original. Pretty old u-boot and kernel too. You may want to update the u-boot and kernel because they're much improved since then.
<neil_>
emeb: OK, I'll update u-boot as well as you say.  sounds like having a data partition so my music isn't trashed when I update the rootfs is a good idea
<emeb>
neil_: yep - that was what I thought too. There are some good instructions on the wiki for setting up the data partition after you reflash.
<emeb>
I just used the script and it worked fine.
<neil_>
why does reflash-ben.sh only issue an nerase command for the rootfs and not for the u-boot and kernel partitions?
<emeb>
the new u-boot allows booting into USB mode without fiddling around with the shorting pads under the battery.
<emeb>
neil_: no idea about the nerase. I was wondering that too
<neil_>
emeb: but it worked for you anyway?
<emeb>
neil_: yes it worked fine both times I ran it.
<larsc>
neil_: for the rootfs leftovers from the previous on need to be cleaned up. for kernel and uboot it doesn't matter
<larsc>
s/on/one
<neil_>
thanks for all the help.  I'm learning a lot and it's getting clearer
<emeb>
neil_: looking at the logfile from the reflash script it appears that the nprog command does an erase automatically.
<larsc>
neil_: if you think there is misleading or missing information on the wiki, please update it.
<emeb>
it may be redundant to do it in the script.
<neil_>
larsc: OK, I will do.  thanks
<nebajoth>
sup
<nebajoth>
hey
<nebajoth>
does the openwrt firmware use dumpkeys/loadkeys?
<nebajoth>
or is that just a debian thing?
<nebajoth>
anyone using debian: ping
<xiangfu>
I tried loadkeys in openwrt before. but not success. the BUSYBOX's loadkeys use different file format.
<nebajoth>
what about dumpkeys?
<qwebirc64441>
Hello.. just flashed the Nanonote with Debian... Now it won't turn on..
<nebajoth>
what happens when you take out the battery and plug in the usb cable?
<nebajoth>
does the red light come on for a brief second, then go off?
<qwebirc64441>
Nothing.
<qwebirc64441>
Hmm.. let me check.
<qwebirc64441>
Yes, it does.
<nebajoth>
your bootloader is corrupt
<qwebirc64441>
Ah.
<nebajoth>
you need to short the usb boot pins beneath the battery
<nebajoth>
force it into usb boot mode
<qwebirc64441>
Ok.
<nebajoth>
and then reflash
<nebajoth>
I use tin foil
<nebajoth>
a small piece
<qwebirc64441>
Just the boot-loader or everything?
<nebajoth>
xiangfu: I occasionallyy get a message about scrubbing PEBs and moving them to other PEBs
<nebajoth>
is this a matter for concern?
<wolfspraul>
qwebirc64441: your Nano is already unbricked? (just reading up)
<wolfspraul>
if your u-boot bootloader is indeed corrupted, you need to short the USB boot pin but there should be a little rubbery button included in your box
<nebajoth>
oh yeys
<nebajoth>
yes
<nebajoth>
I lost mine
<wolfspraul>
use that, much easier than aluminum foil
<nebajoth>
also hello wolfspraul
<wolfspraul>
nebajoth: email me your shipping address and we'll mail you a few more in regular mail
<nebajoth>
sweet!
<wolfspraul>
I think they cost 0.5 US cents or so a piece, forgot :-)
<nebajoth>
haha, well shipping might be a little more
<qwebirc64441>
wolfspraul: Not yet. I'm in the process of putting it into USB-boot mode.
<nebajoth>
any word on backlit keyboards for the Ya? :D
<wolfspraul>
sure but we'll just throw them in a regular letter
<nebajoth>
oh snap
<nebajoth>
I fixed my keymap problem
<nebajoth>
finally, a working + key
<nebajoth>
now I can use remind again
<wolfspraul>
nebajoth: please keep your expectations for those things (backlit keyboad) very low
<nebajoth>
haha, I do
<wolfspraul>
we have to 100% focus on what this project is about - copyleft hardware
<wolfspraul>
we sold 800 Ben, which is great
<wolfspraul>
but of course totally not sustainable
<nebajoth>
nope
<nebajoth>
not unless you increase the price a great deal :O
<wolfspraul>
so we need to be very careful, 100% focus on what is unique about our product
<wolfspraul>
increase price = death
<wolfspraul>
this is a hardware business
<nebajoth>
yep
<wolfspraul>
I want to decrease prices.
<nebajoth>
I dunno, key visibility in low light situations seems like a pretty universal requirement
<nebajoth>
for a "portable" device
<wolfspraul>
so anyway, when we think about Ya, we have some amount X of cash
<nebajoth>
whatever the use case scenario
<wolfspraul>
and it will be very little
<wolfspraul>
and we will focus it only on the areas that matter to actually be able to ship the product
<wolfspraul>
but now, on the good side, I agree about your observations about the keyboard
<neil_>
what impact on the price would USB host have?
<nebajoth>
almost none, I'd think
<wolfspraul>
that's the advantage of all of us using this thing, and the reason why we launched the project the way we do
<wolfspraul>
get a real product out first
<nebajoth>
the jz4740 has usb host capability
<wolfspraul>
collect real life feedback, grow a community
<nebajoth>
if I read the spec sheets correctly
<nebajoth>
it'd have to be broken out into the circuitboard for a connector
<wolfspraul>
once you do a full little computer with 2-3 full-time people, some volunteers, and some donated cash, every tiny thing becomes big :-)
<nebajoth>
yeah, I hear you wolfspraul
<nebajoth>
any chance you can send me some blank keys?
<nebajoth>
I'll experiment with glow in the dark paints :D
<wolfspraul>
blank keys?
<nebajoth>
I want to replace mine
<wolfspraul>
I think the print is under the plastic
<nebajoth>
yeah
<wolfspraul>
I'm not sure how easy it is to take the keyboard apart
<wolfspraul>
it may all break
<nebajoth>
not very
<wolfspraul>
if I have some old prototype/sample keyboard I can throw it in, for sure
<nebajoth>
what do you do for a day job, wolfspraul?
<wolfspraul>
ha
<wolfspraul>
this is my 'day job'
<nebajoth>
:P
<wolfspraul>
:-)
<nebajoth>
where does the money come from to pay you?
<wolfspraul>
it's 10.10 AM in China
<wolfspraul>
from my savings
<nebajoth>
:O
<nebajoth>
you're betting big on this
<nebajoth>
do you live in China?
<wolfspraul>
I don't think like that.
<wolfspraul>
yes, China
<nebajoth>
you are German by birth?
<wolfspraul>
keep costs of living low, plus manufacturing is here
<nebajoth>
interesting
<wolfspraul>
yes. first Germany, then >10yr US make some money and savings, then 3+ years China spend the savings
<nebajoth>
what do you work on mostly?
<wolfspraul>
he he
<nebajoth>
haha
<wolfspraul>
yeah, seriously
<wolfspraul>
that's the short story
<wolfspraul>
I work on manufacturing issues
<nebajoth>
pretty interesting story actually
<nebajoth>
could make a good magazine article
<nebajoth>
when its time to get real publicity out about this unit
<wolfspraul>
I'm a software engineer originally.
<wolfspraul>
fun stuff, file systems
<neil_>
how do test a file system ( other than by using it)?
<neil_>
s/do/do you/
<wolfspraul>
sure run automated scripts/programs
<wolfspraul>
file systems are hardcore, especially on multi-core/SMT machines, with swapping going on, etc.
<wolfspraul>
it was a fun time back then
<wolfspraul>
but I have to say manufacturing is also really really interesting. totally overlooked.
<wolfspraul>
nebajoth: so far I think our NanoNote is off to a good start, isn't it?
<wolfspraul>
after the first year...
<qwebirc64441>
Damn. It's a real bitch trying to get it into USB-boot mode.
<wolfspraul>
now we throw all that we've learnt into Ya, very much looking forward to it
<wolfspraul>
qwebirc64441: yeah, one thing we need to improve in Ya :-)
<qwebirc64441>
Yep.
<wolfspraul>
qwebirc64441: do you use the carbonized rubber button?
<neil_>
I'd say so.  Incredible that it can be made for $99
<qwebirc64441>
Yeah.
<nebajoth>
wolfspraul: NanoNote rules, dude.
<wolfspraul>
unplug the USB cable
<nebajoth>
I effing love this thing
<nebajoth>
it really grows on you
<nebajoth>
and I think that's mostly about hardware that just works
<wolfspraul>
push the carbonized rubber button against the USB boot pins
<neil_>
I'm re-flashing for the 1st time right now.  It says I have a Jz4740.  I thought it was Jz4720?
<wolfspraul>
plug the USB cable back in
<wolfspraul>
ah, sorry, forgot something :-)
<wolfspraul>
on your host, run "watch lsusb"
<wolfspraul>
when you see the ID "0x601a:4740" show up, that's your Nano in USB boot mode
<wolfspraul>
so it's easy to watch it there
<wolfspraul>
so if you plug the USB cable in, you can also press the power-on button (hold for 2-3 seconds to be sure)
<nebajoth>
I prefer 'watch -n 0.2 lsusb'
<nebajoth>
but I'm an impatient guy
<wolfspraul>
you only need to short the USB boot pins at the time when the CPU gets power
<wolfspraul>
you don't need to hold it
<wolfspraul>
(after the CPU is powered)
<nebajoth>
is holding it a problem?
<nebajoth>
I'm breaking my usb-mode pads out to the side of the unit
<wolfspraul>
basically when the CPU gets powered, it checks those pins. If short, branch to USB boot mode. if not short, boot from NAND.
<nebajoth>
and I was going to put in a switch
<wolfspraul>
holding shouldn't be a problem
<nebajoth>
ok good
<wolfspraul>
neil_: 4720/4725/4740 is all the same die, just different packaging (=way the CPU is wrapped in plastic and fixed to the PCB)
<nebajoth>
how much memory is going into the Ya, you think?
<wolfspraul>
A LOT! :-)
<wolfspraul>
he he
<wolfspraul>
don't know
<nebajoth>
:D
<wolfspraul>
we will drive this together, the specs and all
<wolfspraul>
it will be fun
<wolfspraul>
we have so many good people on board now
<wolfspraul>
just need to cleanup a bit
<wolfspraul>
merge the discussion & developer mailing lists into one
<neil_>
are you concerned about overlap with the Pandora?
<wolfspraul>
not at all
<wolfspraul>
Pandora is not copyleft hardware
<wolfspraul>
of course they run Linux and all so that's cool
<nebajoth>
I want to get a Lemote
<wolfspraul>
neil_: we are very serious about this copyleft hardware thing
<nebajoth>
chips with chinese symbols on them are 1337
<wolfspraul>
we need to work more on that, like GPL licensed production testing software (for Ya definitely)
<wolfspraul>
also case design
<wolfspraul>
need to cleanup some trademark issues (like 'microSD')
<nebajoth>
case design isn't open?
<wolfspraul>
we worked hard on the patent problem, and still ongoing
<wolfspraul>
nebajoth: first question is "what is open case design?"
<nebajoth>
haha
<wolfspraul>
right now we have design files open, but not 3D files
<nebajoth>
schematics with a CC license?
<wolfspraul>
sure
<wolfspraul>
all that stuff is there
<wolfspraul>
I am talking about the plastic parts.
<nebajoth>
hmm
<wolfspraul>
of course the design files are all CC licensed.
<nebajoth>
we need to be able to build one of these with a RepRap
<neil_>
one day it would be nice to use a RepRap or one of its descendants to fab a new case at home
<nebajoth>
haha
<wolfspraul>
the problem with mechanical is that all professional software isproprietary
<neil_>
ninja!
<nebajoth>
inb4
<nebajoth>
pwnt
<wolfspraul>
anyway we work on that
<wolfspraul>
one by one
<wolfspraul>
we start with the most valuable parts
<wolfspraul>
hey guys, Milkymist One boots Linux, did you know?
<wolfspraul>
documentation about the SMT process for Milkymist One
<neil_>
I'm getting "Error - can't read bulk data from Ingenic device:1344" when running sudo ./reflash_ben.sh.  I have the latest reflash.sh and xburst-tools
<wolfspraul>
I think this is the best and most thoroughly documented SMT process ever.
<nebajoth>
neil_: is the unit actually in usb boot mode?
<neil_>
think so.  it started the flash process
<nebajoth>
uh oh
<wolfspraul>
did you see whether it flashed u-boot and kernel already?
<wolfspraul>
when did it stop?
<nebajoth>
wolfspraul: that milkymist link is awesome
<neil_>
I have 601a:4740 in lsusb.  can I paste multi-line here or is that rude?
<wolfspraul>
ok for me, but probably not needed
<wolfspraul>
ok if you see that ID, it means you are in USB boot mode. good.
<neil_>
Checking 454656 bytes... no check! End at Page: 605421569
<neil_>
Skip a old bad block !===
<neil_>
fatal error occured - ABORTED
<neil_>
===
<neil_>
error while flashing bootloader:
<neil_>
that's from the log.txt
<wolfspraul>
hmm
<wolfspraul>
boot loader
<wolfspraul>
let's try manually :-)
<wolfspraul>
I don't like the reflash script anyway...
<wolfspraul>
turn off the Nano
<wolfspraul>
unplug USB cable
<wolfspraul>
short the USB boot pins with the carbonized rubber button
<neil_>
ok.  doing that now
<nebajoth>
hmmm
<nebajoth>
how do I get a milkymist?
<wolfspraul>
plug the USB cable in, press POWER ON, see the 0x601a:4740 showing up
<neil_>
do I have to wait a minute like it says on the wiki?
<wolfspraul>
minute?
<wolfspraul>
no
<neil_>
ok, got vend/prod
<wolfspraul>
if you see the 601a:4740, all is good
<wolfspraul>
now run 'usbboot' (as root)
<wolfspraul>
just 'usbboot'
<wolfspraul>
it will go to a command prompt
<wolfspraul>
first command: "boot"
<neil_>
ok.  doing
<wolfspraul>
second command: "nprog 0 u-boot.bin 0 0 -n" (sorry u-boot.bin needs to be the real long filename of u-boot)
<neil_>
succeeded
<wolfspraul>
how about the nprog command?
<neil_>
got prompt back.  last thing it said was "Skip a old bad block"
<wolfspraul>
hmm
<nebajoth>
neil_: reinstall openssh-server, and install console-setup
<nebajoth>
the first will force it to generate a key for the ssh server
<nebajoth>
and the second will fix a keymap issue
<wolfspraul>
neil_: let's run an erase command over your entire NAND first
<nebajoth>
at least, an issue I was having
<nebajoth>
qwebirc64441: ^^
<nebajoth>
qwebirc64441: any luck?
<neil_>
nebajoth: does "boot" install an SSH server/client then?
<wolfspraul>
neil_: is that OK with you?
<neil_>
sure
<wolfspraul>
so try "nerase 0 4096 0 0"
<nebajoth>
neil_: eh?
<wolfspraul>
that will nuke the entire 2 GB
<nebajoth>
neil_: openssh is installed by default, if that's what you're asking
<nebajoth>
but it doesn't work
<wolfspraul>
after that the nprog command again
<nebajoth>
you will almost certainly need to designate a swap file
<nebajoth>
or use the microsd as a swap partition
<wolfspraul>
neil_: no no, "boot" will only load a tiny snipped to the Nano so usbboot can community with the Nano
<nebajoth>
(I do the latter, but xiangfu has done the former)
<wolfspraul>
ouch it's getting confusing now, we talk about entirely different things
<nebajoth>
sorry
<nebajoth>
I'm going to bed soon
<nebajoth>
I was just pouring out information :P
<nebajoth>
but I've just confused things
<neil_>
wolfspraul: ok.  I think I got crossed wires just then.  have done nerase now.  last thing it said was "Force erase, no bad block infomation!"
<wolfspraul>
ok
<wolfspraul>
now the nprog command again
<wolfspraul>
"nprog 0 u-boot.bin 0 0 -n"
<qwebirc64441>
nebajoth: Not yet. :/
<qwebirc64441>
nebajoth: Cant' get it into USB-boot mode.
<xiangfu>
it's u-boot-nand.bin
<neil_>
same:Â Â Finish! (len 454656 start_page 0 page_num 111)
<neil_>
Error - can't read bulk data from Ingenic device:64
<neil_>
Checking 454656 bytes... no check! End at Page: 8402977
<neil_>
Skip a old bad block !
<nebajoth>
qwebirc64441: are you using the plastic doohickey or tinfoil?
<qwebirc64441>
The plastic thing.
<nebajoth>
hm
<nebajoth>
qwebirc64441, neil_: remember to sign up for nanohacks.org if you haven't already
<neil_>
wolfspraul: USB cable is the one that came with it.  host can only do USB 1.1.  is that relevant?
<nebajoth>
there's only a few of us posting stuff, but its the official home for debian discussion
<wolfspraul>
neil_: thinking
<wolfspraul>
neil_: can you try on another Linux host machine?
<wolfspraul>
or if your computer has multiple USB plugs, try the other ones
<neil_>
wolfspraul: can do.  will take a few mins to install xburst and so on
<wolfspraul>
do you have multiple USB connectors on this computer?
<neil_>
yes, although they've always behaved the same, unlike some other machines I've seen
<wolfspraul>
several people have seen problems behind USB hubs, and sometimes there are hub chips on the mainboard
<wolfspraul>
can you still turn on your Nano?
<wolfspraul>
or screen just stays black?
<qwebirc64441>
Well.. trial and error.. trial and error.. i'll keep trying. Thanks for all of your help.
<neil_>
inserting in either port shows:Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
<neil_>
Bus 002 Device 034: ID 601a:4740
<neil_>
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
<neil_>
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
<neil_>
wolfspraul: can still turn it on.  it says unusual stuff
<wolfspraul>
hmm
<wolfspraul>
maybe the bootloader is just fune
<wolfspraul>
fine
<wolfspraul>
let's try to flash the kernel
<wolfspraul>
run 'usbboot'
<wolfspraul>
then at the command prompt 'boot'
<wolfspraul>
then 'nprog 1024 uImage.bin 0 0 -n'
<neil_>
wolfspraul: aha.  it says on LCD: Wrong Image Format for bootm command
<wolfspraul>
replace uImage.bin with the name of your kernel image
<wolfspraul>
what are you flashing actually? openwrt 2010-06-15?
<neil_>
wolfspraul: whatever the reflash-ben script downloaded
<wolfspraul>
ok
<wolfspraul>
openwrt 2010-06-15
<wolfspraul>
let's try nprog for the kernel, see whether more/other errors show up
<neil_>
wolfspraul: it actually has a timestamp of 2010-06-16 but that might just be 'cos I'm in NZ
<wolfspraul>
from your log, my guess is that after the bootloader has been flashed successfully, usbboot looses connection with the Nano
<wolfspraul>
(can't read bulk data)
<neil_>
wolfspraul: ok, will try the kernel now then
<wolfspraul>
all errors after that are just because usbboot lost connection
<wolfspraul>
yeah let's try that
<wolfspraul>
maybe you get other errors
<wolfspraul>
also kernel is bigger, so that's good
<wolfspraul>
neil_: I have another idea - my favorite :-) microSD booting
<wolfspraul>
do you have a microSD card?
<neil_>
wolfspraul: it says scarier things like "Comparing 524288 bytes - FAIL at off 3008, wrote 0x37, read 0xb5"
<wolfspraul>
preferably a smaller one, 1 GB or so there is a bug in u-boot with larger microSD cards right now
<wolfspraul>
neil_: yeah OK.
<wolfspraul>
I doubt this is your Nano, it's USB related.
<wolfspraul>
just a guess
<neil_>
wolfspraul: yes, 2GB uSD just arrived this morning.  it says it's Kingston but I suspect it's not after reading Bunnie's report
<wolfspraul>
do you have a microSD card?
<wolfspraul>
hah
<wolfspraul>
Bunnie's report is awesome!
<neil_>
wolfspraul: too true
<wolfspraul>
ok let's try this
<neil_>
wolfspraul: I could try on another laptop first if that's better
<wolfspraul>
partition the microSD card, one big ext2 partition
<wolfspraul>
unpack the openwrt rootfs into the root of that partition
<wolfspraul>
(you have to download the .tar.gz file)
<wolfspraul>
put the kernel into /boot/uImage on the microSD filesystem
<wolfspraul>
then insert the microSD into your Nano, boot the Nano and hold the 'm' key
<wolfspraul>
with some luck it should boot openwrt from the microSD card
<wolfspraul>
yes, another laptop is also good, we collect more data
<wolfspraul>
sorry for the inconvenience, your type of problem is new to me, never seen this kind of thing
<neil_>
wolfspraul: sorry for delay.  had to open the impossible packaging around the uSD card
<wolfspraul>
and then put this file into /boot/uImage (on the microSD card)
<wolfspraul>
neil_: it's a long shot, but we should try
<wolfspraul>
my assumption is that your u-boot reflashed correctly (even though you got errors), and that your microSD card will not exhibit the bug we have in u-boot right now that makes > 50% of microSD cards fail booting
<wolfspraul>
let's see :-)
<neil_>
wolfspraul: doing all that now
<urandom_>
seems like python-gtk ipkg doesnt work on openwrt ben, also ruby-ncurses might not work
<urandom_>
at least pygame seems to work
<neil_>
urandom_: pygame is ported!?  cool
<nebajoth>
oh snap
<nebajoth>
apt-get install pygame
<neil_>
wolfspraul: do I just rename this blahblah-uImage.bin file to uImage on the SD?
<wolfspraul>
yes
<wolfspraul>
make sure to put it in /boot/uImage
<neil_>
wolfspraul: ok.  I was going to put it in /, so good catch
<neil_>
wolfspraul: ok, all that is done
<wolfspraul>
kewl
<wolfspraul>
:-)
<neil_>
nebajoth: do you mean pygame for Debian on NN or pygame on OpenWRT?
<wolfspraul>
put it into the Nano, press power_on and hold the 'm' key
<urandom_>
when someone made a package for python-gtk and put it in the repo wouldnt he test it?
<neil_>
wolfspraul: sorry I only just thought of this: the battery has been out the whole time, powered only by USB
<neil_>
wolfspraul: could that be a problem?  maybe my USB port power is drooping or something. anyway, should I leave it as-is or replace the battery before booting the SD?
<wolfspraul>
hmm
<wolfspraul>
shouldn't matter
<urandom_>
neil_ we have pygame for openwrt and debian, apt-get is for debian
<urandom_>
and jlime i think
<wolfspraul>
unplug the cable once (without battery) to make sure you start from a clean zero state
<neil_>
urandom_: that is very cool.  no need for me to cross-compile to develop most stuff then
<wolfspraul>
I have seen USB hosts that indeed had power problems (good idea!)
<wolfspraul>
but let's just try this microSD booting now
<urandom_>
i personaly dont like pygame, ulove will be much better
<wolfspraul>
urandom_: remember we are just a few people and essentially doing a whole distro for an embedded device here
<wolfspraul>
test plan is sorely missing, I agree
<wolfspraul>
but I have a feeling I will have to focus on reflash & software update issues for quite a while, as you see there are still too many people who get stuck on that.
<wolfspraul>
with all the people that are helping we have made tremendous progress, but I think there are 2000+ packages in openwrt, and of course most of them are untested
<wolfspraul>
jlime has 18,000 packages or so, 2 or 3 volunteers :-)
<wolfspraul>
neil_: how's it going?
<neil_>
wolfspraul: wow. booted.  has desktop.  not seen that before.  quite flickery
<wolfspraul>
yeah, flickering
<wolfspraul>
sorry
<wolfspraul>
software bug, no worries
<neil_>
wolfspraul: it worked though!
<wolfspraul>
not a hardware issue, definitely not
<urandom_>
i am not sure if we even should keep openwrt as a main distro, i mean i like it but maybe jlime is better
<neil_>
wolfspraul: I'll try dClock, "x" later on
<wolfspraul>
neil
<wolfspraul>
one sec
<wolfspraul>
we haven't reflashed your NAND properly yet
<wolfspraul>
let's make sure all is good there
<neil_>
wolfspraul: yes, sorry I didn't think we were done.  mislead you there
<nebajoth>
the strength of going with openwrt as the main supported distro
<wolfspraul>
hmm
<nebajoth>
is that it lends itself to targetting specific niches
<wolfspraul>
I need help
<wolfspraul>
:-)
<nebajoth>
it enables people to put together custom mini-distros
<nebajoth>
without all the overheard of OE
<wolfspraul>
neil_ has a working u-boot in NAND, but kernel and rootfs not yet
<nebajoth>
which is what is used to build jlime, I believe
<wolfspraul>
I know how to write the rootfs from inside Linux, but never done the kernel
<nebajoth>
you mean the commandline commands to flash it?
<wolfspraul>
(maybe you can find it on your host, reflash_ben.sh must have downloaded it already)
<wolfspraul>
copy that file onto your microSD card
<wolfspraul>
(first turn off your Nano)
<wolfspraul>
then boot Nano again, with that -root.ubi file on the microSD card
<neil_>
wolfspraul: ok.  doing
<wolfspraul>
then after you booted, you go into command line and run "ubiformat /dev/mtd2 -f -root.ubi"
<wolfspraul>
and "ubiformat /dev/mtd3" (that's the empty 1.5 GB data partition to speed up boot times for now)
<wolfspraul>
so basically we have u-boot in mtd0 (already working), rootfs in mtd2 (see whether ubiformat runs through), empty data partition in mtd3 (also let's see what ubiformat says)
<wolfspraul>
then the only thing missing will be mtd1, we have to get your /boot/uImage copied/flashed into /dev/mtd1
<wolfspraul>
maybe just cat or cp ?
<wolfspraul>
nebajoth: yes, that's what I meant
<wolfspraul>
how can neil_ get the /boot/uImage kernel into flashed into /dev/mtd1 ?
<wolfspraul>
hmm, mtd-utils has a 'flashcp' command, maybe use that to copy the uImage to /dev/mtd1 ?
<nebajoth>
cat /proc/mtd
<nebajoth>
there's the three partitions
<wolfspraul>
should be 4 now
<nebajoth>
4 on mine
<nebajoth>
er
<nebajoth>
3
<wolfspraul>
but we need a command to do 'the right thing', i.e. to copy the uImage to /dev/mtd1, not assuming uImage contains any OOB data, and skipping bad blocks if necessary