DocScrutinizer05 changed the topic of #neo900 to: | conversations are logged to and
Humpelstilzchen has quit [Ping timeout: 264 seconds]
Humpelstilzchen has joined #neo900
<wpwrak> better than trying to guess tail would be to use sed :)
<DocScrutinizer05> particularly since they use sed elsewhere in same script
<DocScrutinizer05> but a script that's suppoesed to "install everywhere" is rather interesting
<DocScrutinizer05> duh, another 20,00 EUR PP donation
<DocScrutinizer05> >> Mitteilung des Käufers: Keine Angabe <<
<DocScrutinizer05> always makes me feel bad. Would be so much nicer when they actually would add a note "just to support you guys, have a beer on me!"
<DocScrutinizer05> otherwise you never know if some guy in SUNNYVALE, CA 94087 expects to get a device for that 20 bucks
rjeffries has quit [Ping timeout: 256 seconds]
heinrich5991 has quit [Ping timeout: 419 seconds]
heinrich5991_ has joined #neo900
heinrich5991_ is now known as heinrich5991
rjeffries has joined #neo900
ecloud has quit [*.net *.split]
sixwheeledbeast has quit [*.net *.split]
lobito has quit [Ping timeout: 248 seconds]
ecloud has joined #neo900
sixwheeledbeast has joined #neo900
lobito has joined #neo900
<DocScrutinizer05> [2015-04-14 Tue 06:49:50] <wpwrak> oh, and all prices are in USD. so Neo900 had become some 1/3 more expensive to make since the reorg
<wpwrak> blame merkel :)
<DocScrutinizer05> Draghi?
<wpwrak> (20 bucks) it's sunnydale. and you don't want to mess with those folks :)
<DocScrutinizer05> NFC what's sunnydale
<wpwrak> never seen buffy the vampire slayer ? :)
<DocScrutinizer05> when I don't want to mess with them, I prolly should retour the donation, right?
<wpwrak> not sure if they accept returns at the hell hole they have there
<DocScrutinizer05> PP probelm, not mine
<DocScrutinizer05> I mean, what's worse: a donor who wants to give us 20 bucks for the love of it who gets frustrated when it comes back to him, or a customer in spe not finding any account and device reserved for him when he comes claiming his 20 bucks down payment
<wpwrak> isn't there at least an e-mail ? then you could just ask
<DocScrutinizer05> k, feeling a tad exhausted, going afk for a while
<DocScrutinizer05> (ask) I'm tired of asking
<DocScrutinizer05> why ask when I can write a comment in the PP storno
<DocScrutinizer05> when it's been meant to be a true donation, the donor can redo the PP payment and this time add a comment to seller
<wpwrak> added a few chips that we're considering, plus fixed some digi-key links (they've been busy renaming catalog items)
<wpwrak> seems a bit rude to just reject the payment
<DocScrutinizer05> just reject? I'm adding a sorry in the comment on PP, something the donor should have done (add comment) on initial payment to start with
<DocScrutinizer05> jet to get decided what's more rude
<DocScrutinizer05> also a lot of PP users are not prepared to receive any mail except from paypal to the mail addr they use for PP
<DocScrutinizer05> wait, where's the QTH of spacefalkon?
<DocScrutinizer05> meh, I have no idea where is sunnydale
<DocScrutinizer05> and honestly this already costs more effort to process than it's worth
<DocScrutinizer05> n8
<x29a> wpwrak: you were kind of kidding of returning the donation, right?
<x29a> im not sure that got all the way to DocScrutinizer05
<wpwrak> x29a: problem is that he doesn't know that it's intended for and that there could be a misunderstanding
<freemangordon> DocScrutinizer05: what has happened with the relay card?
<DocScrutinizer51> why?
<freemangordon> ivo@europa:~> relaycard-reset-BB-pimped
<freemangordon> relaycard: Searching for '/sys/bus/usb-serial/drivers/cp210x/ttyUSB*'
<freemangordon> relaycard: Relay Card USB adapter not found! ABORTING...
<DocScrutinizer51> hmmm
<DocScrutinizer51> plugged it to a hub
<DocScrutinizer51> swapping back
<x29a> wpwrak: i dont get why a donation has to have a purpose?! is that a tax regulation? isnt there a minimum amount in order to qualify for a fon? if its below, its an unbound donation. done.
<DocScrutinizer51> ouch, I guess it collides with the USB serial adapter
<x29a> if in doubt, keep the money, put it into bookkeeping and deal with it once the neo900 is available
<x29a> its not like there is too much money, from what i read
<freemangordon> DocScrutinizer05: rs232 on pipmed card is attached to which tty?
<DocScrutinizer05> relaycard-reset-BB-pimped WFM
<DocScrutinizer05> pimped is on mainbpboard RS232
<freemangordon> ok, works now
<DocScrutinizer05> freemangordon: you lighted a few leds on BB_pimped that never before were lit
<freemangordon> I booted nik's u-boot
<DocScrutinizer05> next time you click the reset relay, I'll power down and up again the complete board completely a 3 s later and
<DocScrutinizer05> freemangordon: ^^^
<freemangordon> DocScrutinizer05: hmm?
<DocScrutinizer51> i wanna reset the leds et al
<DocScrutinizer51> not sure what been their state
<freemangordon> DocScrutinizer05: ah,ok. anyway, I don't have more time to play with it now, have to go to work :)
<DocScrutinizer51> so i may reset noard?
<freemangordon> yep
<DocScrutinizer51> k
<DocScrutinizer51> yup i wasright,
<DocScrutinizer51> only one led now
<freemangordon> :)
<DocScrutinizer51> cpu reset doesn't reset leds
<freemangordon> makes sense
lobito has quit [Read error: Connection reset by peer]
lobito has joined #neo900
Pali has joined #neo900
kolp has joined #neo900
sparetire has quit [Quit: sparetire]
mvaenskae has quit [Ping timeout: 264 seconds]
SylvieLorxu has joined #neo900
modem has joined #neo900
jonsger has joined #neo900
Chat-ron has joined #neo900
silviof has quit [*.net *.split]
rjeffries has quit [Ping timeout: 250 seconds]
Humpelst1lzchen has joined #neo900
Humpelstilzchen has quit [Ping timeout: 246 seconds]
Kabouik_ has quit [Quit: No Ping reply in 180 seconds.]
Kabouik has joined #neo900
raccoon_ has joined #neo900
raccoon_ has quit [Changing host]
raccoon_ has joined #neo900
<Chat-ron> hi
<Chat-ron> does someone in charge of FPTF is here ?
<Chat-ron> I was wondering if Maemo 5 on the Neo900 will be built with the hard float point like Harmattan or Sailfish, or still with the soft point ?
<Humpelst1lzchen> hmm the nokia binary blobs probably won't work with hf
<Chat-ron> I read that soft point binaries will work on armhf os
<Chat-ron> like the Maemo 5 apps on Harmattan
<Chat-ron> however, the contrary will not work, we can't run armhf apps on Maemo 5 for the moment
jonsger has quit [Ping timeout: 250 seconds]
rjeffries has joined #neo900
jonsger has joined #neo900
jonsger has quit [Ping timeout: 248 seconds]
rjeffries has quit [Ping timeout: 264 seconds]
<DocScrutinizer05> the difference is so marginal, it's not worth worrying, I guess
jonsger has joined #neo900
xeal has quit [Read error: Connection reset by peer]
mvaenskae has joined #neo900
<Chat-ron> actually it depends of if you want to have an OS which will launch only the few apps fo Maemo 5 or also the apps from Meego, Sailfish, and eventually Ubuntu Touch
<DocScrutinizer05> well, maemo is maemo is maemo, even on Neo900. We're planning to simply re-use the binaries existing for N900
<DocScrutinizer05> this pretty much defines what open-fremantle will look like
<DocScrutinizer05> or simply see what Humpelst1lzchen said
<Chat-ron> it could be a better idea to rebuild Maemo with hard float point ; the old apps will still runs, but also the apps from other OSes
<DocScrutinizer05> when we could "rebuild maemo" we wouldn't have to port it
<Chat-ron> I thought one of the goal was to have a completly free OS with no Nokia binaries
<DocScrutinizer05> no, that's not really the main goal. The main goal is to have maemo running at all
<DocScrutinizer05> he collateral benefit of getting rid of closed blobs during that porting process is secondary
<Chat-ron> so why making a new camera apps which is basicly a clone of the Nokia one ? and the same for few other componments
<bencoh> Chat-ron: which part would you need to "rebuild" as armhf ?
<bencoh> kernel + libs ?
<Chat-ron> yes bencoh
<DocScrutinizer05> hf is an issue only for apps using floats anyway
<bencoh> using floats in function calls*
<Chat-ron> but users can't know if an app uses floats or not without reading the source code
<DocScrutinizer05> and honestly why rebuild maemo apps and core to make it compatible with copied binaries from sailfish et al, that doesn't sound wise to me
<Chat-ron> because apps from Sailfish are not copies from Maemo apps
<DocScrutinizer05> when I'm interested in sailfish apps the I rebuild *those* to run on maemo non-hardfloat
<Chat-ron> and I didn't ask to rebuild all of the Maemo apps
<bencoh> my personal opinion regarding foreign apps is "rebuild them anyway whenever you can"
<bencoh> (just to avoid adding blobs to blobs)
<DocScrutinizer05> exactly, bencoh
<bencoh> (and because I dont like the idea of 3rd-party closed-source software)
<DocScrutinizer05> and when any such 3rd party blobs then those which are built for maemo, not for sailfish
<Humpelst1lzchen> bencoh: /sign, but still I'ld like to see a usable system first.
<Chat-ron> I don't like the idea of spending a whole week-end for rebuilding an app
<bencoh> Humpelst1lzchen: same :)
<DocScrutinizer05> and anyway the whoöe discussion is moot, we have at least the PVR blob we want to be able to re-use
<bencoh> Chat-ron: you'd probably spend a whole weekend porting the the qt/silica/whatever components anyway
<DocScrutinizer05> Chat-ron: look, when you''re interested in sailfish then why not run sailfish on Neo900 genuinely
<DocScrutinizer05> you don't need maemo to run sailfish apps
<Chat-ron> I think than rebuilding librairies will cost less time than all of the Sailfish/Ubuntu Touch/Meego apps
<DocScrutinizer05> ohmy
<Chat-ron> DocScrutinizer05: I am not even sure if sailfish will run smoothly on the Neo900
<DocScrutinizer05> I'm absolutely sure sailfish APPS will NOT
<bencoh> DocScrutinizer05: he means, sailfishos
<DocScrutinizer05> under maemo, when not massively tweaked anyway
rjeffries has joined #neo900
<DocScrutinizer05> bencoh: I know
<Chat-ron> DocScrutinizer05: currently, indeed, since Maemo is not built with hard float point
<bencoh> Chat-ron: even if it was built with hf
<Chat-ron> I see
<DocScrutinizer05> but it doesn't make sense to try and make sailfish apps run on maemo on Neo900 when sailfish *OS* can't run smoothly on Neo900 (which of course is not the case, sailfish will run just fine after porting it)
<DocScrutinizer05> Chat-ron: trying to run a sailfish binary under maemo, hf is your least problem
<DocScrutinizer05> Chat-ron: anyway you're free to rebuild maemo with build flag hf and then add all the needed libs and drivers/daemons for sailfish
<DocScrutinizer05> just FPTF won't do that, I guess
<Chat-ron> I see thank for your anwser
<bencoh> I'm not sure fptf would have the means to do it
<Chat-ron> and what is the targeted kernel ? the old one of Maemo 5 or a new one ?
<DocScrutinizer05> there are blobs in kernel which we want to re-use and those are pretty much exactly the place where hf matters
<bencoh> we still have quite a few closed-source libs
<DocScrutinizer05> well, close to kernel, implemented as libs, right
<DocScrutinizer05> opengl-es2 stuff for example
<DocScrutinizer05> gfx stuff at large
<bencoh> those could come from a different provider :)
<DocScrutinizer05> let's see
rjeffries has quit [Ping timeout: 245 seconds]
<DocScrutinizer05> but honestly why would we rebuild all maemo to make it binary compatible to OS-XY which it won't be anyway
<DocScrutinizer05> wouldn't it be much smarter to stay binary compatible to maemo?
<Chat-ron> indeed, if they will not be compatible, there is no reason
<Chat-ron> and what about the kernel ? is there any plan to use a newer one ?
<Chat-ron> well I have to leave, thank for the answer
Chat-ron has quit [Quit: Leaving.]
infobot_ has quit [Read error: Connection reset by peer]
infobot has joined #neo900
dal2 has joined #neo900
<DocScrutinizer05> infobot: wb
<infobot> thx
<DocScrutinizer05> infobot: +uptime
<infobot> - Uptime for apt -
<infobot> Now: 3m 45s running infobot 1.5.4 (SVN) -- linux
<infobot> 1: 59d 8h 41m 19s running infobot 1.5.4 (SVN) -- linux, ended Sun Nov 14 18:39:57 2010
<infobot> 2: 57d 3h 9m 23s running infobot 1.5.4 (SVN) -- linux, ended Fri Jun 26 20:39:27 2009
<infobot> 3: 36d 20h 47m 14s running infobot 1.5.4 (SVN) -- linux, ended Tue Aug 4 17:38:59 2009
arcean has joined #neo900
jonsger has quit [Ping timeout: 264 seconds]
che1 has joined #neo900
<DocScrutinizer05> freemangordon: I again conected the USB hub and the relaycard to hub. It failed initially like this morning, but a firm pushing in of the hib's USB cable to PC USB port finally made it work again
<DocScrutinizer05> advantage of recent setup: I have a mouse again on europa, plus a 2 free USB ports on hub now
<DocScrutinizer05> ((firmly attach plug)) see /var/log/messages ~18:11 to 18:16
<DocScrutinizer05> the lines in script
<DocScrutinizer05> # find device based on name of kernel driver for IR adapter
<DocScrutinizer05> dev=/dev/$(basename ${IRdrv}/ttyUSB*)
<DocScrutinizer05> if [ "$dev" == "/dev/ttyUSB*" ]; then
<DocScrutinizer05> echo -e "${self}: Searching for '${IRdrv}/ttyUSB*'\n${self}: Relay Card USB adapter not found! ABORTING..."
<DocScrutinizer05> exit 5
<DocScrutinizer05> fi
<DocScrutinizer05> do exactly what they're supposed to do
<DocScrutinizer05> alas it still has that quirk of
<DocScrutinizer05> europa:/usr/local # relaycard-reset-BB-plain
<DocScrutinizer05> stty: standard input: unable to perform all requested operations
<DocScrutinizer05> on first invocation of stty
<DocScrutinizer05> I'm a tad reluctant to simply give stty command twice in series in that script, looks embarrassing
<DocScrutinizer05> but would help
<DocScrutinizer05> ;-)
<DocScrutinizer05> anyway on second and subsequent invocations of relaycard it works as supposed to, since ttyUSB1 got correctly configured by previous partial and new (second, third etc) stty call
<DocScrutinizer05> tty my ass
<freemangordon> ok
jonsger has joined #neo900
alifakhruddin has joined #neo900
alifakhruddin has left #neo900 [#neo900]
<Wizzup> DocScrutinizer05: he seems somewhat gentle there
<DocScrutinizer05> well, I'm not really intersted in LP and what he does or says -- as long as I got ways to steer clear of any results of his work
<DocScrutinizer05> I'm not even sure plymouth is to blame. Might be a genuine bug in the way stty works
Kabouik_ has joined #neo900
<DocScrutinizer05> anyway "stty: standard input: unable to perform all requested operations" means stty checked the actual setting in effect after trying to change them, and noticed there's a difference, so it throws that error msg
Kabouik has quit [Ping timeout: 276 seconds]
sparetire has joined #neo900
<wpwrak> poettering wrote plymouth ?
<DocScrutinizer05> I don't even know what *is* plymouth
<DocScrutinizer05> but yeah I think it's somehow related to systemd/poettering stuff
<DocScrutinizer05> wild guessing based on hearsay since I never really cared
<wpwrak> something that is really good at hogging the console and making it impossible to get into the system after booting. so far, i haven't seen any other use of it.
<wpwrak> needless to say, it's on my hate list right after the local government
<DocScrutinizer05> >>Apparently we need to run the serial gettys after plymouth finished stopping, since otherwise plymouth will configure weird settings to the tty and lock them, so that other tools cannot change them anymore.<< WTF?
<wpwrak> i wonder if rd_NO_PLYMOUTH isn't just some redhatism
<DocScrutinizer05> nfc
<DocScrutinizer05> I dunno what's plymouth and I don't know of any such kernel cmdline either
<wpwrak> this looks encouraging, though:
<wpwrak> gack :) stty -g is evil
<DocScrutinizer05> the ubuntu thread is about getting rid of framebuffer and early(?) bootlog. I rather want that log, not get rid of it. AIUI plymouth is just about the splash screen that covers the logs until you hit ESC key to show them
<bencoh> :]
<DocScrutinizer05> freemangordon: you once more "lighted the xmas tree" ;-)
<freemangordon> cd yeah
<freemangordon> oops
<freemangordon> yeah
<freemangordon> I am playing with differn u-boots
<DocScrutinizer05> :-)
<kerio> DocScrutinizer05: just stop using grub2
<kerio> and start using a serious bootloader
<kerio> like extlinux
<wpwrak> lilo :)
<DocScrutinizer05> hehe
<DocScrutinizer05> kerio: don't mess with the master of bootloaders ;-D
<kerio> no seriously, extlinux is like
<kerio> simple
<kerio> which is a GOOD thing, for a bootloader
<kerio> the mbr bootloader is always the same
<DocScrutinizer05> please discuss all BL topics with Werner almesberger aka wpwrak
<kerio> k
<kerio> wpwrak: use extlinux u motehrfucker
<kerio> its good
<kerio> it's like self explanatory
<DocScrutinizer05> kerio: please watch your speech
<kerio> very much unlike grub
<kerio> NO >:C
<kerio> fuck da police
<DocScrutinizer05> kerio: even when pun intended, it doesn't convey on IRC
<DocScrutinizer05> I am supposed to stop all personal insults and offensive speech to other users in this channel. I'm maybe often tolerating when those are targeted at me, particularly since I know our best troll ;-)
<wpwrak> lilo is kinda simple. and has good documentation, in case you need to do not so simple things with it :)
<kerio> i should probably try it for the VMs actually
<kerio> debian's extlinux is somewhat awkward to configure to use the serial console
<wpwrak> DocScrutinizer05: what does the moon care if the dogs bark at her :)
<DocScrutinizer05> kerio: just in case you're in lack of background info:
* kerio didn't know that!
<kerio> wpwrak: why do people use grub
<kerio> is the pretty background the only reason
<DocScrutinizer05> wpwrak: (moon) sure, but anyway I'm responsible to keep the tone polite and sort of safe for workplace in this channel
<kerio> DocScrutinizer05: ur mom is a CLASSY LADY
<DocScrutinizer05> kerio: please don't push it
<kerio> k :c
<DocScrutinizer05> btw my mom died ~30 years ago
<kerio> literally anti-fun
<kerio> rip :c
norly has joined #neo900
<DocScrutinizer05> fun is not limited to using offensive or nearly offensive speech towards other chan members
<DocScrutinizer05> on a sidenote: it a strangly convenient and satisfactory feeling to hear the click...clack form reset relay from over next room where europa remote tesbench is busy under freemangordon's hacking ;-)
<freemangordon> :)
<DocScrutinizer05> actually could somebody fluent in this markup gibberish add a "... member of core team since mid of 2014..." to
<DocScrutinizer05> please?
modem has quit [Disconnected by services]
modem_ has joined #neo900
modem has joined #neo900
modem_ has quit [Client Quit]
dal2 has quit [Quit: Leaving.]
<DocScrutinizer05> freemangordon: are there any statistical errors you face with the BB bootup? sth that could be caused by europa system?
<freemangordon> sometimes 1st stage toesn boot, goes ok on the second try
<freemangordon> no idea what causes that
<DocScrutinizer05> you're watching log/messages?
<DocScrutinizer05> timing for ROMBL check is rather tight
<freemangordon> no, it got loaded, but then nothing
<DocScrutinizer05> that does sound like a problem inside BB
<freemangordon> so I'd rather blame the board itself, not your setup
<freemangordon> yeah
<DocScrutinizer05> should I add power-cycling reset to the BB_pinped?
<DocScrutinizer05> for now I could just plug the power jack currently used on BB_plain
<freemangordon> dunno, how hard is that?
<DocScrutinizer05> takes 30s
<freemangordon> ok
<DocScrutinizer05> ok, mompls
<freemangordon> and I should yse the relay script for plain?
<freemangordon> *use
<DocScrutinizer05> yes
<freemangordon> ok
<DocScrutinizer05> done
<freemangordon> 10x
<DocScrutinizer05> relaycard-reset-BB-plain now does a power-cycle reset on BB_pimped
<freemangordon> yep
<DocScrutinizer05> this one takes 5s due to power-down time
<merlin1991> that sounds odd, having the bb-plain script reset the bb-pimped board
<freemangordon> :)
<merlin1991> unless it's just a naming thing
<DocScrutinizer05> relaycard-reset-BB-pimped still does the normal button-press reset
<freemangordon> dammit, can't get u-boot running
<DocScrutinizer05> merlin1991: both scripts just toggle a relay on my 8-relay card
<merlin1991> yeah but how do you refer to the non bb-pimped board?
<DocScrutinizer05> err, "refer to"?
<freemangordon> merlin1991: mo way
<freemangordon> *no
<merlin1991> if that is called bb-plain the a script called relaycard-reset-BB-plain ressing bb-pimped is missleading
<DocScrutinizer05> BB_plain now has no way to reset it
<freemangordon> but it is not really needed now
<merlin1991> jeez I left out about 10 characters in my line :D
<merlin1991> what I meant to say is that if you call the "plain" bb board plain then having a script with plain in the name reset the pimped board can be the basis of 2 hours of debuging why the fuck it doesn't work
<DocScrutinizer05> jr@europa:~> cat `which relaycard-reset-BB-pimped `
<DocScrutinizer05> #!/bin/sh
<DocScrutinizer05> #set (03) on card 01 relay 01 for 1s then reset
<DocScrutinizer05> /usr/local/bin/relaycard 03 01 01
<DocScrutinizer05> sleep 1
<DocScrutinizer05> /usr/local/bin/relaycard 03 01 00
<DocScrutinizer05> .
<DocScrutinizer05> jr@europa:~> cat `which relaycard-reset-BB-plain `
<DocScrutinizer05> #!/bin/sh
<DocScrutinizer05> #set (03) on card 01 relay 08 for 5s then reset
<DocScrutinizer05> /usr/local/bin/relaycard 03 01 80
<DocScrutinizer05> sleep 5
<DocScrutinizer05> /usr/local/bin/relaycard 03 01 00
<freemangordon> hmm, as long as I enable DDR setup in xloader, u-boot just hangs
<DocScrutinizer05> o.O
<DocScrutinizer05> dang, it worked with 1GB RAM before, no?
<DocScrutinizer05> even booted to linux
<freemangordon> not on that board
<DocScrutinizer05> right, not on that board
<freemangordon> hmm, lemme check if it is nand ini that bugs it or DDR init
<DocScrutinizer05> with 512MB RAM it works?
<freemangordon> with 256
<DocScrutinizer05> weird
<freemangordon> OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
<freemangordon> OMAP3 Beagle board + LPDDR/OneNAND
<freemangordon> I2C: ready
<freemangordon> DRAM: 256 MiB
<freemangordon> Muxed OneNAND 512MB 1.8V 16-bit (0x50)
<DocScrutinizer05> then *if* it was a hw issue, it prolly must be high addr bit and/or cs1
<freemangordon> will check what happens now
<DocScrutinizer05> sounds good, yeah
<freemangordon> will disable everything onenand and will enable DDR init only
<DocScrutinizer05> check NAND even while only 256MB RAM
<freemangordon> won;t fly, iiuc n9 xloader does some trickery for that onenand
<DocScrutinizer05> I mean, when we get NAND working on this board, we might ignore trouble with 1GB RAM until we can reproduce same trouble on other board too
lobito has quit [Quit: Leaving.]
lobito1 has joined #neo900
<DocScrutinizer05> the reason why we got 2 boards reworked was exactly to rule out hw issues on one of them
<merlin1991> hm I wonder how much power my desk draws during my daily use
<DocScrutinizer05> when on pimped the RAM is borked somehow, we still may test NAND on this one until we find a solution that suggests it should also work on the other pimped board that worked with 1GB RAM
<DocScrutinizer05> then on other board first test NAND with same 246MB RAM setting, then add 1GB RAM init on top of that when NAND works on the other board too
<DocScrutinizer05> 256*
<DocScrutinizer05> >><freemangordon> Muxed OneNAND 512MB 1.8V 16-bit (0x50)<< sounds like worth giving it a try what NAND does
<DocScrutinizer05> afk, newsflash and then shower
<DocScrutinizer05> freemangordon: you noticed the wall msg I sent this morning? about write permissions on /usr/local/bin and please store all useful stuff there instead keeping it in $HOME ?
<DocScrutinizer05> sidenote: I just unplugged BB_plain USB to avoid somebody headdesking why it doesn't reset
<freemangordon> DocScrutinizer05: unfortunately it seems we have HW problem
<freemangordon> either my 1GB init function is buggy (but why the it worked on the other board) or there is a HW problem
<freemangordon> anyway, I have my xloader booting u-boot with 256
<freemangordon> like on n900 eh?
<freemangordon> :)
<DocScrutinizer05> rework on PoP stack in a populated board is about as complex as it gets regarding any rework/pinping that you might do. HW problems pretty much expected to be seen in maybe 30% of reworks
<freemangordon> yeah, sure
<DocScrutinizer05> you tested power-cycle reset?
<freemangordon> yes
infobot has quit [Read error: Connection reset by peer]
<DocScrutinizer05> *sigh* the bot reboots too :-)
silviof has joined #neo900
infobot has joined #neo900
<DocScrutinizer05> ~wb
<infobot> thx
<DocScrutinizer05> freemangordon: you noticed the wall msg I sent this morning? about write permissions on /usr/local/bin and please store all useful stuff there instead keeping it in $HOME ?
<freemangordon> no, but I noticed it now
<freemangordon> will move the binaries, when it comes to it :)
<DocScrutinizer05> wait, please no blobs in */bin/*
<DocScrutinizer05> blobs like BB frimware (xloader etc)
<DocScrutinizer05> I'll create a central dir for storing such stuff
<freemangordon> yeah, got it, will move executables
<DocScrutinizer05> europa:/usr/share/neo900 # ll -d `pwd`
<DocScrutinizer05> drwxrwxr-x 1 root remotehacker 0 Apr 14 21:59 /usr/share/neo900
<DocScrutinizer05> for .bin stuff etc
<DocScrutinizer05> create subdirs as you see fit
<DocScrutinizer05> please
<freemangordon> ok. but not now, please :)
<DocScrutinizer05> :-) afk for a while now
<DocScrutinizer05> hmm?
<DocScrutinizer05> the /usr/share/neo900 stuff? nah, whenever you feel like storing something
<DocScrutinizer05> what the heck, there's freenode-internal lags like mad it seems
<DocScrutinizer05> [2015-04-14 Tue 22:19:17] <DocScrutinizer05> :-) afk for a while now
<DocScrutinizer05> [2015-04-14 Tue 22:19:28] <freemangordon> ok. but not now, please :)
<DocScrutinizer05> on DocScrutinizer51 the sequence was inverted, your post been before mine
<DocScrutinizer05> o.O
<DocScrutinizer05> [2015-04-14 Tue 22:23:46] [CTCP] Sending CTCP-PING request to freemangordon.
<DocScrutinizer05> [2015-04-14 Tue 22:23:58] [CTCP] Received CTCP-PING reply from freemangordon: 12 seconds.
<DocScrutinizer05> o/
<freemangordon> ok, upstream u-boot seems to work, lets see if it supports onenand better
<freemangordon> DocScrutinizer05:
<DocScrutinizer05> great!
<DocScrutinizer05> now try writing and reading back some arbitrary data to/from it
<freemangordon> did it, same result, seems more things have to be enabled in u-boot
<DocScrutinizer05> same result as in "it doesn't work"?
<freemangordon> same result is nik, "written 0 bytes: OK" :)
<freemangordon> *as
<DocScrutinizer05> well, that's a tad weird, anyway maybe look what uboot does when it says this. Also trying to read a huge chunk may help
<DocScrutinizer05> maybe there's a certain minimum size that can get read/written at once
<DocScrutinizer05> possibly one page
<DocScrutinizer05> wild guessing
<DocScrutinizer05> try read first
<DocScrutinizer05> when read of arbitrary chunks works, then see if a page can get written
<DocScrutinizer05> ubbot must have an idea about the "filesystem" on OneNAND
<freemangordon> OneNAND read: offset 0x0, size 0x100000
<freemangordon> 1048576 bytes read: OK
<freemangordon> :)
<DocScrutinizer05> hmm sounds better
<DocScrutinizer05> where to does it read it?
<freemangordon> yeah
<freemangordon> in memory
<DocScrutinizer05> aaah so it is supposed to be in RAM now?
* DocScrutinizer05 has no clue about uBoot command syntax and semantics
<freemangordon> ok, seems like flash works
<DocScrutinizer05> o.O \o/???
<freemangordon> will send a mail in a couple of minutes
<DocScrutinizer05> WOW!
<DocScrutinizer05> you're aware that we got the chip evaluated and verified when that's true? So we could start sourcing them in bulk with confidence
<freemangordon> yep
<freemangordon> that is why I'll send a mial with what I did so far, so you can evaluate it
<DocScrutinizer05> freemangordon: you're the greatest! :-D
<freemangordon> evaluate what I did that is
<freemangordon> yeah, I know :P
<DocScrutinizer05> sure :-)
<DocScrutinizer05> next step: get both RAM and NAND working and boot into linux, but honestly that's just for bonus points
<DocScrutinizer05> and for real productive use later on ;-D
<DocScrutinizer05> you should publish your results on tmo too
<DocScrutinizer05> so community can drool on it and praise you :-)
<freemangordon> feel free to extract what you think makes sense from my mail, it is really pure technical stuff
<DocScrutinizer05> dang, there just been an inbound msg that went straight to /dev/null
<DocScrutinizer05> I hope that wasn't yours
kolp has quit [Read error: Connection reset by peer]
<freemangordon> DocScrutinizer05: btw, should I erase before writing?
<DocScrutinizer05> I guess yes, usually that's needed
<DocScrutinizer05> unless the page(s) are already erased, which is the whole purpose to have that NOR-like interface of OneNAND
<freemangordon> hmm, something happened with that board
<DocScrutinizer05> erasing takes "ages"
<freemangordon> doesn't boot anymore
<freemangordon> WTF?
<DocScrutinizer05> o.O
<freemangordon> I got "onenand_wait: controller error = 0x0400", reset it and nothing
<freemangordon> power cycle doesn't help either
<DocScrutinizer05> that's extremely weird
<DocScrutinizer05> lemme mate-cycle USB
<freemangordon> I am booting through serial
<freemangordon> hmm, I am afraid it got fried
<freemangordon> :(
<DocScrutinizer05> yeah, nevertheless last syslog I see is
<DocScrutinizer05> 2015-04-14T23:19:26.433463+02:00 europa kernel: [125565.221058] usb 1-2.3: USB disconnect, device number 67
<DocScrutinizer05> how the f*ck would uBoot fry a board?
<freemangordon> no idae, but rather it was fucked-up from the start - mmc iface, 1GB ram
<freemangordon> anyway, I'll email what I have so far
<DocScrutinizer05> only thing I faintly could imagine is NAND holding an 'xloader' that makes ROMBOOT hang
<freemangordon> oh
<freemangordon> this is it
<freemangordon> I wrote data to onenand
<freemangordon> :D
<DocScrutinizer05> but even then with the correct SYSBOOT setting it still should first check on serial before it even tries touching NAND
<freemangordon> you should tweak SYSBOOT to try serial first
<DocScrutinizer05> will inspect the board for SYSBOOT config, and fix it when due. Please suggest the right setting
<freemangordon> SYSBOOT[5:0]: 0x10/16
<DocScrutinizer05> ta
<freemangordon> no idea, it is in TRM
* freemangordon checks
<DocScrutinizer05> please add all this to your mail
<DocScrutinizer05> it is
<freemangordon> "0b10000 OneNAND USB UART3 MMC1"
<DocScrutinizer05> anyway this hw inspection and rework can't get done today, and tomorrow not between 00:00 and 02:00 ;-)
<freemangordon> yeah
<DocScrutinizer05> yeah, that's prolly what we got right now
<freemangordon> :nod:
<DocScrutinizer05> when OneNAND holds garbage, we're screwed
<freemangordon> well, I'll count it as a success :)
<DocScrutinizer05> it is :-D
<DocScrutinizer05> however 0x10 is "0b10000 OneNAND USB UART3 MMC1"
<DocScrutinizer05> so that's not what we wanna have
<DocScrutinizer05> right?
<DocScrutinizer05> that's what user may do to their Neo900 to secure it against cleaning woman attack
<freemangordon> right, we want is "0b10110 UART3 OneNAND"
<freemangordon> at least for now
<DocScrutinizer05> we want sth like "USB UART3 MMC1 OneNAND "
<freemangordon> can;t see it in TRM
<DocScrutinizer05> dunno if it exists
<DocScrutinizer05> I got the right setting in a mail from me to Nik in internal ML
<DocScrutinizer05> we discussed that a few weeks ago already
<freemangordon> anyway, going to write that mail and have some sleep
<DocScrutinizer05> yep, many thanks! :-)
<DocScrutinizer05> seems Nik only reworked the SYSBOOT settings of his board, not of the one he sent to me
<DocScrutinizer05> at least when SYSBOOT is actually the explanation of this "frying"
<freemangordon> I guess this is
* DocScrutinizer05 waves again and tries going afk
arcean has quit [Read error: Connection reset by peer]
Pali has quit [Remote host closed the connection]
SylvieLorxu has quit [Quit: ZNC -]
<DocScrutinizer05> what really sort of worries me: shouldn't ROMBOOT do a checksum or at least check a magic header before it accepts and loads and executes stuff in NAND? When it does this, then why does it hang? is there an incompatibility or hw defect in our OneNAND that makes ROMBOOT hang while trying to checksum the NAND content?
<DocScrutinizer05> when that's the case then we're basically screwed :-o
<DocScrutinizer05> we prolly can't get OMAP3730 with fixed bootloader
<DocScrutinizer05> ROMBOOT that is
<DocScrutinizer05> we only could hope for the problem being in a broken solder joint to the NAND PoP then
che1 has quit [Remote host closed the connection]
jonsger has quit [Quit: jonsger]
<DocScrutinizer05> freemangordon: is what we want
* DocScrutinizer05 humms "DEVO - Freedom of choice"
<DocScrutinizer05> well, *maybe* the ROMBOOT code is stupid, reads bogus length info from a garbage header and tries to checksum beyonf the end of NAND working addr space so it hangs on HW timeout error from NAND when trying to access illegal addr
<DocScrutinizer05> in that case we're not +completely* doomed, we still could recover from a bogus garbled NAND xLoader via coldflashing by USB
<DocScrutinizer05> given the SYSBOOT bits are set accordingly
<DocScrutinizer05> freemangordon: \o/ success!!!
<DocScrutinizer05> holding USER switch did the trick ;-)
<DocScrutinizer05> freemangordon: I fixed the issue with a paperclip ;-D
<DocScrutinizer05> IOW USER switch permamnetly pressed now
<DocScrutinizer05> freemangordon: tell me if you'd need SYS_BOOT5 resp USER switch controlled by another one of the relaycard outputs instead
<DocScrutinizer05> now for good: AFK o/
mvaenskae has quit [Quit: Lost terminal]
mvaenskae has joined #neo900
norly has quit [Quit: Leaving.]