Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 411
» Latest member: anouarnechi
» Forum threads: 122
» Forum posts: 415

Full Statistics

Latest Threads
several questions about P...
Forum: PULP General questions
Last Post: ninipa
Today, 06:55 AM
» Replies: 2
» Views: 15
Editor to use with pulpis...
Forum: PULP General questions
Last Post: bluewww
Yesterday, 04:19 PM
» Replies: 2
» Views: 37
Vsim schematic doesn't wo...
Forum: PULP General questions
Last Post: Nordic
Yesterday, 08:14 AM
» Replies: 8
» Views: 86
PULP-sdk on centOS: error...
Forum: PULP General questions
Last Post: kgf
04-02-2020, 09:18 AM
» Replies: 1
» Views: 55
Hello example
Forum: PULP General questions
Last Post: bluewww
03-30-2020, 07:25 AM
» Replies: 1
» Views: 77
Pulpissimo: Using JTAG an...
Forum: PULP General questions
Last Post: LPLA
03-09-2020, 12:15 PM
» Replies: 2
» Views: 331
using axi from rtl and C ...
Forum: PULP General questions
Last Post: sake
03-06-2020, 06:25 AM
» Replies: 2
» Views: 343
Regarding uDMA SPI Master
Forum: PULP General questions
Last Post: fconti
03-04-2020, 06:39 PM
» Replies: 1
» Views: 331
FPGA - Booting (.bit + .e...
Forum: PULP General questions
Last Post: AhmedZaky
02-18-2020, 07:37 AM
» Replies: 0
» Views: 335
UART test case
Forum: PULP General questions
Last Post: zhouqiang
02-17-2020, 03:16 AM
» Replies: 2
» Views: 942

 
  several questions about Pulpissimo SoC platform
Posted by: ninipa - Today, 03:33 AM - Forum: PULP General questions - Replies (2)

Hi,
I've already run "Hello" case successfully with Xcelium, now I have some further questions:
1. In readme I see it says "Either the RI5CY core or the Ibex one as main core". So by default, if I've built everything following readme, which core is used in the Soc?
2. In ARM cores, there is usually a program counter (PC) register, so that users can simply know where the issue happens (with disassembly code). Is there the similar register in Pulpissimo?
3. I see ./sim/boot/boot_code.cde is loaded in boot_rom. Is this boot_code.cde necessary for all the cases? Via the waveform of "Hello" case, I see something is read from boot_rom, but i'm not sure if the boot code is really used or not. What does the boot code do? Initialize the SoC? If I put my executable in SPI flash, can I still reuse the boot code before jumping to SPI content?

Print this item

  Editor to use with pulpissimo?
Posted by: sake - Yesterday, 06:40 AM - Forum: PULP General questions - Replies (2)

Hey,

What kind of setup do you people use to work with pulpissimo?
I would also like to know about editor extensions that might provide auto-completion, jumping to definition and integration with make build errors.

Print this item

  Vsim schematic doesn't work (PULPissimo)
Posted by: Nordic - 04-03-2020, 09:14 AM - Forum: PULP General questions - Replies (8)

Goodmirning everyone Smile 

I was trying to track some signals using che schematic tracer built inside Vsim. I tried to do this using the hello test program inside the pulp-rt-examples repo.

I called the simulation enabling the gui using the commands:

Code:
- make clean all
- make run gui=1


but once vsim gui starts, when i try to send the selected instance to vsim schematic editor (doing Rmouse click on the instance -> Add to -> Schematic) i got the following error:
 
# Debug data file, vsim.dbg, does not exist.

#
# Invoke vsim with -debugDB to create this file.

So, i tried to manually set the command -debugdb inside the script invoked before running.


The vsim options file invoked might be located in: pulpissimo/sim/tcl_files/run.tcl and i changed the label to be:

Code:
set TB "vopt_tb -L models_lib -L vip_lib -debugdb"


i try to run the simulation once again, and i noticed the file vsim.dbg has been created inside the working folder (pulp-rt-examples/hello/build/pulpissimo). However when i try to send the instance inside the schematic tracer again i get the following error:

# Schematic viewing and causality tracing unavailable.

# Possible reasons are :
# 1. vopt was run without -debugdb
# 2. The -novopt option is given with -debugdb which is not allowed.

I tried to manually set vopt that might be invoked from the file located in: pulpissimo/sim/tcl_files/config/vsim.tcl

I modified the related vopt arg list to be something like:

Code:
quietly set vopt_args ""

if {$vopt_acc_ena == "YES"} {
 #+ quietly append vopt_args $vopt_args "+acc=abflmnprstv"
 quietly append vopt_args $vopt_args "+acc=mnprv \
                                      -assertdebug \
                                      -bitscalars \
                                      -fsmdebug \
                                      -debugdb \  //line added by me
                                      -linedebug"

both commands are recognised by vsim inside the gui debug windows, but the error which appears is one more time the latter i have shown:

# Schematic viewing and causality tracing unavailable.

# Possible reasons are :
# 1. vopt was run without -debugdb
# 2. The -novopt option is given with -debugdb which is not allowed.

Have I done the whole process correctly, or there are already some command line options i need to set in order to activate the debugdb?

Thanks for the time you will dedicate to me, and thanks in advance for all the incoming suggestions Smile

Print this item

  PULP-sdk on centOS: error during build + fix
Posted by: Nordic - 04-02-2020, 09:15 AM - Forum: PULP General questions - Replies (1)

Hello, and thanks for let me join inside your community!

I am writing this thread for sharing to all of you the problem I faced building PULP-sdk on a centOS 7 distribution; and how I solved that without let other people to struggle as I did for solving this.

I was trying to recreate and setup the PULPissimo platform due to functionality analysis. I Have installed each of the requested components (gcc, pulp-sdk, pulp-builder, PULPissimo) inside a generic root project folder called  <user_project_folder_path>. Each of those component has been built inside a dedicated folder. In order to be able to simulate the platform, one of the needed steps is to setup and build the sdk. I moved to the PULP sdk main page, and then followed these steps:
Then, I Set the requested env variables, linking the toolchain and vsim paths:

Code:
- export PULP_RISCV_GCC_TOOLCHAIN=<user_project_folder_path>/opt/riscv/bin
- export VSIM_PATH=<user_project_folder_path>/pulpissimo/sim

As suggested form the guide, I first need to download and build the PULPissimo sdk. Since I am running the project on a centOS 7 operating system, then I installed the suggested dependencies:

Code:
- sudo yum install git python36-pip python36-devel gawk texinfo gmp-devel mpfr-devel libmpc-devel swig libjpeg-turbo-devel redhat-lsb-core doxygen python-sphinx sox GraphicsMagick-devel ImageMagick-devel SDL2-devel perl-Switch libftdi-devel cmake cmake3 scons
- sudo python3 -m pip install --upgrade pip
- sudo python2 -m pip install --upgrade pip
- sudo python3 -m pip install artifactory twisted prettytable sqlalchemy pyelftools openpyxl xlsxwriter pyyaml numpy configparser pyvcd
- sudo python2 -m pip install configparser

and after I cloned PULP-sdk repo on branch master 

Code:
- cd <user_project_folder_path>
- git clone https://github.com/pulp-platform/pulp-sdk.git -b master
- cd pulp-sdk
- source configs/pulpissimo.sh
- source configs/platform-rtl.sh
- make all


The make command started the building for a while, but after at a time it gives the following error (showed also inside the attached screenshot):

camera/camera.cpp:24:22:: fatal error: Magick++.h: No such file or directiry
  #include <Magick++.h>
 
compilation terminated.

After double checking all the dependencies I started browsing and comparing the same steps using a fresh 16.04 Ubuntu distribution, with resulting that the whole process worked fine on Ubuntu but not on centOS distribution. After struggling and after a long research, I found that inside the dependencies was missing the development library furnished by Magick++. The related dependence was solved installing:

Code:
- sudo yum install GraphicsMagick-c++-devel

After calling again the build command make all, I’ve been able to complete the whole sdk build and setup process, which let me able to move throught the following steps in the process. I still don’t know if this error come for some kind of lacks inside my system or not. If someone inside the PULP team want to try and replicate the behaviour, would be nice to fix the missing dependence from the git list in order to solve this problem for all the users which are using the same operating system as me. Anyway, I Hope this might be useful for all those people will found the same error: here’s the fix which can help you saving a lot of precious time Smile

Print this item

  Hello example
Posted by: nayan - 03-30-2020, 06:39 AM - Forum: PULP General questions - Replies (1)

How can I view the intermediate trees generated after make clean all run in hello example

Print this item

  Pulpissimo: Using JTAG and Flash for larger sets of data
Posted by: LPLA - 03-06-2020, 05:24 PM - Forum: PULP General questions - Replies (2)

I couldn't think of a more descriptive title so let me please explain what i am trying to achieve.

I'm using a hardware accelerator and have quite some amount of data (weights, inputs, etc) that i need to send to the accelerator.
The idea was to use the SPI flash model to store the flash_stim (and the other data) in the flash memory, without using the UserPreload feature.
Now there are a few things that aren't clear to me which i couldn't resolve by reading the issues on github or reading the forum.

Here is my approach so far:

First i wrote an application to send data to the flash memory, similar to the send example.
I created an array that contains some data with the intend of having this array contain the data from the flash_stim.slm file (without the addresses).
This worked for smaller data sets where i defined an array with random sample data to send to the flash.
At some point the array (and therefore the whole code) was simply too big to fit in the Pri banks of the L2 memory and i was stuck in "Waiting for end of computation".

So now i am using JTAG to load my data into the non Pri banks of the L2 memory.
The goal is to send this data to the flash memory, effectively making the flash memory contain the same data as if i had been using the UserPreload feature of the S25FS256S model.
Sending data to the L2 via JTAG of course works fine but also raises the first question.
There are different stimuli files for either JTAG (stim.txt) or STANDALONE (flash_stim.slm).
Effectively they should both do the same thing in the end, but are different in size and format.
For example i can't use readmemh to load the flash_stim.slm into the stimuli array.

As far as i understand there is no way to directly load the flash memory via JTAG because it's not memory mapped, correct?
If this is true, then would the correct way to do this be:
1) Use JTAG to load the image (in this case the stim.txt) into L2 just as you would do when booting from L2 but use a different address (e.g. 0x1C030000).
2) Use SPI to transfer that data to the flash memory (this i do by code, similar to the send example i mentioned, using pulp_read32 to get the data from L2, but this seems rather inefficient).
3) Now i should be able to boot from ROM even tho i didn't use the UserPreload feature.

What i am wondering about are the following things:
- Is the way i described above the correct or rather most efficient way to do this?
- Is there a way to load the flash_stim.sml to flash without using the UserPreload feature or converting the format so readmemh can be used?
- This issue mentions the way to do this would be to write data from JTAG to L2 (like i am doing too) and then to engage the udma to transfer this data to the flash. Unfortunately i'm not sure how you would do this and i couldn't find a documentation or guide on this.

Thank you for your help,
LPLA

Print this item

  using axi from rtl and C code
Posted by: sake - 03-05-2020, 07:36 PM - Forum: PULP General questions - Replies (2)

Hi, I'm trying to add hardware accelerator to the system that would connect with axi-lite slave to pulpissimo.
The system already has master there that I can access from CPU?
I have skimmed through pulpissimo datasheet and bit of the code but I'm lost here.
Got any pointers?

Print this item

  Regarding uDMA SPI Master
Posted by: gaumzi - 03-04-2020, 06:01 PM - Forum: PULP General questions - Replies (1)

I have been looking into using udma_qpsi (https://github.com/pulp-platform/udma_qspi) logic in SPI_STD mode. I noticed that when in SPI_STD mode for sampling data_rx in udma_spim_txrx module, spi_sdi1_i is used instead of spi_sdi0_i. 


udma_spim_txrx.sv
 line 264: s_data_rx[s_bit_index] = spi_sdi1_i;

However for data_tx spi_sdo0 is used

line 234: s_spi_sdo0 = r_tx_shift_reg[s_bit_index];


Was this intentional? If so, is there a reason behind it?

Thanks!

Print this item

  FPGA - Booting (.bit + .elf) from flash or SD card
Posted by: AhmedZaky - 02-18-2020, 07:37 AM - Forum: PULP General questions - No Replies

Hi All,

I am trying to pre-load the pulpissimo bitstream along with the application on a Genesys 2 to run the application directly without connecting it to PC. This is mainly to be done either using the SD card or SPI flash. 

Does anyone have an idea on how to merge the .bit and .elf file together to be loaded upon powering the FPGA? All the sources I found were talking about Microblaze based systems. 

Any help will be highly appreciated. 

Thanks!

Print this item

  OpenPULP Documentaion
Posted by: Supra - 02-14-2020, 01:17 PM - Forum: PULP General questions - No Replies

On page number 14 of datasheet.pdf uploaded in https://github.com/pulp-platform/pulp/bl...asheet.pdf , we have the figure of PULP.
Why isn't the Fabric Controller depicted in this image ?


It is a silly question, but it is something which would help me see the big picture correctly.

Print this item