Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing data input in NN_L0_1_small_fbuf test #84

Open
ddkkevin opened this issue Jul 24, 2018 · 9 comments
Open

Missing data input in NN_L0_1_small_fbuf test #84

ddkkevin opened this issue Jul 24, 2018 · 9 comments

Comments

@ddkkevin
Copy link

ddkkevin commented Jul 24, 2018

Hi, I am trying to run the NN_L0_1_small_fbuf test on the NVDLA small and the test can finish successfully. Then I add some debug output for the test and find that the src_data of conv operation with index 0 and the x1_data of sdp operation with index 1 are missing.

The src data of conv operation with index 0 uses memory ID 5, but the flag of memory ID 5 is 1 which means NVDLA_LOADABLE_MEMORY_FLAGS_ALLOC. Similarly, the x1_data of sdp operation with index 1 uses memory ID 7, but the flag of memory ID 7 is 1 too.

I think the correct memory flags should be 3 which means NVDLA_LOADABLE_MEMORY_FLAGS_ALLOC and NVDLA_LOADABLE_MEMORY_FLAGS_SET.

@anakin1028
Copy link

@ddkkevin, can I sidetrack ask: do you run nvdla_small on fpga or on virtual platform?

@ddkkevin
Copy link
Author

On virtual platform

@anakin1028
Copy link

So you build your own CMOD and integrate it in into virtual platform? Have you meet the problem I listed in #87?

@ddkkevin
Copy link
Author

ddkkevin commented Jul 28, 2018

I don't modify the cmod codes at all and just tmake it with nv_small spec. I have never encountered the problem listed in #87

@anakin1028
Copy link

@ddkkevin thanks for your information. What's your host system? Ubuntu 14.04 or CentoOS7? Also do you use the native kernel for the distribution?

@ddkkevin
Copy link
Author

I use CentOS 7 and the native kernel.

@anakin1028
Copy link

anakin1028 commented Aug 20, 2018

@ddkevin what's the attribute name of that flag? Is that flag defined in KMD? What you mean is since the SET macro is not being set so the input may not be valid?

Another question is do you kNow why SDP require X1, X2, and SRC? Since Activation function can run with src input? I don't know what the functionalities X1and X2 deal with?

Thanks!

@ddkkevin
Copy link
Author

The flags are defined in umd/core/include/nvdla/c/NvDlaLoadable.h. Since the compile is responsible to provide the input data from the loadable, the flag should be alloc and set, otherwise the input data is missing.

X1, X2 and Y have almost the same functions. You can get their difference from here

@honorpeter
Copy link

@anakin1028 @ddkkevin
I am trying to run the NN_L0_1_small_fbuf test on the NVDLA small on fpga ZCU102
can't run NN_L0_1_small_fbuf? Has anyone had the same problem?

== Tests for nv_small ==

= Run PDP/PDP_L0_0_small_fbuf
creating new runtime context...
Emulator starting
submitting tasks...
Shutdown signal received, exiting
Test pass
= Run CONV/CONV_D_L0_0_small_fbuf
creating new runtime context...
Emulator starting
submitting tasks...
Shutdown signal received, exiting
Test pass
= Run SDP/SDP_X1_L0_0_small_fbuf
creating new runtime context...
Emulator starting
submitting tasks...
Shutdown signal received, exiting
Test pass
= Run CDP/CDP_L0_0_small_fbuf
creating new runtime context...
Emulator starting
submitting tasks...
Shutdown signal received, exiting
Test pass
= Run NN/NN_L0_1_small_fbuf
creating new runtime context...
Emulator starting
submitting tasks

can't continue to run, Has anyone had the same problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants