DocScrutinizer05 changed the topic of #qi-hardware to: 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 and http://irclog.whitequark.org/qi-hardware
<mth> the bootrom checks whether OSTCNTL >= 9766 * v1
<mth> well, it explains why it reacts different to low values of v1, but what is it doing here?
<mth> (OSTCNTL is the lower 32 bit of the OS timer)
wolfspraul has joined #qi-hardware
wolfspraul has quit [Client Quit]
wolfspraul has joined #qi-hardware
<pcercuei> mth: I have no idea
xiangfu has joined #qi-hardware
<mth> there seem to be 3 instances of "goto <register>"
<mth> "jr t4" and "jalr s4" (2x)
<mth> the "jr t4" jumps into SRAM #2, so it's not used when executing code from the cache
<mth> this means we're being called by jalr and therefore have an address to return to
<mth> in both cases, the code returned to then immediately jumps to 0xbfc0128c
<mth> which is in the same routine as bfc0130c is, but earlier
<mth> the code that sets v1 is before 0xbfc0128c though
unclouded has joined #qi-hardware
freemor has joined #qi-hardware
Calyp_ has joined #qi-hardware
Calyp has quit [Ping timeout: 258 seconds]
wolfspraul has quit [Quit: leaving]
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
panda|x201 has quit [Ping timeout: 248 seconds]
emeb has quit [Quit: Leaving.]
freemor has left #qi-hardware [#qi-hardware]
wolfspraul has joined #qi-hardware
jekhor has joined #qi-hardware
unclouded has quit [Ping timeout: 245 seconds]
pcercuei has quit [Quit: dodo]
wolfspraul has quit [Quit: leaving]
jekhor has quit [Ping timeout: 272 seconds]
panda|x201 has joined #qi-hardware
wolfspraul has joined #qi-hardware
Caly__ has joined #qi-hardware
Calyp_ has quit [Ping timeout: 272 seconds]
Caly__ has quit [Ping timeout: 245 seconds]
Caly__ has joined #qi-hardware
<larsc> mth: we do have the bootrom asm
<larsc> well for the jz4740
unclouded has joined #qi-hardware
<mth> annotated asm or just objdump output?
<mth> because I got the latter for jz4770 now
<mth> by the way, preserving v1 and a0 fixes the problem
<mth> I'll be pushing the fix to ingenic-boot later (other changes still need cleanups)
unclouded has quit [Quit: Leaving]
<larsc> usbboot.S
<larsc> and yes it is annotated
<mth> I don't think this is the same code I'm talking about
lekernel has joined #qi-hardware
<larsc> well, it's the bootrom, at least the usbboot protocol part
<mth> inside the SoC itself, there is a small ROM area which at address 0x1fc00000
<mth> s/at/is at/
<qi-bot> mth meant: "inside the SoC itself, there is a small ROM area which is at address 0x1fc00000"
<larsc> yes
<mth> but the code you linked has a comment "Relocate code to beginning of the ram"
<mth> while the code in the SoC cannot bring up the RAM
<larsc> yes, I guess it has been modified to run in the ram instead of the rom
wolfspraul has quit [Quit: leaving]
<mth> there is some similarity in the way the USB controller is accessed, but the overall flow is very different
<mth> I don't know if that's because of JZ4740 and JZ4770 differences or not
<mth> the whole timeout mechanism that was causing problems for me doesn't exist in this version
<mth> thanks for the link though, it might be useful if I want to learn more about the protocol one day
<DocScrutinizer05> I think I already seen IR-RC made like this
<mth> they say it's great for children, but if it takes 2 hours to dry it's not really practical for experimentation
<larsc> I think the first thing I'd try is to see what happens when you use the conductive paint on skin ;)
cod3r has joined #qi-hardware
<DocScrutinizer05> if they actually use carbon fibre then this could get pretty nasty
<DocScrutinizer05> aaaah, seems there's something left over from Iraq war
<DocScrutinizer05> didn't they short power lines with carbon fibre bombs
<whitequark> DocScrutinizer05: huh?
<DocScrutinizer05> ========== <-powerline //\\/\/<- crbon fibres
<DocScrutinizer05> 50kV lines
<DocScrutinizer05> or 100kV
<DocScrutinizer05> they took power plants out by shorting the wires
<larsc> ⚡⚡⚡ ⚡⚡⚡
<DocScrutinizer05> now they probably recycled the surplus bombs and played "does it blend?" with the carbon fibres, then mixed it with wallpaper glue
<whitequark> won't that result in a huge discharge arc and failsafe switch on the plant?
<whitequark> and then it'll turn back on again
<larsc> if it has one
<whitequark> larsc: er... some of them don't?
<DocScrutinizer05> hmm, seems the shorts been permanent
<whitequark> DocScrutinizer05: I'm pretty damn sure the fiber will be vaporized
<whitequark> you can find lots of videos like that on 'tube
<DocScrutinizer05> it's carbon
<whitequark> so?
<DocScrutinizer05> well
<whitequark> it's not enough carbon to dissipate several MW
<DocScrutinizer05> the first few fibres take out the power plant and might evaporize or rather burn, the rest will happily sit on the powerless wires and short any next effort to power up the line again
<DocScrutinizer05> also wire cut is likely
<whitequark> DocScrutinizer05: (short any next effort) isn't the only thing you need to do is to power up the line? it will remove the fiber itself. the arcing probably will be a problem, however.
<whitequark> I'm not sure to what extent will the wires degrade
<whitequark> > During the Gulf War Iraq responded to the use of this type of munition by disconnecting electrical power grid circuit breakers.
<DocScrutinizer05> I think the more protective gear they have, the more trouble to power up a shorted line
<DocScrutinizer05> DI
<whitequark> probably
<whitequark> I also heard some of that gear is both very expensive and one-time use
<DocScrutinizer05> yep
<whitequark> yeah exactly... it seems that the arcing did damage the wires
* DocScrutinizer05 wonders of BGA can be glued instead reflowed
unclouded has joined #qi-hardware
<DocScrutinizer05> you for sure need perfect glue application and component positioning, since no self centering and small surface tention of glue
<DocScrutinizer05> but hey, no more reflow, no more heat. No more water steam explosions in balls
<lindi-> <pabs> interesting, the Broadcom Videocore reverse engineering folks have custom code running on the part of the RPi GPU responsible for booting
lekernel has quit [Quit: Leaving]
<whitequark> lindi-: yeah, except they don't really know anything about videocore and can neither activate the framebuffer (not even talking about 3D) nor boot the ARM core
* whitequark tries to get NFC working on his phone
<whitequark> either bad phone or bad tags :/
<whitequark> they are kinda write-only, and I think only a single attempt of several dozen succeeded
unclouded has quit [Remote host closed the connection]
panda|x201 has quit [Read error: Connection reset by peer]
<whitequark> hmmm interesting
<whitequark> it seems that first 8 bytes of even a clean tag are non-random garbage
<DocScrutinizer05> serial # ?
<whitequark> DocScrutinizer05: nope
<whitequark> serial is before that
<whitequark> the weird thing is: it's an NXP tag and NXP tag reader (does anyone else make them? all NFC stuff I could find at my place was by NXP)
<whitequark> sooo I clean the tag, and apart from system info it contains 01 03 A0 10 44 03 00 FE
<whitequark> and this is correctly recognized by the tag reader as an empty NDEF record
Caly__ is now known as Calyp
Calyp has quit [Changing host]
Calyp has joined #qi-hardware
<whitequark> but when I write the actual info to the tag, it contains 01 03 A0 10 44 44 0E and an actual NDEF record
<whitequark> which I can recognize manually
<whitequark> nothing in the prologue seems to be a valid record start
<whitequark> FE seems to be an epilogue (actual info also contains it at the end) but it is not a valid record according to the NDEF standard
<whitequark> maybe there's more framing going on
<whitequark> why do I have to do this at all! >_< it should be a consumer technology. easy to use yadda yadda
<whitequark> HWSON8: plastic thermal enhanced very very thin small outline package
wolfspraul has joined #qi-hardware
<whitequark> indeed, there's another TLV structure there
<whitequark> hmmm right
<whitequark> instead of "44 0E" there should've been "03 0E" for it to be a valid T/L for an NDEF record
<whitequark> I wonder why it writes 44 there...
jekhor has joined #qi-hardware
rz2k has joined #qi-hardware
FDCX has quit [Ping timeout: 264 seconds]
FDCX has joined #qi-hardware
jekhor has quit [Read error: Connection reset by peer]
baba has joined #qi-hardware
freemor has joined #qi-hardware
cod3r has quit [Ping timeout: 260 seconds]
jluis has quit [Ping timeout: 264 seconds]
FDCX has quit [Ping timeout: 264 seconds]
fdcx_ has joined #qi-hardware
pcercuei has joined #qi-hardware
guanucoluis has joined #qi-hardware
porchao has joined #qi-hardware
Ornotermes has quit [Ping timeout: 264 seconds]
porchaso0 has quit [Ping timeout: 256 seconds]
baba is now known as megha
kilae has joined #qi-hardware
wej has quit [Ping timeout: 248 seconds]
wej has joined #qi-hardware
Ornotermes has joined #qi-hardware
Ornotermes has quit [Ping timeout: 264 seconds]
Ornotermes has joined #qi-hardware
Calyp has quit [Quit: gone working on freeconomy =o)]
Ornotermes has quit [Read error: Connection reset by peer]
Ornotermes has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
Ornotermes has quit [Ping timeout: 256 seconds]
Ornotermes has joined #qi-hardware
LunaVorax has joined #qi-hardware
Ornotermes has quit [Read error: Connection reset by peer]
Ornotermes has joined #qi-hardware
rzk has joined #qi-hardware
emeb has joined #qi-hardware
Ornotermes has quit [Read error: Connection reset by peer]
rz2k has quit [Ping timeout: 264 seconds]
Ornotermes has joined #qi-hardware
megha has quit [Ping timeout: 240 seconds]
LunaVorax has quit [Ping timeout: 256 seconds]
kuribas has joined #qi-hardware
<kuribas> Can the nanonote linux kernel be used for other ingenic devices?
<kuribas> I bought a very cheap linux ereader (http://www.walmart.com/ip/iTomic-IEBR7C-7-eBook-Reader/19887947) and I would like to put linux on it.
<kuribas> The processor is a jz4755.
<pcercuei> not easily
<kuribas> There is little documentation on the chip, however I found a patched linux kernel from the manufacturer.
<larsc> the jz47xx kernel tree has support for other SoCs like the jz4755
<larsc> but unless you know what you are doing you probably wont get somewhere easily
<wpwrak> that sounds like a universal truth :)
<kyak> buy ereader, try to put linux there, get too much involved, never use that ereader to read books :)
<whitequark> oh yes
<kuribas> I didn't intend to read books with it :)
kilae has quit [Quit: ChatZilla 0.9.90 [Firefox 20.0.1/20130409194949]]
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
jekhor has joined #qi-hardware
jekhor has quit [Ping timeout: 256 seconds]
guanucoluis has quit [Ping timeout: 264 seconds]
jekhor has joined #qi-hardware
woakas has quit [Ping timeout: 272 seconds]
kuribas has quit [Remote host closed the connection]
Jurting_pc2 has joined #qi-hardware
jekhor has quit [Ping timeout: 256 seconds]
Jurting_pc2 has quit [Ping timeout: 255 seconds]
rz2k has joined #qi-hardware
rzk has quit [Ping timeout: 264 seconds]
guanucoluis has joined #qi-hardware
xdpirate has quit [Read error: Connection reset by peer]
guanucoluis has quit [Ping timeout: 256 seconds]