<GraphicHealer>
this is my post about the device Im trying to port
<Tusker>
it probably expects some dodgy CentOS from 2001 as a base OS...
<GraphicHealer>
actually fedora 12
<GraphicHealer>
I cant get 12 to install on Virtualbox though
<russell-->
what is the board?
<GraphicHealer>
so I went with 34
<GraphicHealer>
Look at the forum post above
<GraphicHealer>
It's all documented there
<GraphicHealer>
even disassembly
<GraphicHealer>
SHould I try fedora 12 again?
<GraphicHealer>
The problem I had was yum couldn't find a server
<GraphicHealer>
so I couldn't install dependency's
<Tusker>
most of the time those build roots expect very specific OS libraries
<GraphicHealer>
ah.
<russell-->
i'd bypass the SDK
<GraphicHealer>
How do I get around the yum repo not found error?
<russell-->
is there a u-boot on the board already?
<GraphicHealer>
Yes, but the boot interrupt is disabled
<GraphicHealer>
so you cant get to any prompt
<Tusker>
generally I wouldn't bother replacing uboot... unless you have experience with JTAG and booting from JTAG, it will likely end in a world of pain :)
<GraphicHealer>
How do I get OpenWRT then?
<russell-->
are you sure the serial isn't just disconnected, it's common to not populate a shunt to disable rx
<russell-->
and a) it worked; b) it was small enough to fit in the previous space available
<Tusker>
russell--: I think it is a bit of a random guess whether the vendor has modified enough of the uboot code to work differently to mainline...
<russell-->
the vendor u-boot is guaranteed to have forked from mainline u-boot in 2005 and have been untouched since 2010
Rentong has joined #openwrt-devel
<GraphicHealer>
there is a resistor from rx(maybe tx?) to gnd, but all other connections seem to go directly to the SOC
<GraphicHealer>
for the UART
<russell-->
my point is, with some strategic configuring, and some light porting, we built modern mainline u-boot for a mt7620 or something and it worked
<russell-->
but you need a reliable way of recovering if you don't get it right the first time
<GraphicHealer>
yeah
<russell-->
hence, external spi programmer
<GraphicHealer>
Its got a MT7628AN in it
<russell-->
it's basically the same soc
<GraphicHealer>
I think the pins on J10 (pics on forum post) are SPI
<russell-->
with som minor differences
<GraphicHealer>
Would that port you made work on mine???
<russell-->
U4 is the spi flash
<GraphicHealer>
huh?
<GraphicHealer>
I thought the SPI flasher would flash to the chip itself. Is uboot stored on a separate device?
<russell-->
the photo from the forum post
<Tusker>
also, it is possible that there is a uboot recovery mode... and you can load a properly constructed firmware image via http...
<Tusker>
does the boot process change if you hold the reset while booting ?
<GraphicHealer>
here is. I've seen references to it in the source.
<GraphicHealer>
*there is
<GraphicHealer>
Idk
<GraphicHealer>
it didnt seem to boot at all if a button was held down
<russell-->
there's glare, you can't make out the part number from the photo, but the red paint dot is a tell
<russell-->
and the soic-8 footprint
<GraphicHealer>
would I need to hook up a UART to USB and then plug it in while holding reset or WPS?
<Tusker>
that's an option, if there is a HTTP recovery mode, or TFTP recovery mode, that'll be easier
<Tusker>
especially if you want others to install it :)
<GraphicHealer>
true
<Tusker>
so, tcpdump while doing that would be good to see if any TFTP pings on port 69
<GraphicHealer>
If the firmware fails to boot wont UBOOT kick into recovery mode?
<russell-->
don't try flashing anything until you have a way to go to what you started with
<GraphicHealer>
then i can just flash the factory firmware back?
<GraphicHealer>
ah.
<russell-->
you tell me?
<GraphicHealer>
Ill try the pi
<Tusker>
if uboot has a recovery mode...
<GraphicHealer>
its referenced in the source
<GraphicHealer>
for this specific device
<russell-->
the lack of serial means you don't have a way of recovering from u-boot unless u-boot does something automatically
<GraphicHealer>
doesn't mean its enabled
<GraphicHealer>
what about that J2?
<russell-->
and since you can't see what that is, you'd be doing it blindly with no clue what is actually happening and then ending up in an unknown state
<russell-->
try it?
<GraphicHealer>
try what? the J2?
<grid>
you may be able to do enough to get an initramfs booted
<grid>
but it would be a frustrating exercise
<grid>
nervermind
* grid
was thinking tx only uart :(
<russell-->
J2 doesn't look like serial to me
fda- has joined #openwrt-devel
<GraphicHealer>
but it could trigger a dev mode of sorts
<russell-->
what is the 2x2 female header?
<russell-->
on the top side of the board?
<russell-->
maybe connect to leds or something?
fda has quit [Ping timeout: 480 seconds]
<GraphicHealer>
no thats power
<GraphicHealer>
from the power board
<GraphicHealer>
nothing.
<GraphicHealer>
Shorting J2 does nothing.
<russell-->
ah yeah, was just coming to the conclusion it was power
<russell-->
the giant + was the first clue, then the lack of a barrel connector on the board
GraphicHeal has joined #openwrt-devel
fda- has quit [Read error: Connection reset by peer]
<GraphicHeal>
wierd
<GraphicHeal>
I am somehow still "connected
<GraphicHeal>
it won't let me use my real name
<Tusker>
your old irc session is hanging around
<GraphicHeal>
and shorting j2 seems to disable the web interface
<GraphicHeal>
oddly enough
<grid>
GraphicHeal: did you have uart output? if the boot interrupt is disabled you can glitch the flash and cause a checksum/validation error of the image
<grid>
e.g. the wink hub would drop to a u-boot prompt
<grid>
all that's necessary is to short a couple address or data pins together with e.g. a multimeter probe at the right point in the boot process
<GraphicHeal>
uart doesnt change. I just cant access the website anymore
<GraphicHealer>
I thought I needed spi, not single wire serial.
<Tusker>
good point, sorry...
<GraphicHealer>
*correction, not SWS, JTAG
<GraphicHealer>
WOuld the board i have do JTAG?
<Tusker>
hmm... i wonder if there is a flashrom compatible firmware for st link v2
<GraphicHealer>
hmm
<grid>
there's serprog firmwares
<grid>
can use an arduino too i think but it'd need to be 3.3v
<GraphicHealer>
I have a arduino uno
<GraphicHealer>
would that work?
<Tusker>
much better
<grid>
needs to be powered at 3.3v
<GraphicHealer>
I think it has 3.3v
<GraphicHealer>
idk
<grid>
they're 5v by default
<grid>
can use external 3.3v power probably
<grid>
eh nvm...they can't do 3.3v with a 16mhz crystal
<grid>
"If you run an ATMega328 at 16MHz powered by 3.3 Volts, this is out of specification and you are effectively overclocking it. However, it is likely to work" shrug
<grid>
just put it in the freezer before you use it :P
<grid>
the firmware that gives flashrom capability to bluepill
<GraphicHealer>
Ah
<Tusker>
that is a firmware to load on to the bluepill so that flashrom can talk through it
<GraphicHealer>
how do I load it? sorry. Kinda new to STM32. Never really used the darn thing.
<grid>
uhm, from linux. probably easiest booting into a live usb or something
<grid>
doing usb passthrough to a VM would be finicky at best i think
<russell-->
GraphicHealer: are you running windows or linux, not sure we established that
<GraphicHealer>
windows
<GraphicHealer>
sorry
<russell-->
ick ;-)
Rentong has joined #openwrt-devel
<GraphicHealer>
ok. Stlink and stm32 are wired up and plugged in.
<grid>
to flash it per the instructions you'd need to hook up the ftdi to the blue pill. there's native usb flashing on the blue pill, i don't remember if that's the ROM or it needs to have a special bootloader already flashed
<grid>
make sure the ftdi is set for 3.3v though, if it does both 5v and 3.3
<GraphicHealer>
so wait, do I just run the make command with the FTDI connected?
<GraphicHealer>
*stlink
fda has quit [Ping timeout: 480 seconds]
<grid>
1.) you'd need to be in linux 2.) see which usb port the ftdi enumerates as, it wouldn't be /dev/ttyACM0 as specified in the Makefile. probably would be at /dev/ttyUSB0
<grid>
it's a lot faster than bus pirate and has all sorts of configs for swd, jtag, uart, sgpi, etc.
<Tusker>
yeah, looks nice
<grid>
i have other ftdi, including an ft4232h, but that for example had a buffer / level shifter which prevented using it for SWD as-is. i had to lift a pin
<GraphicHealer>
ah
<GraphicHealer>
n idea what that means
<GraphicHealer>
*no
<GraphicHealer>
Nice! I got pins now!
<grid>
swd is like jtag for arm chips but only uses a few wires
<grid>
stlink can do it
<GraphicHealer>
yeah thats I think how STM32 does it.
<GraphicHealer>
Ive got pi headers on the UART pis now
<GraphicHealer>
*pin
<GraphicHealer>
*pins
<russell-->
i have a tigard too, fwiw (a few of them actually)
<GraphicHealer>
ok now the fun part
<GraphicHealer>
pressing the reset and typing
<GraphicHealer>
YAY
<Monkeh>
I can confirm the same code is in the RE6350 source for the bootloader
<GraphicHealer>
wait, where?
<GraphicHealer>
ive looked through it
<GraphicHealer>
I dont remeber seeing anything like that
<Monkeh>
Because they didn't include obvious things like the string '1234567890' or 'password' or the like.
<GraphicHealer>
ohhh
<Monkeh>
But 'backdoor', well.. nobody accused them of being all that clever
<Tusker>
hmmm... if the factory firmware of a device has ubi, and I want to flash a new ubi rootfs over top of it, is there a flag in sysupgrade to tell it to wipe it first before mkubivol ?
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<GraphicHealer>
IM IN
<GraphicHealer>
I have a UBOOT prompt!!!!!
<Monkeh>
So you should be able to load code via tftp, now you just need to have something to load.
<GraphicHealer>
exactly!
<grid>
nice
<GraphicHealer>
Isn't that router a MT7628 device?
<GraphicHealer>
would the UBOOT from that tutorial work?
<Monkeh>
You don't need to touch the bootloader
<GraphicHealer>
Ah
<GraphicHealer>
so use inframFS?
<Monkeh>
Everything you need should more or less be in the source, search for CONFIG_UMEDIA_RE6350
<Monkeh>
Should be pretty trivial to get a basic DTS working, dump and examine the flash, and flesh out the rest
<GraphicHealer>
I can get to UBOOT even if the firmware doesnt boot, so as long as I make a backup (can I do a tftp pull?) i should be good
<GraphicHealer>
it has a `start www` command
<GraphicHealer>
awww markdown dont work
<GraphicHealer>
for firmware recovery
<russell-->
wait, what happened? how did you get the prompt?
<fda>
also the path names of kernel patches changed, no more versions in it
<fda>
you know "dts" files? are the "delete-node" okay in the patch? in vendors file is something with phy4
* russell--
has no idea
<fda>
:(
<russell-->
try button-holing the person who made the commit
<fda>
how? or where?
<fda>
im now to openwrt, and where to create iusse is not easy to determine
<fda>
i opened yesterday 2 issues on main repo, but as there are more than 1000 opened i dont expect an answer within days
<fda>
the 2nd issues was an duplicate of an 18month problem ^^
<fda>
(old)
dedeckeh has joined #openwrt-devel
<russell-->
the name of the author is in the commit
<russell-->
try emailing them?
<russell-->
fda: what makes you think that commit is the problem?
<russell-->
do you have a boot log?
<fda>
no
<fda>
the device needs torx T6 and my smallest is T8
<fda>
uboot loads from tftp and file and something is written, the original images is gone
<fda>
and it is not pingable or something
<fda>
same procedure works with openwrt19
<fda>
so something must have changed
<fda>
and there are to so much commits related to avm 1200 4040 7530 3000
<fda>
and the other seem still run
<russell-->
usually you can remove torx with small flatheads
<fda>
could also be something completely different
<fda>
the screw is 1cm deep in the case
<russell-->
unless someone has the hardware or more information, it's going to be hard to fix
<fda>
i know :(
<russell-->
so i guess my advice is "try harder" ;-)
<fda>
im glad the older version runs. so maybe someone sees in the .dts someting, or i have to test when it does not work anymore
<russell-->
what is wrong with the old version?
<fda>
old
<russell-->
it will be abandoned at some point
<fda>
i can not build it by myself
<fda>
openwrt has different repos, and paxkages dont match
<fda>
i tried it yet!
<fda>
and i have numerous fixes to master i ant apply with prebuild image
<russell-->
if you have longterm plans to keep the device, i'd recommend investing work in helping people keep it supported
<zatwai>
guys, is team aware of autonegotiation speed bug in 21.02 for at least ramips mt7621? it cannot negotiate on 100baseT cables to 1000baseT ports.
<russell-->
seem like these are rules copied from another large successful open source project
<fda>
thats the wrong direction
<Tusker>
it's really easy to configure your text editor to auto-wrap for you if it's a problem
<fda>
linux is not sucessfully because of some rules
<fda>
i use shell to commit
<fda>
so i have to count chars
<fda>
ot put glue on the bottom left edge
<russell-->
if only we could invent some kind of machine to do simple math for us, but here were are starting fires by striking stones together ;-)
<russell-->
i.e. if your text editor can't keep track of line length you should maybe shop around for another text editor
<fda>
maybe this i known if you are english native
<fda>
i use a simple terminal
<fda>
thers no editor
<russell-->
find a screwdriver, put a serial console on your device and get a boot log from the non-working firmware
<fda>
using a mouse is slow
<russell-->
that's the way forward
<Tusker>
you can open vi or nano or whatever you want upon git commit
<Tusker>
or use a fixed width font and a terminal 75 characters wide
<russell-->
ed is a good editor
<fda>
why is en editor needed? to commit is a simple command enough
<russell-->
you need to make a change to commit, yes?
<fda>
i thnk not
<Tusker>
you want to stop counting characters... then use a tool to allow you to do it
<Tusker>
rules are to produce consistency and allow interoperation with people who like to code on their embedded hardware
<Tusker>
with a OLED display
<fda>
i cant imagine someone would do this
<Tusker>
if you don't like the rules, then find a friend that can commit on your behalf and mentions always "committed code on behalf of fda, who shall not be named"
<fda>
have such device not lan for ssh?
<fda>
maybe i just put them in the forum
<Tusker>
*shrug* regardless, these rules are not bad, they help for consistency and community mindedness
<fda>
its okay, openwrt works great
<Tusker>
they are not a barrier to entry for contributing :)
<Tusker>
sure, put the patches on the forum
<fda>
for sure
<fda>
its a barrier
<Tusker>
it's not a barrier for contributing, it's a barrier for bad code and bad practises which messes up everything and isn't contributing :)
<Tusker>
it may be a "felt" barrier, but it's not an actual barrier
<fda>
using not a real name causes bad cod?
<fda>
but anyway... initiall i was asking about 1200 and dts
<Tusker>
:)
<fda>
another thing. is there really no autofs4/automout daemon in openwrt? i could only find the kernel module
<fda>
and if the daemon is missing, why was the kernel module added? how was it used?
<Tusker>
good questions that I don't know the answer to
<Tusker>
in terms of your fritzbox, looks like guys are working on getting the 7490 going so probably your 7590 would benefit
<fda>
i wrote about 7490 on github
<fda>
7590 is completely diffrent
<fda>
and i sell it
<Tusker>
ah ok
<fda>
but i dont except the 7490 will works well. it has 2 cpu architecure, 1 only for wlan
<Tusker>
OK, weird... not sure what is going on with the ethernet on this device (ar8033 ipq806x-gmac-dwmac) - hangs on scp quite often... but ping etc looks normal
<Tusker>
OK, looks like it was the switch port on the wrt1900 that was causing it, I think the port is fine... :)
glitzydeletion__ has joined #openwrt-devel
por has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #openwrt-devel
por has quit [Remote host closed the connection]
floof58_ has joined #openwrt-devel
por has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
por has quit []
glitzydeletion__ has quit [Quit: Leaving]
por___ has joined #openwrt-devel
aleksander has joined #openwrt-devel
por has joined #openwrt-devel
Tapper has quit [Ping timeout: 482 seconds]
por___ has left #openwrt-devel [#openwrt-devel]
danitool has joined #openwrt-devel
Tapper has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
bluew has quit [Quit: Leaving]
floof58_ has quit [Ping timeout: 480 seconds]
floof58_ has joined #openwrt-devel
<rsalvaterra>
rmilecki: Did you get around to testing the mt76 patch? :)
<rmilecki>
rsalvaterra: yes, I don't think it fixes Xiaomi 4C
<rmilecki>
rsalvaterra: i'm goig to test on R6220 today
<rsalvaterra>
Oh, that's unfortunate… :(
nitroshift has joined #openwrt-devel
Tapper has joined #openwrt-devel
<rmilecki>
rsalvaterra: that seemed very promising though
<rmilecki>
rsalvaterra: i'll reply to that developer for sure
por has left #openwrt-devel [#openwrt-devel]
Borromini has joined #openwrt-devel
decke has quit [Quit: Leaving.]
floof58_ has quit [Ping timeout: 480 seconds]
floof58_ has joined #openwrt-devel
silver has quit []
Tusker has quit [Quit: Time wasted on IRC: 11 hours 50 minutes 11 seconds]
SamantazFox has quit [Ping timeout: 480 seconds]
Borromini has quit [Ping timeout: 480 seconds]
<GraphicHealer>
Morning!
mangix has quit [Remote host closed the connection]
mangix_ has joined #openwrt-devel
dorf has quit [Remote host closed the connection]
minimal has joined #openwrt-devel
dorf has joined #openwrt-devel
floof58_ has quit [Ping timeout: 480 seconds]
floof58_ has joined #openwrt-devel
Borromini has joined #openwrt-devel
valku has joined #openwrt-devel
Rentong has joined #openwrt-devel
<GraphicHealer>
Oh dear. Kermit mode is slow.
<GraphicHealer>
Had to flash the FW, I think I messed it up somehow.
<GraphicHealer>
Im at 1mb out of 6.5mb, and its been like 5-10 minutes already.
<Monkeh>
Why are you flashing it like that?
Borromini has quit [Ping timeout: 480 seconds]
dorf has quit [Remote host closed the connection]
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
<PaulFertser>
GraphicHealer: flashing via UART, what's the baud rate?
silver has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
<nbd>
rmilecki: netifd regression is fixed now
<rmilecki>
nbd: thanks!!
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
<rmilecki>
i've a little deamon registering ubus object and using uclient for downloading files
<rmilecki>
my problem is: when my deamon tries connecting to offline server (uclient_connect()) all calls to my exported buus methods hang
<rmilecki>
uloop is single thread and that part of uclient seems to be blocking it
<rmilecki>
it there any solution for that?
<nbd>
i guess the code needs to be changed to make the connect() call async
<nbd>
(and the ns lookup as well)
<rmilecki>
nbd: uclient's code, right?
<nbd>
right now it just uses usock
<nbd>
yes
<rmilecki>
thanks
Rentong has quit [Remote host closed the connection]
aleksander has quit [Quit: Leaving]
Rentong has joined #openwrt-devel
<GraphicHealer>
PaulFertser: 57600
<GraphicHealer>
Monkeh: the device has no ethernet port.
<PaulFertser>
GraphicHealer: you can can assume about 5760 bytes/second speed at most.
<GraphicHealer>
Yeah
<GraphicHealer>
Its done now. Webpage still wont open.
<PaulFertser>
GraphicHealer: but if you have serial you should be able to log in via serial. Does that work?
<GraphicHealer>
I think it broke.
<PaulFertser>
GraphicHealer: better use some pastebin to show full serial output after cold boot.
<GraphicHealer>
Hang on! What if J10 is Ethernet, not SPI?
<GraphicHealer>
and how would I figure out what pins go where?
<GraphicHealer>
would I just grab a cable, cut an end off and wire stuff on untill I get a signal?
<GraphicHealer>
if it was ethernet, it would explain the direct connection to the SoC instead of the SPI flash chip.
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
<GraphicHealer>
This is so weird. I did nothing to the device, but it wont start the web server anymore.
<PaulFertser>
GraphicHealer: wired ethernet always have a transformer
<GraphicHealer>
Ahhh. Must be SPI then.
Rentong has quit [Remote host closed the connection]
<PaulFertser>
GraphicHealer: so if you can't get the prompt how were you using Kermit?
<GraphicHealer>
No. I can get to the prompt.
<GraphicHealer>
When I do it normally I can't get to the web configuration interface.
Rentong has joined #openwrt-devel
<GraphicHealer>
The Linksys web configuration interface you're supposed to use if you use these as normal. It won't start at all anymore. Port 80 returns nothing.
<GraphicHealer>
The device seems fine, the web interface just seems to have disappeared.
<GraphicHealer>
I dont get it.
Rentong has quit [Remote host closed the connection]
SamantazFox has joined #openwrt-devel
Rentong has joined #openwrt-devel
SamantazFox is now known as Guest775
SamantazFox has joined #openwrt-devel
<GraphicHealer>
anyone kow how I can get the webpage to show back up?
<GraphicHealer>
or maybe how to flash OpenWRT?
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Guest775 has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
SamantazFox is now known as Guest778
SamantazFox has joined #openwrt-devel
Guest778 has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
SamantazFox is now known as Guest781
SamantazFox has joined #openwrt-devel
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
<GraphicHealer>
Monkeh: well then how do I hook spi to the chip?
<GraphicHealer>
Or do I even need spi?
<GraphicHealer>
Could I just create the DTS file and build openwrt?
SamantazFox is now known as Guest797
SamantazFox has joined #openwrt-devel
Guest797 has quit [Ping timeout: 480 seconds]
<russell-->
GraphicHealer: either a SOIC-8 chip clip or micrograbbers
<GraphicHealer>
oh boy
SamantazFox is now known as Guest801
SamantazFox has joined #openwrt-devel
<russell-->
GraphicHealer: i prefer the micrograbbers, personally
Guest801 has quit [Ping timeout: 480 seconds]
<grid>
agilent/hp branded clips are the best i've tried
fda has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
SamantazFox is now known as Guest808
SamantazFox has joined #openwrt-devel
rsalvaterra_ has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
Borromini has quit [Quit: leaving]
Guest808 has quit [Ping timeout: 480 seconds]
rsalvaterra has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
silver has quit [Quit: One for all, all for One (2 Corinthians 5)]
Tapper has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
Tapper has joined #openwrt-devel
dedeckeh has quit [Remote host closed the connection]
silver has joined #openwrt-devel
rmilecki has quit [Ping timeout: 480 seconds]
rmilecki has joined #openwrt-devel
rmilecki has quit [Ping timeout: 480 seconds]
minimal has quit []
rsalvaterra_ has quit []
rsalvaterra has joined #openwrt-devel
SamantazFox is now known as Guest821
SamantazFox has joined #openwrt-devel
Guest821 has quit [Ping timeout: 480 seconds]
Tapper has quit [Ping timeout: 481 seconds]
Tapper has joined #openwrt-devel
SamantazFox is now known as Guest824
SamantazFox has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
Guest824 has quit [Ping timeout: 480 seconds]
SamantazFox is now known as Guest827
SamantazFox has joined #openwrt-devel
Guest827 has quit [Ping timeout: 480 seconds]
<GraphicHealer>
One problem. The SPI chip is under the heat spreader on the underside of the board.
Tusker has joined #openwrt-devel
<GraphicHealer>
To power the board, I have to plug it into the power biard, which involves sticking it back into the case. Clips and stuff won't fit into the case.
<GraphicHealer>
*board
<GraphicHealer>
Idk how to get around this. Maybe solder pins?
<Tusker>
GraphicHealer: can't you take the power board out and attach outside of the case ?
<GraphicHealer>
How?
<GraphicHealer>
Its not a flexible cable. Its a header to header
<Tusker>
but aren't the UART pins vias and can be accessed by both sides of the main board ?
<GraphicHealer>
Yes, bt the SPI chip (which is what i need to connect to next) is on the bottom
<GraphicHealer>
Im thinking the pins on that SPI device are big enough I could just solder wires to the bus and put headers on them.
<GraphicHealer>
I guess.
<Tusker>
or create a header to header extension with whatever header type it is...