00:10.25 | *** join/#openjtag flyhorse|linux (~flyhorse|@183.22.233.246) |
01:16.58 | *** join/#openjtag _julian_ (~quassel@dslb-088-071-078-190.pools.arcor-ip.net) |
01:27.01 | *** join/#openjtag Openfree` (~Openfreer@116.228.88.131) |
01:32.30 | *** join/#openjtag Openfree` (~Openfreer@116.228.88.131) |
02:04.35 | *** join/#openjtag nslu2-log (~nslu2-log@limax.nslu2-linux.org) |
05:05.14 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
07:15.54 | *** join/#openjtag roxfan (dunno@91.180.225.31) |
08:21.57 | *** join/#openjtag baddu (~salko@nat/nokia/x-ycuprieqejensxme) |
09:57.37 | *** join/#openjtag pirho (debian-tor@gateway/tor-sasl/pirho) |
09:57.49 | *** part/#openjtag pirho (debian-tor@gateway/tor-sasl/pirho) |
10:06.15 | *** join/#openjtag roxfan (dunno@91.180.114.167) |
10:52.15 | *** join/#openjtag nslu2-log (~nslu2-log@limax.nslu2-linux.org) |
16:11.11 | zergos | hello |
16:11.29 | zergos | i have a problem with GCC i got this error : region sram is full |
16:11.59 | zergos | i not understand how to avoid |
17:44.18 | Weaselweb | zergos: 1st, this has nothing to do with jtag. 2nd, i guess your code size for this sram section is too big |
18:08.52 | zergos | Weaselweb, thx for answer, i know is big, but how this happend interest me, and about jtag i have a problem, with 1 of my boards, have you already used board with AT91sam9261 ? |
18:14.36 | Weaselweb | zergos: no, not 9261. but 9260, 9263 and 9g20 |
18:15.06 | Weaselweb | afaik all have different sram sizes and/or blokcks |
18:15.39 | zergos | Weaselweb, yes, with at91sam9 i still not arrive to connect on jtag |
18:16.06 | zergos | looks something not good in config script |
18:16.18 | Weaselweb | be sure, you run jtag_clock 1/6 of core clock at maximum |
18:16.37 | Weaselweb | especially when running in slow clock mode |
18:17.04 | Weaselweb | paste error messages, otherwise nobody may help you |
18:17.44 | zergos | Error: Could not probe bank: no QRY |
18:17.44 | zergos | Try workaround w/0x555 instead of 0x55 to get QRY. |
18:17.44 | zergos | Error: Could not probe bank: no QRY |
18:18.04 | Weaselweb | this is from probing NOR flash |
18:18.08 | Weaselweb | using CFI |
18:18.38 | Weaselweb | if you don't have one, remove the flash bank entries from your config file |
18:19.56 | zergos | flash bank at91sam9261.flash cfi 0x40000000 0x1000000 2 2 0 $_TARGETNAME |
18:20.24 | *** join/#openjtag toi (~toi@d54C2AA76.access.telenet.be) |
18:20.50 | zergos | but flash is NAND not NOR |
18:20.58 | Weaselweb | that sound like a 16MiB 16bit NOR-FLash on chip select 3 iirc, do you have such device mounted? |
18:21.16 | Weaselweb | afaik nand is properly supported from openjtag |
18:21.19 | Weaselweb | isn't! |
18:21.29 | Weaselweb | just remove this line |
18:22.29 | zergos | but how interface will know about flash chip |
18:22.57 | zergos | i m sorry, its first time i use board with external flash and ram |
18:23.10 | Weaselweb | afaik, you can't program NAND flashes from openocd, use sam-ba for that |
18:23.44 | Weaselweb | or u-boot |
18:23.53 | zergos | ah |
18:24.01 | Weaselweb | which needs to be flashed first, though :) |
18:24.10 | zergos | uff |
18:24.11 | zergos | :D |
18:24.12 | zergos | i see |
18:24.29 | zergos | so jtag is not userfull in this case ? |
18:24.35 | Weaselweb | did you read sam4linux.org? |
18:24.44 | zergos | not |
18:25.09 | Weaselweb | well, it could be usefull i you have a nand programm application which you can write to sram or sdram and run it from there |
18:25.22 | Weaselweb | but otherwise, I would use sam-ba to program NAND flash |
18:25.56 | zergos | and in case is NOR ? |
18:26.03 | zergos | is possible over jtag ? |
18:26.17 | Weaselweb | yep, i programmed NOR several times using openocd |
18:26.26 | Weaselweb | this is plain CFI, hopefully |
18:26.31 | zergos | i see |
18:26.40 | zergos | so i made mistake by buying my board :( |
18:26.44 | Weaselweb | some devices seem to be buffy |
18:27.16 | zergos | now have to understand why is presend JTAG port on board |
18:27.28 | zergos | if cant program over there |
18:27.30 | Weaselweb | well, your dealer should have some descriptions how to start |
18:27.48 | zergos | yes u-boot |
18:27.53 | zergos | but in this case why is there jtag |
18:28.00 | Weaselweb | some other debuggers can program nand, openocd seem to support this not well enough |
18:28.12 | zergos | aha |
18:28.14 | zergos | i see |
18:28.47 | Weaselweb | is IS possible to flash NAND using jtag, but openocd can not AFAIK |
18:28.54 | Weaselweb | to make this clear :) |
18:28.56 | zergos | and about your boards, does their chipset got embedded flash memory ? |
18:29.24 | Weaselweb | nope, either NAND or NOR |
18:29.34 | Weaselweb | which means external flash memory |
18:29.47 | zergos | ok |
18:30.00 | zergos | have did any application with encrypted flash ? |
18:30.02 | Weaselweb | iirc 9g45 or 9g10 have internal flash memory |
18:30.17 | zergos | + external , |
18:30.18 | zergos | ?N |
18:30.28 | Weaselweb | encrypted? had nothing to do with that yet |
18:30.49 | zergos | i mean against dump :D |
18:31.38 | Weaselweb | preventing erasing? depends on the device, some have block write protection |
18:31.40 | zergos | about openocd, what for is Nand function ? |
18:32.10 | zergos | i seen this in 0.1 |
18:32.12 | zergos | oups |
18:32.14 | zergos | 0.4.0 |
18:32.25 | Weaselweb | I read once about NAND in some openocd comment this is not finished yet. but coult be outdated. didn't tried yet again |
18:32.32 | Weaselweb | that was < 0.4.0 |
18:33.01 | Weaselweb | sry, but I'm afk now |
18:33.11 | zergos | oki thank you for all answers |
18:33.20 | Weaselweb | you're welcome |