<wpwrak> mwalle: hmm, another nice feature for urjtag would be if -q actually did anything :) the chattiness is a little inconvenient at times ...
<kristianpaul> Fallenou: when i read _any_ register from milkymist soc, i must always use volatile unsigned int? i cant do  volatile signed short int reads?
<kristianpaul> Fallenou: i mean, the reads and writes are fixed to to 32 bits? no more no less?
<stekern> kristianpaul: CSR doesn't seem to have a datamask, so writes can't work with anything else than 32-bit
<stekern> why do you want to access them at non 32-bit granularity?
<kristianpaul> stekern: and that datamask should be related with sel_i i guess
<kristianpaul> stekern: i'm trying to print (%d) (using milkymist software) some registers stored  in a 16 bits register (this goes to the verilog module) but of course
<kristianpaul> wb_dat_o <= {16'h0, i_16_bit_register};
<kristianpaul> so when i read as a volatile signed int, still be printed as a unsigned
<kristianpaul> and when try it as short, well i just got zeros be printed
<kristianpaul> bbl
<stekern> kristianpaul: you could always sign extend it in the verilog module. or in sw before you print it
<wpwrak> maybe try this: volatile uint32_t *p = whatever; value = (int16_t) *p;
<stekern> wpwrak: yep, that would be how to do it in sw, let's serve the verilog version on silverplate too: wb_dat_o <= {16{i_16_bit_register[15]}, i_16_bit_register};
<stekern> ;)
<wpwrak> stekern: now you've made it complicated and he has to choose where to do the sign extension ;-)
<stekern> hehe, freedom of choice! :)
<scrts> hi guys ;)
<Alarm> hi
<Alarm> he following line: "qemu-system-LM32-M-kernel Milkymist flickernoise" must be executed in which folder?
<Alarm> *the
<sb0> er... first you should probably pay more attention to the syntax and spelling of the command
<Alarm> I did a copy / paste the command in the wiki http://milkymist.org/wiki/index.php?title=Using_QEMU
<sb0> your clipboard has an interesting behaviour :) mine gives 'qemu-system-lm32 -M milkymist -kernel ...' instead
<sb0> anyway 1. qemu-system-lm32 should be in your PATH 2. the executable passed as parameter to -kernel is relative to the current folder (unless you give an absolute path, i.e. starting with /)
<Alarm> I can not locate flickernoise? I find flickernoise.fbi,
<Alarm> I had to forget something when I compiled?
<sb0> try: make bin/flickernoise
<Alarm> No rule to make target `bin/flickernoise'
<Alarm> unless I am mistaken, 'make-compile-flickernoise flickernoise.fbi C' can not create file 'flickernoise "for qemu
<sb0> ah, you are using xiangfu's scripts... try going one level below and rebuild only flickernoise
<Alarm> ok thanks
<kristianpaul> stekern: wpwrak i choose verilog way, hardware is faster :)
<kristianpaul> stekern: Thanks !!