| --- Log opened Sun May 03 00:00:33 2015 | ||
| olofk | stekern: Maybe you could push the sockit dts to orpsoc-cores? | 06:28 |
|---|---|---|
| stekern | olofk: I don't have one for the current sockit in orpsoc-cores | 06:30 |
| olofk | ah ok | 06:30 |
| stekern | you know what we should do if we host the orpsoc-cores dts'es in orpsoc-cores, we should make a common dts that the others can include, and just enable the peripherals that is in use | 06:31 |
| stekern | since we are using a unified memory map and irqs | 06:32 |
| olofk | Do we need to merge them manually, or can you specify multiple dts files in Linux? | 06:32 |
| stekern | you "merge" them manually, by saying #include "orpsoc-cores.dtsi" | 06:35 |
| stekern | for instance | 06:36 |
| olofk | ah cool | 06:36 |
| olofk | didn't know | 06:36 |
| stekern | you can look at the the socfgpa dts for an example: https://github.com/openrisc/linux/blob/master/arch/arm/boot/dts/socfpga_cyclone5_sockit.dts | 06:36 |
| olofk | I still want something built on top of FuseSoC that can provide a little better integration for OpenRISC systems | 06:38 |
| olofk | Like generating a BSP from the contents of wb_intercon.conf and pulling in drivers from each core | 06:38 |
| stekern | something I'd really like would be some way to inherit systems/cores | 06:39 |
| olofk | You can do that somewhat for the RTL files, but not for other files. | 06:40 |
| olofk | Are you thinking about the dts file, or something else? | 06:41 |
| stekern | no I meant the whole system | 06:43 |
| stekern | de0 nano could be inhereted from mor1kx-generic for instance | 06:43 |
| olofk | Yeah, I've been looking for something like that too | 06:44 |
| stekern | I want to add a de0 nano system that has support for all the cool stuff my migen extension boards have | 06:44 |
| olofk | s/migen/minimig ? | 06:45 |
| stekern | now, that means I just copy the existing one hack that up | 06:45 |
| stekern | yes, minimig ;) | 06:45 |
| stekern | too much stuff starts with 'mi' | 06:46 |
| stekern | migen, milkymist, minimig, mist... | 06:46 |
| olofk | Yeah, and that was one of the intentions with FuseSoC. A bit sad that it's not really there yet | 06:46 |
| stekern | does any board use the opencores sdcard core yet? | 06:47 |
| olofk | I think that ordb2a uses it, but it's only available in an orpsocv2 fork in the VirtualBox image | 06:48 |
| stekern | oh, right | 06:48 |
| stekern | because, it'd actually be pretty cool if the sdcard accesses on the minimig-de0_nano could be speed up by using that | 06:49 |
| olofk | stekern: If you depend on de0_nano in your minimig port, what do you need to change? top-level, pin assignments, constraints? | 06:49 |
| stekern | yes | 06:50 |
| olofk | s/?/...anything else? | 06:50 |
| stekern | no, I think that's it. I'll of course need to extend the .core file and change wb_intercon | 06:51 |
| olofk | true | 06:51 |
| stekern | but that's my point, you should be able to have a base 'class' and only define/override the things you actually want to change | 06:51 |
| olofk | hmm... I'm thinking about how to do that | 06:52 |
| stekern | and for the top-level, I think that the template system that hansfbaier started to look into would be a good step towards it | 06:53 |
| olofk | I was hoping that IP-Xact could take away some of the boring aspects of top-level generation, but I forgot that XML files are horrible for VCS | 06:56 |
| olofk | For tcl/sdc files I'm thinking of using the same solution as for RTL files, with private_tcl_files for files that you don't want other systems to inherit | 06:59 |
| olofk | That will make it easier to reuse snippets of constraints for example in CDCs found in subcomponents | 07:00 |
| stekern | yes, and tcl/sdc files are pretty easy to make modular, like we had for de0 nano in orpsocv2 | 07:06 |
| GeneralStupid | whats about conf.d folders? | 07:49 |
| bandvig | latif: I've never used the orpsocv2. I read the blog just a general guiding a used fusesoc. Excuse me, but I haven't any more ideas. | 09:20 |
| olofk | latif: I'm trying to figure out how to debug this. It's a bit awkward without a real debugger. I see several potential problems | 09:45 |
| olofk | 1. The boot ROM doesn't copy the image from flash to RAM and execute it | 09:45 |
| olofk | 2. The image in the Flash is broken | 09:46 |
| olofk | 3. The file is loaded correctly, but the program itself doesn't work | 09:46 |
| olofk | 4. Anything else :) | 09:46 |
| olofk | antgreen: Do you have a clue why objcopy makes the verilog memory files executable? | 10:02 |
| GeneralStupid | i need some help with that GDB :) | 10:02 |
| olofk | ahh.. could it be because I'm creating it via an elf file | 10:02 |
| GeneralStupid | continue does not mean that the program is running permanent? | 10:03 |
| olofk | GeneralStupid: Not an gdb expert, but when I used gdb on OpenRISC I used detach instead of continue | 10:03 |
| olofk | But I mostly just used OpenOCD nowadays. It works fine if I just want to download and run programs and look at registers and memory | 10:05 |
| GeneralStupid | Ohh iam too stupid :) Its working... all LEDs are lighting because its too fast :) | 10:06 |
| olofk | haha | 10:06 |
| GeneralStupid | i wish i could say im doing this the first time this year | 10:06 |
| olofk | me too :) | 10:06 |
| olofk | stekern: Have you programmed the de0 nano SPI Flash with an FPGA image + sw? | 10:14 |
| GeneralStupid | Info : clock speed 3000 kHz | 10:16 |
| GeneralStupid | isnt that a bit low? :-D | 10:16 |
| olofk | GeneralStupid: haha. It's the JTAG clock | 10:16 |
| GeneralStupid | ok. I mean "Info: Clock Speed" is very misleading for a hardware newcomer like :) | 10:24 |
| olofk | I won't argue with that :) | 10:24 |
| olofk | Alright. I pushed some patches to de0 nano to port over the SPI boot loader from ORPSoCv2 | 10:25 |
| olofk | I'll soon release my or1k_bootloaders repo so that it will be available to all systems | 10:25 |
| GeneralStupid | i dont think thats normal behaviour?! if i do reset in telnet my LEDs still lighting. | 10:35 |
| GeneralStupid | he dont react to the reset pushbutton | 10:35 |
| olofk | strange | 10:37 |
| GeneralStupid | i put everything into a while loop thats ok ? I want to run it forever... | 10:40 |
| olofk | Can't see a problem with that | 10:46 |
| GeneralStupid | https://dpaste.de/r3C7 | 10:50 |
| GeneralStupid | ok i got it | 11:07 |
| GeneralStupid | for normal GPIO the size is 2, if i dont need them bidirectional (for LEDs) the size is only 1. So 0x9...0 is the data, and 0x9...1 is useless | 11:07 |
| GeneralStupid | For the "normal" configuration i have on github. Is it bad to have alld LEDs in between 0x900000 and 0x9000?? ? ... | 11:08 |
| stekern | olofk: yes, some time long ago | 11:25 |
| olofk | GeneralStupid: There is some kind of semi-standardized address space for the OpenRISC systems, but I'm not sure what is said about extra GPIO components | 11:44 |
| olofk | stekern: ah ok. I've never done it with the Altera tools so I'm not sure about how to do it | 11:46 |
| stekern | you need to generate a .pof file | 11:51 |
| stekern | I can look up how it was done when I'm back home | 11:51 |
| olofk | cool. That would be great | 11:51 |
| olofk | Just found that you have a de2_115 port for ORPSoCv2 at chokladfabriken also | 11:52 |
| GeneralStupid | do i have to do anything to roll out the changes to the register? | 13:24 |
| olofk | GeneralStupid: Not sure what you mean | 13:35 |
| GeneralStupid | i want to "listen" to a button... while(1) { if (button_pressed) led1 = 1; else led1 = 0; } | 13:37 |
| GeneralStupid | but it goes only into else | 13:37 |
| olofk | No, that should work | 13:37 |
| GeneralStupid | https://dpaste.de/q7AA | 13:38 |
| GeneralStupid | thats it actually | 13:38 |
| olofk | hmm | 13:40 |
| GeneralStupid | ok forget it, lets try something different. How do you start programs with openocd? | 13:40 |
| olofk | Your leds are mapped to 0xb0000000 | 13:40 |
| olofk | ? | 13:40 |
| GeneralStupid | please np | 13:41 |
| GeneralStupid | 0xb3000000 | 13:41 |
| GeneralStupid | Ok thats right | 13:41 |
| olofk | ah sorry. Yes. See it now | 13:42 |
| olofk | ok. Loading programs with openocd then | 13:42 |
| olofk | connect openocd (I assume you know that part if you're using gdb) | 13:43 |
| olofk | Then start a new terminal and run telnet localhost 4444 | 13:43 |
| GeneralStupid | ok | 13:44 |
| olofk | The it's just halt; load_image <elf file>; reg npc 0x100; reset | 13:45 |
| olofk | or perhaps resume instead of reset | 13:46 |
| olofk | gtg | 13:48 |
| GeneralStupid | olofk: thanks, its the same issue. i have to try out a bit more | 13:50 |
| GeneralStupid | okay okay, there is a failure in that pinmap from terasic. Switches 0 to 7 are mixed up with 8 to 15 | 14:28 |
| stekern | olofk: it wasn't called .pof, but .jic | 16:01 |
| stekern | but I think that .pof actually is something too | 16:01 |
| stekern | anyway, this are the steps, and I got them from a guy called gong tao | 16:01 |
| stekern | create a .cof file, for example like this: http://oompa.chokladfabriken.org/openrisc/orpsoc.cof | 16:02 |
| stekern | then cherry pick what you need from this: | 16:02 |
| stekern | http://pastie.org/10126830 | 16:02 |
| latif | hi all.. have a nice day... | 16:03 |
| stekern | now when I look at this again, I think juliusb might have copied those instructions to some wiki page or something ;) | 16:03 |
| latif | olofk: I think there is a problem with atlys.S which is in or1k-tollchain... board mem size was defined 0x2000000..that means 32 megabyte..but atlys has a 128 megabyte ddrram... | 16:05 |
| stekern | latif: you're right, that's wrong | 16:07 |
| stekern | it's my mistake, I probably just copied it from the de0 nano one and forgot to change it | 16:08 |
| GeneralStupid | i have 32 defined but only 8 on board | 16:09 |
| GeneralStupid | stekern: i will put it on my to do list :) | 16:09 |
| stekern | that's worse ;) | 16:09 |
| latif | also there is a problem in this tutorial...http://www.rte.se/blog/blogg-modesty-corex/loading-and-executing-program/2.7 the mem size was defined as 0x800000 ..but this should be 0x8000000.. one 0 is missing!! | 16:09 |
| GeneralStupid | stekern: i will propably add a "driver" for 7 segment display | 16:10 |
| GeneralStupid | i need to ask if it is able to publish | 16:10 |
| latif | can someone say me that what is the defined mem size for atlys in or32 toolchain??? | 16:11 |
| latif | aha soryy.. in or32 toolchain there doesnt exist atlys.S... forget about it:) | 16:14 |
| GeneralStupid | oh fuck, i have to optimize a lot my fpga is very full right now :) | 16:20 |
| GeneralStupid | Okay 0x400000 . I check it | 16:30 |
| latif | stekern:olofk: I ve got a question.. flash size of atlys is 16 mb..ram is 128 mb.. in flash size image 1.5 mb is for a bit file (for example openrisc processor) and 14.5 mb is for user data or program etc.. But if or1k-elf thinks that there is a 128 mb area and compiles the a code it may causes an error for spi flash..because it is just 14.5 mb..this is may be the error..just a questiıon?? | 18:00 |
| latif | I mean if a code compiles for 128 mb or 32mb even if it is small it may causes an error while it is being writed to the spi flash..because it is just 16 mb and just 14.5 mb is for user program..I think this is not correct..is it?? | 18:02 |
| latif | olofk: stekern: yes that is why spi flash is not booted... because of this mem eroor.. I made the mem size 8 mb in atlys.S and compiled it then put it in /opt/or1k...libboard-atls.a .. then I used v2 and a led test program.. at the end I have managed to write .mcs file to spi flash and booting gpga from spi!! | 18:59 |
| latif | I am realy happy about that :) | 18:59 |
| stekern | latif: that shouldn't be related at all, the setting you changed is only used to setup the stack pointer | 19:40 |
| latif | stkern: I dont know what the whole problem is... I can just say that now I can access Leds and booting FPGA from SPI.. by using orpsocv2.. tomorrow ı will try to do it with orpsocv3.. | 19:50 |
| olofk | latif: Great to hear that it's working out | 21:46 |
| olofk | GeneralStupid: Seems like you managed to get things working as well. Great | 21:47 |
| olofk | stekern: Thanks for the instructions. I'll see if I can try them out tomorrow. I've been working a bit on the de0 nano port recently | 21:48 |
| olofk | Still considering to throw out the or1200 support to make it a bit cleaner. On the other hand, it doesn't add too much complexity and it can be nice to have the choice | 21:48 |
| GeneralStupid | olofk: yes its getting forward but its only a side project. :) | 22:19 |
| GeneralStupid | thx 4 help | 22:20 |
| --- Log closed Mon May 04 00:00:21 2015 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!