**** BEGIN LOGGING AT Tue Mar 27 02:59:56 2007 Mar 27 03:21:47 Anyone ever used BDI2000 for NSLU2? Mar 27 03:24:17 I think one of {dyoung,[g2]} have. Mar 27 03:24:45 heh, I *wish* I had the bdi xscale firmware Mar 27 03:25:07 but $1000 is too much for a hobbyist Mar 27 03:25:12 rwhitby: thanks... wish someone that said it was working in the wiki had posted a config file. Mar 27 03:25:23 jacques: yes I have one I borrowed from work. Mar 27 03:25:43 I have access to a bdi2000 device, but only the PPC firmware Mar 27 03:26:12 jacques: do you have to have a license on the device for programming all parts? Mar 27 03:26:51 I'm pretty sure we only paid for the ppc firmware - it's all we use it for at work Mar 27 03:27:04 is it not enough to get .cfg and .def files (from BDI FTP server)? Mar 27 03:27:34 the firmware in the bdi device varies by arch and sub-arch Mar 27 03:27:53 you can load new firmware into the bdi, but the license for each sub-arch is $1000 Mar 27 03:28:11 (and I've never seen the bdi firmware available for download) Mar 27 03:28:15 oh I didn't even consider that... we don't use IXP at work either (PPC too) Mar 27 03:28:33 :-( Mar 27 03:28:33 so it might not have the license, and thus won't recognize IXP425 Mar 27 03:29:07 if your bdi isn't running the xscale/xp firmware, it won't Mar 27 03:29:08 RobNC: just get a digilent parallel port cable and use wince jtag tools :-) Mar 27 03:29:13 xscale/ixp Mar 27 03:29:16 (425 was closest to 420 I could find - same thing) Mar 27 03:29:26 yeah same thing Mar 27 03:29:46 yeah RobNC I have a wiggler compatible parallel port cable and it works on the nslu2 Mar 27 03:29:57 just extremely slow compared to bdi Mar 27 03:30:07 40 minutes to flash 128kB IIRC Mar 27 03:30:15 I've done that once too - I actually have the JTAG cable permanently connected, but never use it :-) Mar 27 03:30:28 rwhitby: yeah looking that way. laptop doesn't have lpt port that I trust. Set in BIOS to EPP, and bidir, but winxp still thinks it's ECP. For some reason, I couldn't compile jtag tools from knoppix liveCD Mar 27 03:30:56 jacques: not too important since the bootloader is so small, luckily :-) Mar 27 03:31:07 40 minutes still gets old fast Mar 27 03:31:38 rwhitby: I made one too, but I couldn't get the device to be found. Unless the wiki instructions are errored, or the PCs I was on had other issues. Mar 27 03:31:55 true... can't you set the speed in the openjtag tools? Mar 27 03:32:19 jacques: hopefully you only ever do it once. then you learn your lesson and be more careful with the bootloader :-) Mar 27 03:33:00 rwhitby: I hear ya. My wife interrupted my train of thought and I hit return instead of erasing the line to copy apex to ram and run it from there. Mar 27 03:33:05 rwhitby, well when I was porting u-boot I must have done it 20 times Mar 27 03:33:29 and it's still not working right (no network) :-( Mar 27 03:33:32 jacques: yeah, bootloader development is a different kettle of fish. Mar 27 03:34:09 weird thing about parallel port JTAG. It appears that the instructions for openwince JTAG port is different than the NSLU2 wiki. Not sure if all pins are needed for jtag tools? Mar 27 03:35:12 Have you all tried USB-to-parallel-port adapters with the openwince JTAG tools? Mar 27 03:35:35 not I Mar 27 03:35:41 RobNC: I used this page: http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlashUsingJTAG Mar 27 03:35:50 and a Digilent parallel port cable. Mar 27 03:36:31 rwhitby: I hear ya. The Digilent parallel cable has more pins and a transistor than the wiki site you mentioned. Not sure if it matters. Mar 27 03:36:49 I too used a digilent Mar 27 03:37:06 Here is what I'm talking about: http://wiki.openwrt.org/OpenWrtDocs/Customizing/Hardware/JTAG_Cable Mar 27 03:38:26 see how trst is used, as well as srst_n, whereas the NSLU2 wiki makes no mention of this, and also the pin-8 to pin-15 interconnect (LPT) "detect" wire is not there. Mar 27 03:39:23 yeah, none of that is needed for jtag flashing Mar 27 03:39:27 yep Mar 27 03:39:52 superfluous Mar 27 03:41:42 ok, gotcha... I also noted that TDI and TCK have pullups (6.8k and 10k, respectively) Mar 27 03:43:38 I'll try that again. I got a little further with cygwin. Gotta use some extra driver to let you program directly to port. When I have it working with cygwin, I'll wiki it of course. Mar 27 03:49:24 you guys know if it's so important to only use the version of headers specified in the wiki? I.e., only INCLUDE-0.3.2. Mar 27 04:09:58 thanks guys for your help... will try parallel-port version... Mar 27 17:13:23 NAiL: any luck with the rev2 openpbx package? OE ticket 2044 Mar 27 17:19:51 03oleo 07uclibc-unstable * r5833 10optware/sources/buildroot/buildroot.config: unstable buildroot: enable short/long jump exceptions Mar 27 17:26:57 hillct: sorry, been working on other stuff. If I don't mess up stuff, I'll be checking it in today ;) Mar 27 17:27:32 thanks Mar 27 17:53:16 03bzhou * r5834 10optware/trunk/make/swi-prolog.mk: swi-prolog: 5.6.31 -> 5.6.32 Mar 27 17:57:33 thanks Mar 27 18:43:18 NAiL: is the new openpbx not working in the autobuild system? Mar 27 18:44:22 haven't committed it to stable yet Mar 27 18:44:29 you'll see it in here when I do Mar 27 18:44:48 ah. tanks Mar 27 18:44:50 thanks Mar 27 21:32:26 03nail 07slugos-3.10-beta * r418 10slugos/openembedded/packages/openpbx/openpbx.org_1.2_rc3.bb: openpbx.org: Update to rev2, thanks hillct Mar 28 00:21:28 i'm really sweating here... i'm attempting to install debian on my nslu2, and I think it's stuck.. it's in the 'partitions formatting' screen and stuck at 33% Mar 28 00:21:45 I think it went through to 33% really fast, like probably in a min or so Mar 28 00:22:27 my external hard-drive isn't making any sounds.. and the led is a solid red, which is strange as I have never seen it light up in red Mar 28 00:23:55 adorn: you should go first on #nslu2-general Mar 28 00:24:23 thanks Mar 28 00:31:41 adorn: actually, since it's debian, #nslu2-linux nor #nslu2-general are the right channels. #debian-arm or #debian-boot on irc.oftc.net are the designated support channels for Debian/NSLU2 (since it's a fully supported Debian target) Mar 28 00:32:08 ... neither #nslu2-linux nor ... Mar 28 00:45:37 ohh ok Mar 28 00:53:51 rwhitby I got the JTAG programmer to work (parallel). Replaced redboot, back up and running, about ready to D-I RC2 again. Just wish someone would update the memory locations, etc. for D-I installs using Redboot ->APEX->Debian kernel Mar 28 00:54:23 RobNC: which memory locations? Mar 28 00:54:52 the normal debian install is redboot->apex->kernel Mar 28 00:55:19 there is a wiki that shows mem locations but it's not valid for redboot->apex->kernel b/c no apex :-) Mar 28 00:55:47 says at bottom "needs updating for Debian install". I'd like to replace apex but don't want to screw it up! :-) Mar 28 00:56:11 RobNC: so you'll be updating the wiki then? Mar 28 00:56:39 yes, I already have updated the wiki for JTAG (lots of problems) recovery. got it to work with WinXP and cygwin (woohoo) Mar 28 00:57:09 cool. for apex (second-stage) replacement, why not just do it from userland writing directly to the correct /dev/mtdblock partition? Mar 28 00:57:21 I am an avid believer of documentation. I do it all the time at work. I love it b/c I just refer people to my instructions instead of spoon-feeding every time Mar 28 00:57:22 (just like flash-kernel does for the kernel) Mar 28 00:58:12 yeah I was thinking of that, but it assumes debian already installed (I guess?), using some program called apex-loader or something like that. Mar 28 00:58:24 I could never change the env vars of apex. Mar 28 00:59:03 so just do a normal D-I RC2 install first, and then replace apex later? Mar 28 00:59:40 yeah but last time it took like 6 hrs and I am guessing it's b/c low mem. Would like to use the 256MB during install *BIG GRIN* Mar 28 01:00:38 never heard back from APEX guy, dunno why Mar 28 01:03:11 BTW, this page http://www.nslu2-linux.org/wiki/Main/UpSlug2 says: (The above partition information is not accurate for Debian installations that use APEX - would someone like to update it?) Mar 28 01:08:19 it's ok - gonna go ahead and install anyway. Mar 28 01:12:38 RobNC: yeah, Marc goes "dark" for extended periods sometimes. Mar 28 01:13:06 ok I am patient... only wanna help others and also update the wiki so maybe more fatslug users will be encouraged. Mar 28 01:13:15 RobNC: the other way to do this is use slugimage to unpack the D-I image, then pack back in the new Apex Mar 28 01:13:29 then you can use upslug2 unchanged. Mar 28 01:14:00 ah that's an idea... provided that the apex size in the 8MB image is the same (or at least same place in memory) Mar 28 01:16:05 Since I have JTAG working, it is definitely worth a shot (doing TFTP over Redboot is best for me). I don't have a slugimage binary, but should be able to replace the APEX latest into the D-I image. Mar 28 01:16:59 should be same size and same place in memory Mar 28 01:17:18 slugimage is a perl script you can run on any host Mar 28 01:17:30 ah ok that's cygwin friendly then. Mar 28 01:17:32 (it's in Debian) Mar 28 01:18:04 The command I previously mentioned was http://wiki.buici.com/wiki/NSLU2_Memory_Expansion_--_Fat_Slug - mentioned the command "apex-env" which is something one compiles. Mar 28 01:18:05 if you're using a windows machine, then SerComm upgrade tool would be easier than redboot and tftp Mar 28 01:18:30 the apex env stuff is so new that no-one knows anything about it. Mar 28 01:18:34 ah I did that before but it installed something on the PC. I'm not afraid of TFTP - I use it all day long at work. :-) Mar 28 01:19:13 you should get the new apex into an 8MB image using slugimage, and then boot into apex and change the environment there, Mar 28 01:19:34 just gotta find a memory map for D-I (i.e., where is APEX) - but slugimage should do that for me eh? Mar 28 01:22:41 If I already have D-I in flash, but it has 1.4.15 APEX, shouldn't I just tftp the new APEX into RAM, then replace APEX in flash at the location it is run in flash, or is it more complex? Mar 28 01:24:12 dunno Mar 28 01:24:21 yes, slugimage will show you the mem map for D-I Mar 28 01:25:52 ah I see... just don't know what pack (-p) and unpack (-u) do... Mar 28 01:27:24 lemme try first Mar 28 01:30:06 do unpack and debug to see the FIS table Mar 28 01:31:56 can't get slugimage via CVS - seems like URL is either bad or website problems Mar 28 01:34:29 RobNC: http://svn.nslu2-linux.org/svnroot/slugimage/trunk/ Mar 28 01:35:04 thanks I'll change wiki Mar 28 01:36:37 RobNC: bbiab Mar 28 01:37:00 ok, btw couldn't change wiki b/c passwd req'd Mar 28 01:43:32 nice program slugimage! Mar 28 01:58:45 when u get back - Q for you - looking at apex config file, it seems that default memory for NSLU2 is set there. If I recompile apex, wonder if I could get the NSLU2 to recognize it. Some ppl say that SDRAM_CFG regs only read at boottime by redboot Mar 28 02:41:51 RobNC: back Mar 28 02:42:02 RobNC: which wiki page is requiring a password? Mar 28 02:42:22 RobNC: latest apex is supposed to be able to change sdram config as a second stage bootloaderf Mar 28 02:50:59 rwhitby: sorry I was away too. wiki page req passwd is http://www.nslu2-linux.org/wiki/Main/SlugImage Mar 28 02:51:35 rwhitby: agreed about 2nd stage boot loader for apex, but to do that requires changing env parameters (which are locked) Mar 28 02:52:34 cool - thanks - able to edit (and fix bad URL) now. Mar 28 02:53:14 if env parameters are locked, then something is wrong Mar 28 02:53:21 (they shouldn't be locked) Mar 28 02:53:48 RobNC: if you want to write some stuff in that wiki page about how to use slugimage from a user's point of view, that would be great. Mar 28 02:55:17 ok, when I get it working, I will. Now, redboot goes to apex, then apex continually reboots. I did this: Mar 28 02:55:48 slugimage -u -i di-nslu2.bin Mar 28 02:56:27 but no output for FIS directory (read 1 block), and no ouput for EthAddr (0x06 bytes read) Mar 28 02:57:08 files in dir are now: RedBoot, SysConf, apex.bin, vmlinuz, ramdisk.gz, and Trailer. Mar 28 02:57:20 Next, I did: Mar 28 02:58:34 slugimage -p -o di-nslu2-newapex.bin -b RedBoot -s SysConf -L apex-1.4.17.bin -k vmlinuz -r ramdisk.gz -t Trailer -e (my MAC address here) Mar 28 02:58:37 both of those no outputs are correct Mar 28 02:58:59 you don't need the mac address, since you're not overwriting redboot Mar 28 02:59:29 the rest looks fine Mar 28 02:59:47 so apex 1.4.17 is rebooting? Mar 28 02:59:52 and apex-1.4.17.bin is from the binary image from ftp.buici.com/pub/apex/apex-1.4.17/apex-1.4.17-nslu2.zip **** ENDING LOGGING AT Wed Mar 28 02:59:56 2007