| 02:55.30 | *** join/#openjtag StrontiumDog_ (n=Strontiu@24.13.111.218.klj01-home.tm.net.my) |
| 03:20.29 | *** join/#openjtag rje`mac (n=rje`mac@c-67-185-128-239.hsd1.wa.comcast.net) |
| 06:35.47 | Zoiah | zwelch: I have no clue, I'm just playing around. :) |
| 06:36.33 | Zoiah | zwelch: there's also a MPC8245, but even though it detects it I cannot find any flash part with 'detectflash' on any of the popular rom bases. It always gives '00' or 'ff', so there's probably something wrong/different. |
| 06:37.24 | zwelch | actually, i wonder if that could be a symptom of a flash protection feature |
| 06:37.52 | zwelch | if it is like some other chips, you would be able to read it once you erased it... but you probably do not want to do that, eh? :) |
| 06:37.58 | zwelch | kinda defeats the purpose |
| 06:38.11 | Zoiah | zwelch: do you mean the PLD or the Flash ROM attached to the MPC8245? |
| 06:38.20 | zwelch | both, actually :) |
| 06:38.37 | Zoiah | With the Flash ROM, I do imagine at least the identification to work. |
| 06:38.46 | zwelch | if the network switch is from cisco or a similar brand, i would virtually guarantee this is the case |
| 06:38.57 | zwelch | they would not let anyone sniff their bits |
| 06:39.10 | zwelch | yes, that is true... id should be possible, or how would you erase it? :/ |
| 06:39.12 | Zoiah | It's a 3com 3870, ES4649 and Dell PowerConnect 3324. |
| 06:39.24 | Zoiah | They're all from the same ODM, Accton(.com.tw). |
| 06:39.41 | Zoiah | I've been playing with and disassembling them for a while now. |
| 06:39.51 | zwelch | these days, i would expect a lot of devices are incorporating these features |
| 06:40.17 | zwelch | i am not passionate about reverse engineering, though i love to enable those who are ;) |
| 06:40.37 | Zoiah | I've mostly disassembled the firmware with IDA. |
| 06:40.55 | Zoiah | And actually ran into a backdoor user, that's enabled via telnet, with a password generated from the mac-address. |
| 06:42.12 | zwelch | sweet :) |
| 06:42.14 | zwelch | not surprising |
| 06:42.25 | zwelch | coughs and looks away quickly |
| 06:42.37 | Zoiah | Wah? |
| 06:42.44 | zwelch | i would never build such a thing into any products that i worked on |
| 06:42.46 | zwelch | coughs and looks away quickly again |
| 06:42.48 | Zoiah | ;) |
| 06:43.07 | Zoiah | Well, a backdoor user is understandable, but enabled via telnet is not so good. |
| 06:43.23 | zwelch | try explaining that to Corporate ;) |
| 06:43.47 | Zoiah | :) |
| 06:44.04 | Zoiah | I did notice two 'missing' SMD resistors on the PCB next to the MPC8245. |
| 06:44.29 | zwelch | wiggles his eyebrows with intrigue |
| 06:44.31 | Zoiah | One of them was 'unconnect' to CKSTP_IN. |
| 06:44.53 | Zoiah | The other to GND. |
| 06:50.00 | Zoiah | Actually, I'm not 100% sure about the pinout. |
| 06:50.26 | Zoiah | But it's very near to the CPU on both devices, it's 2x8 and the GND is on the right pin when I check: http://www.etoolsmiths.com/amcc-powerpc-405-jtag-pin-out.html |
| 06:50.39 | Zoiah | And openocd and urjtag are both able to see a JTAG chain when wired like this. |
| 06:51.58 | Zoiah | I'm just not entirely sure about JTAG. JTAG basically allows you to get and set pins on the chip? So all other functions like poke, detectflash, etc. are actually higher-level functions implemented by toggling pins? |
| 06:59.19 | zwelch | you are making the common confusion between JTAG and its most common purpose: boundary scanning |
| 06:59.30 | zwelch | JTAG allows you to access other functions than just toggling pins |
| 07:00.10 | zwelch | if you have the openocd svn, i just committed a new reference manual with a Technical Primer on JTAG :) |
| 07:00.32 | Zoiah | I should get it if I checkout the latest trunk? |
| 07:00.55 | zwelch | run 'doxygen Doxyfile' from the top of your working copy, then fire up doxygen/index.html in a browser and it should be easy to find |
| 07:01.27 | zwelch | i have a patch that will make this a little easier and cleaner |
| 07:01.35 | zwelch | can't decide whether to commit it or not |
| 07:01.50 | Zoiah | Make the generation cleaner? |
| 07:02.01 | Zoiah | Or the manual? |
| 07:02.20 | zwelch | the generation.... if it was the manual, it would be a no brainer :) |
| 07:02.35 | Zoiah | What would you patch? Generate it during make? |
| 07:02.42 | zwelch | make docs, yeah |
| 07:03.06 | zwelch | just a simple rule... and tiny perl script to make the output less verbose while still redirecting it to a log |
| 07:03.20 | Zoiah | "make docs" sounds like a common thing. |
| 07:03.32 | zwelch | it is, the catch is the perl script :) |
| 07:03.45 | Zoiah | What kind of catch? |
| 07:03.47 | zwelch | i _think_ everyone will have perl installed |
| 07:03.51 | Zoiah | Ahh, like so. |
| 07:03.53 | zwelch | but i am not sure |
| 07:03.58 | Zoiah | Dependency on perl. |
| 07:04.12 | Zoiah | And you can't easily implement it with awk or sed? |
| 07:04.15 | zwelch | i don't like adding gratuitous deps, but i think we already have it |
| 07:04.25 | zwelch | basically, autotools uses perl, doesn't it? |
| 07:04.29 | zwelch | automake at any rate |
| 07:04.45 | zwelch | can't remember, but i thought it gets required somehow :) |
| 07:05.09 | Zoiah | $ apt-cache show autoconf | grep ^Depends |
| 07:05.09 | Zoiah | Depends: perl (>> 5.005), m4 (>= 1.4.8), debianutils (>= 1.8) |
| 07:05.12 | zwelch | anyway, there is at least one perl script already in the tree (tools/rlink_speed_table_mumble/...) |
| 07:05.21 | zwelch | and there you have it :) |
| 07:05.27 | zwelch | so i suppose it's safe |
| 07:05.36 | Zoiah | But you only need autoconf when you need to bootstrap. |
| 07:05.52 | zwelch | touche |
| 07:06.22 | zwelch | well, it's part of the developer reference manual |
| 07:06.30 | Zoiah | Reimplementing the perl script in sed or awk is non-trivial? |
| 07:06.39 | zwelch | in theory, it should be used in the svn tree |
| 07:07.06 | Zoiah | doxygen is rather chatty indeed. |
| 07:07.07 | zwelch | oh, it might not be... but i have to admit that i never mastered those tools as well as I know that I should ;) |
| 07:07.54 | zwelch | it's really trivially: read and echo lines. print a '.' to stderr every N lines, and print a '\n' every C columns |
| 07:08.08 | zwelch | clever, but trivial ;) |
| 07:08.44 | zwelch | thus, 'make docs' does 'doxygen Doxyfile | dotty.pl >doxygen.log' |
| 07:09.15 | zwelch | dunno |
| 07:09.43 | Zoiah | I have to say my awk and sed skills are also less than stellar. ;) |
| 07:10.02 | zwelch | my argument might be that it could be an unlisted dep, since this documentation should not be generated during normal builds |
| 07:10.06 | zwelch | it takes too long, for one |
| 07:10.24 | zwelch | developers that want to run make docs |
| 07:10.47 | zwelch | ... should simply have to install perl... possibly at the same time they install doxygen and graphviz :) |
| 07:11.09 | Zoiah | Why print . to stderr? |
| 07:11.24 | zwelch | because it does >doxygen.log |
| 07:11.34 | Zoiah | Oh, the '.' output is for the user? |
| 07:11.42 | zwelch | it echos through, but that gets hidden... yup it shows progress |
| 07:11.57 | zwelch | on my machine, the process takes ~15 second even when nothing has changed |
| 07:12.12 | zwelch | when doing a fresh build, it takes a long time |
| 07:12.23 | zwelch | that's too long to go without indication of progress |
| 07:12.33 | zwelch | and it's impossible to debug the issues without a log |
| 07:12.42 | zwelch | so, the script is the best of both worlds... |
| 07:12.45 | zwelch | now, what i wonder: |
| 07:13.18 | zwelch | there has _got_ to be a tiny tool in a GNU package that provides this, and it's probably installed on my system |
| 07:13.21 | zwelch | what is it called? :) |
| 07:14.00 | zwelch | i've written a script like this several different times for different projects, and i can't be the only one |
| 07:14.50 | Zoiah | You'd say so, but... :) |
| 07:21.23 | Zoiah | cat doxyoutput | sed 's/.*/./' | sed ':a;N;$!ba;s/\n//g' |
| 07:21.45 | Zoiah | Hm, not to stderr. |
| 07:21.48 | Zoiah | And ugly. ;) |
| 07:22.13 | Zoiah | And it only outputs when the pipe is closed. |
| 07:22.30 | zwelch | no uglier than most of the stuff you see in autoconf's output :) |
| 07:23.00 | zwelch | perl's $| = 1 takes care of flushing after each '.', and it can manage pipes pretty well |
| 07:23.13 | zwelch | honestly, i could probably write it as a one liner. :) |
| 07:23.20 | zwelch | it would be sinfully ugly though |
| 07:25.43 | Zoiah | I just read the primer. |
| 07:25.54 | Zoiah | I guess that explains the shift dr and ir things I read in most examples. ;) |
| 07:29.00 | Zoiah | I should do some more reading to try to get the concepts through to my head. ;) |
| 07:35.11 | zwelch | yeah, the primer is just a start based on a single email from Strontium |
| 07:35.47 | zwelch | i think it is a great start, which is why i added it.... but there is a lot of information to grok, particularly when you consider that JTAG ends up being as general purpose as a UART |
| 07:36.03 | Zoiah | It would be nice to have a document like this explaining the various concepts. |
| 07:36.15 | Zoiah | http://www.engr.udayton.edu/faculty/jloomis/ece446/notes/jtag/jtag1.html |
| 07:36.18 | zwelch | that's what the manual was started for |
| 07:36.48 | zwelch | folks from this community simply need to write their own original material, spinning it for openocd |
| 07:37.03 | Zoiah | I found a lot of these low-level documents, but how it relates to the higher-level concepts is not very clear I think. |
| 07:38.22 | zwelch | i tend to agree |
| 07:38.41 | zwelch | there is a missing middle-layer of documentation that ties the two together |
| 07:38.48 | Zoiah | Yes. |
| 07:39.11 | zwelch | points to the new manual and grunts |
| 07:39.14 | Zoiah | Everybody is pasting the same list of 'instruction sample/preload', 'shift ir', etc. but nobody knows why. ;) |
| 07:45.34 | zwelch | i imagine the ieee spec would be informative |
| 07:45.51 | zwelch | i suppose it might even be worth the price |
| 07:47.53 | Zoiah | To you? |
| 07:48.33 | zwelch | to someone that wants to become a master |
| 07:48.46 | zwelch | i am not yet certain that person is me, but it might be ;) |
| 07:48.58 | Zoiah | I am just a hobbyst. :) |
| 07:49.53 | zwelch | i am between contracts in my career as a professional software engineer :) |
| 07:50.30 | Zoiah | Got some nice products on your resume? |
| 07:50.40 | zwelch | not as many as i would like |
| 07:51.10 | zwelch | but arm/linux machine #28 was my proudest, even if it was shortlived |
| 07:52.21 | Zoiah | You helped develop this machine? |
| 07:52.54 | zwelch | i was its sole software engineer during its initial development and subsequent launch |
| 07:53.07 | Zoiah | What was the goal of it? |
| 07:53.12 | zwelch | tdsway.com |
| 07:53.17 | zwelch | handheld computers |
| 07:53.31 | Zoiah | Ah, cool. |
| 07:54.05 | zwelch | indeed. i would love to find a similar job again, given what i have learned in the past decade |
| 07:55.06 | zwelch | then, i got hired because i played mandolin with its electrical engineer; now, i actually have the credentials to do it :) |
| 07:55.23 | Zoiah | Business is contacts. :) |
| 07:55.32 | zwelch | nevermind that i was successful at it then, no sane hiring manager would have ever let me in the door |
| 07:55.39 | zwelch | yup |
| 07:57.59 | Zoiah | The ranger was used in a few products? |
| 08:13.49 | zwelch | i was an oem handheld, yah |
| 08:14.02 | zwelch | many different markets |
| 08:14.11 | zwelch | however, it was really a wince device |
| 08:14.19 | Zoiah | Meh. ;) |
| 08:14.48 | zwelch | my linux port was a side-effort that they tolerated for a while |
| 08:15.01 | Zoiah | Was the linux port used in anything? |
| 08:15.20 | zwelch | years after i left then ended up getting a third-party to do a port for a newer product |
| 08:15.45 | zwelch | that port served one important purpose for me: it made me swear off working on windows ce |
| 08:15.56 | Zoiah | How so? |
| 08:16.01 | zwelch | i started a linux consulting company after that :) |
| 08:16.20 | zwelch | i have not and will not work on windows |
| 08:16.27 | zwelch | since then :) |
| 08:22.01 | Zoiah | One of my goals is to try to see if it's possible for me to boot u-boot and later maybe Linux on the device. ;) |
| 08:22.31 | Zoiah | It's currently running a custom bootloader from Accton booting an VxWorks firmware. |
| 08:23.05 | Zoiah | And then the next step would be to try to interface with the switching fabric on the PCI bus. ;) |
| 08:23.42 | zwelch | any time frame for these milestones? :) |
| 08:23.46 | Zoiah | Heh, no. |
| 08:23.59 | zwelch | then you stand a chance of succeeding :D |
| 08:24.06 | Zoiah | Just playing with unused parts. |
| 08:24.21 | Zoiah | I'm a network engineer and we've mostly migrated away from these parts. |
| 08:24.37 | Zoiah | Mostly due to the buggy software. |
| 08:24.43 | zwelch | hah :) |
| 08:24.57 | zwelch | it'd be neat if you could prove it wasn't the hardware :) |
| 08:25.08 | zwelch | i wonder if you could ask for a refund ;) |
| 08:25.16 | Zoiah | Heh, nah. |
| 08:25.37 | Zoiah | It's not only buggy, but also cumbersome in use. |
| 08:25.42 | Zoiah | Little to no logging. |
| 08:25.51 | Zoiah | Little to no diagnostic features. |
| 08:27.02 | Zoiah | I know some vendors selling switches based on similar silicon running Linux, but they are very niche and very expensive usually. |
| 08:27.25 | Zoiah | And often the linux is just a shim around the large binary blob that does all the real work. |
| 08:31.36 | zwelch | well, it sounds like you have your work cut out for you |
| 08:31.45 | zwelch | it would be hard to do worse than what you have :) |
| 08:32.19 | Zoiah | And the switches are written off anyhow, so even if I break them, ohh well. ;) |
| 08:32.37 | zwelch | plural... oh, boy... you have room for error :) |
| 08:33.05 | Zoiah | Yeah. :) |
| 08:33.26 | Zoiah | Now to figure out if I can communicate with the two Intel Strataflash devices. |
| 08:33.52 | Zoiah | Via JTAG to the MPC8245. |
| 08:34.40 | zwelch | should be possible |
| 08:35.14 | *** join/#openjtag pleemans (n=toi@d51A49C45.access.telenet.be) |
| 08:35.16 | Zoiah | How could I verify that at least my communication is correct? |
| 08:35.22 | zwelch | depends on their configuration though; there has been recent discussion in this area on the openocd list |
| 08:35.28 | Zoiah | I see an IR chain, a device, etc. |
| 08:35.29 | zwelch | well, can you id scan them? |
| 08:35.35 | zwelch | that's a good start |
| 08:35.44 | Zoiah | Yes, but the IDCODE is 0x0. But that's apparently normal for MPC824x. |
| 08:35.45 | zwelch | from there.... it's black magic |
| 08:35.57 | zwelch | fun |
| 08:36.21 | Zoiah | http://buffalo.nas-central.org/wiki/JTAG_Software/Openwince#Flash_Programming |
| 08:36.37 | zwelch | btw... "black magic" means i can't deconstruct the process to the point where i can eplain it :) |
| 08:36.49 | Zoiah | That's a completely different device, but the same CPU and the same output for 'detect'. |
| 08:37.07 | Zoiah | Heh. |
| 08:37.13 | Zoiah | Concepts. ;) |
| 08:37.28 | zwelch | they can be contagious. :) |
| 08:38.38 | Zoiah | But since my communication appears in order, the two missing SMDs are probably not directly related? |
| 08:38.51 | Zoiah | The PCB is filled with missing components. |
| 08:40.22 | zwelch | probably not related |
| 08:40.36 | zwelch | but without a schematic, who knows |
| 08:40.46 | Zoiah | Unlikely I'll be getting one soon. ;) |
| 08:41.47 | Zoiah | I tried tracing the lines on the PCB, but the PCB appears multilayer. |
| 08:46.22 | wookey_ | zwelch: I was indeed speaking of openocd |
| 08:47.05 | wookey_ | I've joined the mailing list and will post a report there to see if anyone can help. The problem seems to be a refusal to go into state 'halted' on 'reset halt' with the amontec |
| 08:51.57 | zwelch | cool. thanks for joining and i will look forward to your post |
| 08:52.18 | zwelch | wookey_: there's a lot of change going on in the community right now |
| 08:53.33 | zwelch | fwiw, i am having similar problems with my target, but i am not thinking they are related... just that there are lot of minor bugs to shake free from the tree |
| 10:03.13 | *** join/#openjtag moi1234 (n=moi@cpe-76-88-37-118.san.res.rr.com) |
| 10:11.43 | *** join/#openjtag keesj (n=keesj@ip49-193-210-87.adsl2.static.versatel.nl) |
| 10:20.52 | *** join/#openjtag starkmjolk (n=starkmjo@h-91-88.A163.priv.bahnhof.se) [NETSPLIT VICTIM] |
| 10:30.13 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 10:30.45 | *** join/#openjtag _julian (n=quassel@dslc-082-083-134-114.pools.arcor-ip.net) |
| 10:58.43 | _julian | hi all |
| 11:22.31 | *** join/#openjtag roxfan2 (n=dunno@244.163-244-81.adsl-dyn.isp.belgacom.be) |
| 11:30.30 | *** join/#openjtag building21 (n=building@wlan-client-312.informatik.uni-bremen.de) |
| 12:42.15 | _julian | I am new to openocd and am just trying to get a JTAG connection with a embedded-projects JTAG board and a LPC2144 uc. before I used a rowley adapter with the rowley sutdio, that worked well. now I wanted to start of making a lpc2144 config, I used the lpc2148.cfg and changed the flash size to 0x1f400 (128k), but this gives me the error: |
| 12:42.19 | _julian | Error: BUG: unknown bank->size encountered |
| 12:42.22 | _julian | any ideas on this? |
| 13:48.44 | *** join/#openjtag koobe_ (n=koobe@83.150.95.26) |
| 13:49.12 | mib_1a2ttd | 128k is 128*1024 = 131072 = 0x20000 |
| 13:58.00 | *** join/#openjtag StrontiumDog__ (n=Strontiu@24.13.111.218.klj01-home.tm.net.my) |
| 14:17.43 | *** join/#openjtag jamie (n=jamie@pdpc/supporter/active/jamie) |
| 15:23.20 | *** join/#openjtag building21 (n=building@dyndsl-095-033-087-246.ewe-ip-backbone.de) |
| 15:25.40 | *** join/#openjtag _julian_ (n=quassel@dslc-082-083-134-114.pools.arcor-ip.net) |
| 15:28.24 | *** join/#openjtag building21 (n=building@dyndsl-095-033-087-246.ewe-ip-backbone.de) |
| 16:11.58 | *** join/#openjtag dirk2 (n=dirk@p5B041D7A.dip0.t-ipconnect.de) |
| 16:47.53 | *** join/#openjtag Chocobo (n=Ask@strongbad.eece.maine.edu) |
| 16:48.19 | _julian_ | mlundin: ok, 0x20000 is accepted. actually the size for the lpc2138 was set to 512*1000, that's why did 128*1000, as well |
| 16:48.27 | _julian_ | anyway I do get: Error: RCLK not supported |
| 16:48.27 | _julian_ | Error: JTAG communication failure, check connection, JTAG interface, target power etc. |
| 16:48.58 | _julian_ | the same board works with rowley+crossconnect+adapter cable to the boards connector |
| 16:49.56 | Chocobo | Ok... pin 15 on the Olimex is RST... is this the "SRST" pin? if so, can I connect that to the RST pin on the target? I am having a bitch of a time with this ADuC, reset init says "SRST can not be asserted." but when I connect up the RST line OpenOCD whines about IR mismatch. It is very frustrating |
| 16:50.13 | Chocobo | I also have a pull up on RST. I can post a schematic if anyone would like. |
| 16:51.03 | Chocobo | this is killing me: Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x3f. tap=aduc7026.cpu pos=0 expected 0x1 got 3 |
| 16:51.42 | _julian_ | Chocobo: have the same error... still, I get the error I posted even before |
| 16:55.44 | mlundin | are you trying, or your cfg file, to set jtag_khz 0 ? |
| 16:55.45 | Chocobo | ugh... no work around? I have tried about every combination of reset_config. I am using OpenOCD 0.1.0 |
| 16:56.10 | Chocobo | I have been messing around with jtag_speed. let me trie jtag_khz |
| 16:56.52 | Chocobo | I just get an additional error: Error: RCLK not supported |
| 16:57.43 | Chocobo | jtag_khz 1 removes that error.... but the others are still there. |
| 16:57.50 | mlundin | I meant, that is the cause of this error message, sorry for confusion |
| 16:59.22 | Chocobo | Oh... nope. Here is my config file and the error output: http://pastebin.com/m63502fd6 |
| 17:01.30 | *** join/#openjtag jamie (n=jamie@pdpc/supporter/active/jamie) |
| 17:02.05 | mlundin | there is a communications failure, so all data are wrong. Try to run openocd with the -d3 flag to get more debug output |
| 17:05.19 | Chocobo | Not much new information: http://pastebin.com/m3ee72dd2 The interesting thing is... if I disconnect the RST line it works .... better. Not great, the reset command is all screwed up but at least it finds the device. |
| 17:06.56 | Chocobo | ooooooh interesting. I cut the RST line and it is still doing it. |
| 17:23.19 | Chocobo | ugh, I just don't know. |
| 18:22.41 | Chocobo | when issuing a "reset halt" you would expect the PC to be 0x00000000 correct? |
| 18:24.59 | Chocobo | I have managed to get it so this is the worst offender: srst pulls trst - can not reset into halted mode. Issuing halt after reset. |
| 19:08.00 | mlundin | this is old discussion, some processors cannot be be reset to halt, security feature to hide rom contents. Boot code must initialize debug access. |
| 19:09.31 | mlundin | for my lpc2148 reset halts stops at 0x00000378 |
| 20:44.52 | *** join/#openjtag building21 (n=building@p5B10745F.dip.t-dialin.net) |
| 21:49.04 | *** join/#openjtag jamie (n=jamie@pdpc/supporter/active/jamie) |